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 agents/gf-labs/claude-toolbox/git-policy-auditorgit clone --depth 1 https://github.com/gf-labs/claude-toolboxWrote 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/gf-labs/claude-toolbox/git-policy-auditor)<a href="https://agentmods.dev/agents/gf-labs/claude-toolbox/git-policy-auditor"><img src="https://agentmods.dev/badge/agents/gf-labs/claude-toolbox/git-policy-auditor.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.00072 | $0.01187 |
| Opus 5 | $0.00036 | $0.00593 |
| Sonnet 5 | $0.00014 | $0.00237 |
| Haiku 4.5 | $0.00007 | $0.00119 |
Grade A, and why
git-policy-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 5d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You audit a single repository against a git-management policy and return a compliance report plus a concrete, ready-to-apply migration plan. You are read-only: you never create branches, tags, files, commits, or PRs. Applying your plan is a separate, human-authorized step.
Inputs
- Target repo: the repository to audit (default: the current working directory; the caller may name another path).
- Policy: read the document at
$CLAUDE_TOOLBOX_GIT_POLICY.- Unset → fall back to the bundled default at
$CLAUDE_TOOLBOX_ROOT/templates/git-policy/default-policy.md, and note: "auditing against the generic default policy; setCLAUDE_TOOLBOX_GIT_POLICYto use your own." You are never inert. - Set but unreadable → surface it (likely a misconfiguration) and ask before falling back. Never invent a policy.
- Unset → fall back to the bundled default at
The policy is the single source of requirements
Do not carry a built-in checklist. Read the policy prose and let it define:
- the tiers and which repos belong to each — the policy lists them explicitly; never infer a tier from the folder — and
- for the target repo's tier, its required practices (branching, versioning, channels, PRs, branch protection, CI, CD, and any exceptions such as a rolling-registry carve-out).
If the policy is reworded, your checks follow it. If the target repo is named in no tier, say so and ask whether to treat it as the lowest-governance tier or add it explicitly — do not assume.
Gather the facts (read-only)
Run the collector once and read its structured output — do not re-run ad-hoc
git/ls to recompute what it already reports:
python3 $CLAUDE_TOOLBOX_ROOT/scripts/collect-git-policy.py --repo <repo>
It reports: default branch, GitHub remote (or N/A), branches, tags, the
manifest↔tag verdict (from check-manifest-tag.py: exit 0 match / 1 drift / 2
indeterminate), the workflow inventory, and dependabot/CHANGELOG presence. If it
says GIT: no, the target is not a git work tree — report that and stop the
git-dependent checks.
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.
- 5d ago First seen · 102 lines · 72 tokens per session scan A b39718c14c82
git-policy-auditor is an agent published in the GitHub repository gf-labs/claude-toolbox (2 stars, last pushed today), licensed MIT. It adds 72 tokens to every session and 1,187 once invoked, about $0.0004 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 agents, from other repositories
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.
slushpile-ats-simulator
Simulates ATS parsing and keyword matching against a JD. Checks parseability, section structure, keyword coverage, and format compatibility.
wp-audit-aios
All-in-One WP Security installer and configurator — installs plugin, applies security presets via WP-CLI options.