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/dheerg/swarms/audit-contextnpx skills add DheerG/swarms --skill audit-contextgit clone --depth 1 https://github.com/DheerG/swarmsWrote 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/dheerg/swarms/audit-context)<a href="https://agentmods.dev/skills/dheerg/swarms/audit-context"><img src="https://agentmods.dev/badge/skills/dheerg/swarms/audit-context.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 | $0.00042 | $0.01227 |
| Opus 5 | $0.00021 | $0.00613 |
| Sonnet 5 | $0.00008 | $0.00245 |
| Haiku 4.5 | $0.00004 | $0.00123 |
Grade A, and why
audit-context 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 4d 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.
Reads agent configuration directorieslowAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
4. **Settings hooks.** Check both `.claude/settings.json` (project) and `~/.claude/settings.json` (global) for a `hooks` section. Flag any hook that intercepts tools used by swarm (the Agent tool, SendMessage, or CronCre Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit Context
Evaluate the user's ambient context artifacts for compatibility with swarm's governance rules. You are a read-only diagnostic — never modify any files.
What to scan
- CLAUDE.md files. Read the project's
CLAUDE.md(working directory root). If.claude/CLAUDE.mdexists, read that too. Also check~/.claude/CLAUDE.md(global config) — it loads into every session. - Memory files. Find the project memory path by checking
~/.claude/projects/for a directory matching the current working directory. Claude Code dash-encodes the project path (e.g.,/Users/foo/my-projectbecomes-Users-foo-my-project). If amemory/MEMORY.mdindex exists, read it and follow links to individual memory files. - Local skills and commands. List
.claude/skills/and.claude/commands/in the project directory. Flag any skill whose name matches a swarm built-in:suggest-members,define-rubric,resolve-dispute,writing-style,reflect-outcome,independent-review-loop,code-mode,triage-mode,writing-mode,general-mode,workflow-rules,audit-context. - Settings hooks. Check both
.claude/settings.json(project) and~/.claude/settings.json(global) for ahookssection. Flag any hook that intercepts tools used by swarm (the Agent tool, SendMessage, or CronCreate).
How to classify
For each artifact, classify as one of three categories:
- Complementary — Does not conflict with any swarm rule. Style preferences (brevity, tone, formatting), domain conventions, and tool permissions are complementary by default. No action needed.
- Potentially Interfering — Could conflict with a swarm rule depending on context. The artifact's intent is benign but its phrasing is broad enough to suppress or alter expected swarm behavior. Worth reviewing.
- Conflicting — Directly contradicts a named swarm governance rule. Will likely cause unexpected behavior during a team run. Should be addressed before launching.
Swarm governance rules to evaluate against
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.
- 4d ago First seen · 95 lines · 42 tokens per session scan A e46a276d5276
audit-context is a skill published in the GitHub repository DheerG/swarms (86 stars, last pushed 1mo ago), licensed MIT. It adds 42 tokens to every session and 1,227 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
pocket-development
Use when executing implementation plans of one or more tasks. Trigger on execute plan, delegate tasks, dispatch subagents. Combines delegate handoff discipline with prompt-engineering attention mechanics.
pocket-grinding
BDD-driven feature/fix discovery before any implementation. Use when planning a feature, designing a fix, or exploring options before building. Trigger on "pocket-grinding", "brainstorm", "think through", "plan this", "before we build". Invokes pocket-planning at handoff.
pocket-planning
Converts a pocket-grinding spec into a TDD-structured execution plan of full Pocket Packets. Use when pocket-grinding handoff arrives (spec path + acceptance criteria). Trigger on "create plan", "build plan", "pocket-planning", or when pocket-grinding skill invokes this. Outputs tasks ready to dispatch via…
pocket-closing
Terminal pocket stage. User invokes after pocket-development's phase-level pass writes verdicts. Reconciles reviews against log.json, gates on REVIEWFAIL/REVIEWBLOCKED, advances REVIEW→DONE, runs log close, and emits a closeout summary. Trigger on "pocket-closing", "close the plan", "close out", "finalize plan", or…
pocket-help
Onboarding and routing guide for the Pocket skill ecosystem. Use when someone asks what Pocket is, which Pocket skill to use, how the end-to-end flow works, or when Pocket is better than lighter Superpowers-style flows. Trigger on "what is pocket", "how do I use pocket", "which pocket skill", "explain pocket"…
bug-hunting
Use when fixing bugs, debugging failures, or proactively reviewing code for hidden bugs. Reactive mode: fix known bugs. Proactive mode: hunt for bugs in code. Enforces confirmed root cause before any fix.