Skillget

raffkin

agent
Security Audit
Warn
Health Warn
  • License — License: Apache-2.0
  • Description — Repository has a description
  • Active repo — Last push 0 days ago
  • Low visibility — Only 5 GitHub stars
Code Pass
  • Code scan — Scanned 12 files during light audit, no dangerous patterns found
Permissions Pass
  • Permissions — No dangerous permissions requested

No AI report is available for this listing yet.

SUMMARY

Raffkin — an agentic SOC skill suite for Exabeam New-Scale: investigates alerts, triages the case queue and finds noisy detection rules in Claude Code or OpenAI Codex, with deterministic guardrails and a human approving every consequential action.

README.md

Raffkin

an agentic SOC skill suite for Exabeam New-Scale

Project level: Production
CI
License: Apache-2.0

📘 Looking to install or use Raffkin? Start at the user guide.

open-agent-ai-security.github.io/raffkin

How to install on Claude Code or Codex, credentials, the safety gate, your first investigation,
what gets logged. Everything on this page below the line is about how Raffkin is built —
it is for people working on the code.

Raffkin gives an AI coding agent — Claude Code or OpenAI Codex — the job of a SOC analyst on an
Exabeam New-Scale tenant, with the guardrails and governance that make that safe to do. Three skills,
named for the person whose work they do:

Skill Whose work What it does
soc-investigate the analyst one alert or case, from first look to written verdict — evidence, entity pivots, a benign hypothesis tested against a malicious one, then the write-up and the action
triage-cases the shift lead the open queue — clustered by attack shape, ranked by corroborated signal, a "start here" list; read-only across the sweep
rule-tuning the detection engineer the rules quietly wasting analyst attention, with the specific fix proposed — never applied

Dismissing an alert or closing a case is held behind two locks: a gate the plugin ships and the
host enforces (a bundled hook on Claude Code, tool-approval policy on Codex), and the skill asking you
first. Containment is recommended for a human to perform in EDR or IAM; the plugin never executes it.
Nothing is hosted by us: Raffkin runs on the analyst's machine, against your tenant, through your own
model provider.

See what it produces: a worked investigation, from alert to verdict —
coordinated credential access.

How it's built

Five separable layers. A capable model with tool access is not, by itself, something you can let
near a SOC queue; the layers below are what make it one.

Layer Where What it contributes
Methodology plugin/skills/ the procedures the model follows: soc-investigate, triage-cases, rule-tuning, sharing one safety spine
Capability .mcp.json · .mcp.codex.json the Exabeam New-Scale MCP — search, alerts and cases, threat timelines, rules and MITRE context — bundled for each host
Authority permissions.json which calls run unattended, which stop for a human, which are denied — enforced by the host, not the model; one tier file drives the Claude Code hook and the Codex policy
Guardrails plugin/connector/ a local bridge that treats telemetry as hostile input on the way in, neutralizes what the agent writes on the way out, and keeps an audit trail
Evidence security/ · evals/ the red-team program and the agent-behavior verification that gate every release, the AI BOM and the SBOM, the regression harness

Repository layout

plugin/        the distributable plugin — the only directory installed on a user's machine
  skills/      the three skills and their reference material
  connector/   the MCP bridge and its guardrails
  hooks/       the Claude Code safety gate
  docs/        the user guide, published to the site by docs_build.py
security/      release gates: red team (redteam/), behavior verification (praxen/), design records, BOMs
evals/         regression harness for the skills
tests/         deterministic invariants, run in CI
scripts/       release tooling

Working on Raffkin

  • CONTRIBUTING.md — branching (dev → main), tests, review, cutting a release.
  • tests/end-to-end-testing.md — testing real code against a live tenant, and the post-promotion install test.
  • security/ — how a release is red-teamed and behavior-verified, with the ledgers.
  • SECURITY.md — reporting a vulnerability.

Project sponsor

Raffkin is sponsored by Exabeam, which contributed the initial code and
continues to support the project as part of its commitment to security in an increasingly agentic world.

License

Apache-2.0. Contributions require a DCO sign-off — see CONTRIBUTING.md.

Reviews (0)

No results found