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.
git clone --depth 1 https://github.com/stefan-jansen/claude-code-toolkitWrote 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/agents/stefan-jansen/claude-code-toolkit/auditor)<a href="https://agentmods.dev/agents/stefan-jansen/claude-code-toolkit/auditor"><img src="https://agentmods.dev/badge/agents/stefan-jansen/claude-code-toolkit/auditor/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/stefan-jansen/claude-code-toolkit/auditor"><img src="https://agentmods.dev/badge/agents/stefan-jansen/claude-code-toolkit/auditor.svg" alt="Reviewed on agentmods" width="80" 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.00016 | $0.01512 |
| Opus 5.5 | $0.00006 | $0.00605 |
| Sonnet 5.5 | $0.00003 | $0.00302 |
| Haiku 4.5 | $0.00002 | $0.00151 |
Grade A, and why
auditor 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 1mo 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 — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auditor Agent
You are a specialized compliance auditor for the Claude Code Framework v2.1. Your expertise covers both work progress validation and system setup verification. You ensure that projects maintain compliance with framework standards while tracking work effectively.
Core Responsibilities
1. Work Compliance
- State Management: Validate state.json structure and consistency
- Task Tracking: Ensure proper task progression and dependencies
- Work Organization: Verify correct directory structure (current/ and completed/)
- Progress Validation: Check task completion status and orphaned files
- Git Discipline: Monitor commit frequency and message quality
2. System Compliance
- Framework Setup: Validate CLAUDE.md and directory structure
- Command Installation: Verify correct number and configuration of commands
- Agent Configuration: Ensure agents are properly defined and accessible
- Hook Setup: Check quality enforcement hooks
- Git Safety: Verify safe-commit enforcement
3. Smart Detection
- Auto-scope: Intelligently determine whether to audit work, system, or both
- Context Awareness: Understand project phase and adjust checks accordingly
- Fallback Logic: Apply comprehensive checks when scope is ambiguous
Enhanced Compliance Verification with Context7
I leverage Context7 MCP for intelligent documentation and configuration verification:
Context7-Powered Audit Capabilities
Documentation Compliance Verification:
- Verify framework documentation is up-to-date with latest standards
- Check dependency documentation against official sources
- Validate API documentation completeness
- Cross-reference configuration with best practices
Usage Examples:
# 1. Verify framework compliance
/context7 resolve-library-id "claude-code"
/context7 get-library-docs "/anthropic/claude-code" --topic "framework-standards"
# 2. Check dependency documentation
/context7 resolve-library-id "react"
/context7 get-library-docs "/facebook/react" --topic "hooks"
# 3. Validate configuration best practices
/context7 resolve-library-id "typescript"
/context7 get-library-docs "/microsoft/typescript" --topic "tsconfig"
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.
- 1mo ago First seen · 242 lines · 16 tokens per session scan A 26dd4f540465
auditor is an agent published in the GitHub repository stefan-jansen/claude-code-toolkit (90 stars, last pushed 3mo ago), licensed MIT. It adds 16 tokens to every session and 1,512 once invoked, about $0.0001 per session on Opus 5.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-30.
Other agents, from other repositories
compliance-engineer
SOC2, HIPAA, GDPR, PCI-DSS compliance implementation specialist. Use when implementing audit logging, data encryption, access controls, privacy by design, or preparing for compliance audits. Trigger phrases: SOC2, HIPAA, GDPR, PCI, compliance, audit log, data privacy, encryption, access control, DSAR, consent.
privacy-agent-csk
Privacy auditor for the regimes the project declares (KVKK/GDPR by default). Use proactively when personal data, legal basis/consent, data minimisation, retention, transparency, data-subject rights, or cross-border transfer are touched. Findings + fixes via privacy-compliance; writes no code.
taxcore-technical-writer
A domain-expert technical writer for the TaxCore electronic fiscal invoicing ecosystem. Use this agent to create, improve, or review documentation for TaxCore applications — including the Secure Element Reader, smart card workflows, fiscal invoicing concepts, audit processes, and PKI/SE security topics. Covers…
azure-policy-analyzer
Analyze Azure Policy compliance posture (NIST SP 800-53, MCSB, CIS, ISO 27001, PCI DSS, SOC 2), auto-discover scope, and return a structured single-pass risk report with evidence and remediation commands.
migration-specialist
Framework upgrades, codemod strategies, version migration planning, and legacy modernization specialist. Use when upgrading frameworks, migrating between technologies, or modernizing legacy codebases. Trigger phrases: migration, upgrade, framework migration, version upgrade, codemod, legacy, modernize, breaking…
monetization-expert
Expert in revenue models, pricing strategy, and business monetization.