Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/ramboz/jignpx agentmods add skills/ramboz/jig/security-reviewWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/ramboz/jig/security-review)<a href="https://agentmods.dev/skills/ramboz/jig/security-review"><img src="https://agentmods.dev/badge/skills/ramboz/jig/security-review.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00147 | $0.03898 |
| Opus 5 | $0.00073 | $0.01949 |
| Sonnet 5 | $0.00029 | $0.00780 |
| Haiku 4.5 | $0.00015 | $0.00390 |
Grade A, and why
security-review scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
shell=True` / `child_process.exec` on dynamic input; reflection or How it starts
The opening of the file, as written. The whole thing — 315 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec 052 introduced this skill as jig's team baseline for security review, under ADR-0013's "jig provides the floor; bring your own depth" principle. Like
/jig:pr-review(spec 012),/jig:arch-review(spec 014), and/jig:contracts(spec 022), it ships as SKILL.md only — no.pyhelper. It is fundamentally a judgment skill; the determinism it needs (detect a scanner onPATH, run it, read a diff) Claude runs inline. If any other skill is installed whose description identifies it as handling security review, SAST, or vulnerability analysis, the Claude Code skill router prefers that one over jig's baseline — the deferral is category-based, not name-specific, so a richer skill named anything (security-review,adobe-security-reviewer,sast-scan,vuln-audit, etc.) wins. Jig's slim version remains the auto-trigger when no such skill is installed.
What this skill does
Produces a breadth-over-depth heuristic security pass over a diff, a branch's changes, or a pasted snippet, in a four-bucket markdown envelope:
- Summary — a one-paragraph read of what changed and the overall security posture (clean / needs fixes before merge / needs a deeper look).
- Blockers — concrete must-fix security issues. Each cites a
file:lineand a one-sentence rationale. - Nits — lower-urgency hardening suggestions. Same shape as blockers.
- Strengths — security-positive choices worth repeating (parameterized queries, secrets read from env, input validated at the boundary).
It works in two modes that compose:
- Orchestrate-if-present. When a real scanner (
semgrep,bandit,gosec,npm audit/osv-scanner) is onPATH, it runs the ones present and folds their output into the review. It installs nothing. - Defer-if-richer. When a richer security/SAST/vuln skill is installed, the router prefers it; jig's baseline yields.
When neither a scanner nor a richer skill is present, the heuristic baseline below is the floor — even a tooling-less user gets a real, structured pass. This is not a SAST engine and not a guarantee — see Honest framing.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 7d ago First seen · 315 lines · 147 tokens per session scan A 7d2bf292b0a7
security-review is a skill published in the GitHub repository ramboz/jig (6 stars, last pushed 6d ago), licensed MIT. It adds 147 tokens to every session and 3,898 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
review
Plan-aware graph-enhanced code review before merge. CRITICAL issues block merge. Use after fix/verify.
flutter-dart-code-review
Library-agnostic Flutter/Dart code review checklist covering widget best practices, state management patterns (BLoC, Riverpod, Provider, GetX, MobX, Signals), Dart idioms, performance, accessibility, security, and clean architecture.
onboarding
Skill "onboarding" from knitli/toolshed, covering codeweaver first-run onboarding, your goal, setup flow, 1. welcome & overview and 2. embedding provider selection.
setup
Skill "setup" from knitli/toolshed, covering codeweaver setup / reconfiguration, your goal, setup flow, 1. welcome & context and 2. embedding provider selection.
code-review
Use to review diffs and PRs for bugs, regressions, edge cases, proof, merge readiness.
.codex
Skill ".codex" from knitli/toolshed, covering context hygiene skill, name, description, instructions and 1. discovery.