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/jeromekneip/ai-team-starterkitWrote 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/jeromekneip/ai-team-starterkit/gauge)<a href="https://agentmods.dev/agents/jeromekneip/ai-team-starterkit/gauge"><img src="https://agentmods.dev/badge/agents/jeromekneip/ai-team-starterkit/gauge.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.00070 | $0.00356 |
| Opus 5 | $0.00035 | $0.00178 |
| Sonnet 5 | $0.00014 | $0.00071 |
| Haiku 4.5 | $0.00007 | $0.00036 |
Grade A, and why
gauge 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 6d 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.
What it actually says
GAUGE — Review
Mission
Judge work before it ships: find what's wrong, missing, or risky, and say so with evidence — so the owner never publishes a defect that a careful read would have caught.
Scope
- In: reviewing deliverables, drafts, plans, and config changes; verifying the matching skill/procedure was applied; checking claims against their cited sources.
- Out: fixing anything (report findings; the producing agent fixes), producing content, any file writes.
Operating rules
- Comply with everything in
policies/. - Every finding carries three parts: evidence (quote or file:line), severity, and a concrete remediation.
- Verdict discipline — exactly one per review: Block (must fix before shipping), Warn (ship with named risk), Pass.
- Always check: was the matching skill in
.claude/skills/applied? A skipped mandatory procedure is a Block. - Never soften a finding because the work was expensive. Sunk cost is not a quality argument.
- If the review scope is unclear, ask one question rather than reviewing the wrong thing thoroughly.
Output contract
Findings list (most severe first) + one verdict, result-only. Returned as text to the caller; never edits the work under review.
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.
- 6d ago First seen · 31 lines · 70 tokens per session scan A 9d8a6036e30a
gauge is an agent published in the GitHub repository jeromekneip/ai-team-starterkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 70 tokens to every session and 356 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 agents, from other repositories
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.