Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/abdurrafay2004/handoff/securitynpx skills add AbdurRafay2004/handoff --skill securitygit clone --depth 1 https://github.com/AbdurRafay2004/handoffWhat 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 | $0.00064 | $0.03164 |
| Opus 5 | $0.00032 | $0.01582 |
| Sonnet 5 | $0.00013 | $0.00633 |
| Haiku 4.5 | $0.00006 | $0.00316 |
Grade A, and why
security scanned grade A with 0 findings 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 3d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Audit
Part of the Verify phase — see the workflow skill for tiers and sequencing.
Claude Code's built-in /security-review covers diff-scoped checks of pending
changes; this skill is the deeper whole-repo audit — run it at the T3 verify
gate, before launch, or on a schedule. Don't duplicate the built-in for diffs.
You are a Chief Security Officer who has led incident response on real breaches. You think like an attacker but report like a defender. No security theater — find the doors that are actually unlocked.
The real attack surface isn't your code — it's everything around it: exposed env vars in CI logs, stale API keys in git history, forgotten staging servers with prod DB access, third-party webhooks that accept anything, and installed agent skills. Start there, not at the code level.
You do NOT make code changes. You produce a Security Posture Report with concrete findings, severity ratings, and remediation plans.
Modes and scope
- Standard (default): all phases, 8/10 confidence gate. Zero noise.
- Comprehensive (user asks for a deep/monthly scan): all phases, 2/10 gate —
surfaces more, marks sub-8 findings
TENTATIVE. - Scoped (user asks for e.g. "audit auth" / "supply chain only"): run Phases 0-1, the phases matching the scope, then Phases 12-13. Never silently reinterpret the user's scope — if it's ambiguous, ask.
Phases 0, 1, 12, 13 always run. If WebSearch is unavailable, skip checks that need it and note: "WebSearch unavailable — proceeding with local-only analysis."
Use the Grep tool for all code searches
Bash blocks in this skill and its references show WHAT patterns to search for,
not HOW to run them. Use the Grep/Glob/Read tools rather than raw shell grep.
Do not truncate results with | head.
Instructions
Phase 0: Architecture Mental Model + Stack Detection
Before hunting for bugs, detect the stack and build an explicit mental model. This phase changes HOW you think for the rest of the audit.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 247 lines · 64 tokens per session scan A 227d64b564c2
security is a skill published in the GitHub repository AbdurRafay2004/handoff (4 stars, last pushed 1mo ago), licensed MIT. It adds 64 tokens to every session and 3,164 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
checkpoint
Write the current working state (task, decisions, files touched, open problems, next steps) to .amber/STATE.md so it survives compaction and session restarts. Use when the user asks to checkpoint/save state, before risky long operations, when context feels heavy, or before ending a work session.
focus
Declare a focus contract for the current task to keep context lean — scopes which files/dirs are in play, bans out-of-scope exploration, and routes broad searches to subagents. Use when starting a task, when the user says "focus on X", or when the session is drifting across unrelated parts of the codebase.
react
React UI patterns for apps/ui—Effects vs rendering, TanStack Query for all server data, useMemo, keys, event handlers. Start here when creating or editing React components.
diet
Audit what is eating the context window in this project (CLAUDE.md size, MCP servers, rules that should be skills) and produce a concrete slimming plan with estimated token savings. Use when the user complains about context filling up fast, frequent compaction, or asks to optimize/reduce context usage.
resume
Reload saved working state from .amber/ (STATE.md, FOCUS.md, checkpoint.md) and continue the previous task. Use when the user says resume/continue where we left off, or at the start of a session in a project that has an .amber directory.
project-memory
Use when resuming work after chat loss, switching AI models, migrating context to a new agent or workspace, or maintaining long-running research and project memory across sessions. Manages roadmap, decision log, hypotheses, research evidence, and recovery checkpoints as separate canonical files so no single transcript…