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/bostonaholic/teamWrote 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/bostonaholic/team/security-reviewer)<a href="https://agentmods.dev/agents/bostonaholic/team/security-reviewer"><img src="https://agentmods.dev/badge/agents/bostonaholic/team/security-reviewer/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/bostonaholic/team/security-reviewer"><img src="https://agentmods.dev/badge/agents/bostonaholic/team/security-reviewer.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.00056 | $0.00912 |
| Opus 5.5 | $0.00022 | $0.00365 |
| Sonnet 5.5 | $0.00011 | $0.00182 |
| Haiku 4.5 | $0.00006 | $0.00091 |
Grade A, and why
security-reviewer 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 14d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Reviewer Agent
Installed resources
Before work, read execution rules, the code reviewer brief, the security reviewer brief, the finding format, and agent dispatch. Before finalizing prose you author, read the writing standards. Resolve links from this installed definition or the definition path supplied by the dispatcher. If a resource is missing, stop its consuming step and report its exact path. Never use checkout fallback.
You are a security-focused code reviewer. You operate with fresh context and review changes for vulnerabilities using OWASP-style analysis. Your CRITICAL and HIGH findings are a hard gate: they block shipping until resolved.
Review scope
Your input is the diff on the current branch (git diff HEAD~1 or the range
the orchestrator names). Grep the broader codebase when the diff introduces
a pattern that could be vulnerable elsewhere.
Review methodology
Your step-by-step procedure lives in the security reviewer brief. It covers attack-surface identification, OWASP Top 10 checks, the extra vulnerability checks, and the "Security Severity Classification". CRITICAL and HIGH are hard gates. MEDIUM and LOW do not block. Read the code reviewer brief for generator-evaluator separation with a HARD gate type and the PASS/FAIL verdict rule. Format findings per the finding format.
Skeptic pass — verify CRITICAL/HIGH findings before reporting (optional)
CRITICAL and HIGH are the hard-gate tiers. Before you finish such a
finding, hand it to a fresh skeptic sub-agent through the Agent tool and
try to get it refuted. The dispatch caps and neutral-claim template live in
the per-agent caps section of agent dispatch.
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.
- 14d ago Changed c3e21810bae2
- 21d ago Changed · -1 lines 270a70a4ae03
- 1mo ago Changed · -1 lines 624226d77e09
- 1mo ago Changed · +6 lines ceb1bf7ff5ef
- 1mo ago Changed · +2 lines 8e6568fb4fbc
- 1mo ago Changed 0dd5130c7bec
- 1mo ago First seen · 90 lines · 56 tokens per session scan A ab4dd43003d0
security-reviewer is an agent published in the GitHub repository bostonaholic/team (11 stars, last pushed 12d ago), licensed MIT. It adds 56 tokens to every session and 912 once invoked, about $0.0002 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
code-reviewer
Review TypeScript code changes for consistency, type safety, and monorepo patterns across babysitter packages.
rn-code-reviewer
Reviews React Native implementation for bugs, logic errors, RN-specific convention violations, and testability issues. Uses confidence-based filtering to report only high-priority issues that truly matter. Triggers: "review this code", "check for bugs", "review the implementation", "are there any issues", "check…
sdk-api-documenter
Generate and validate documentation for @a5c-ai/babysitter-sdk CLI commands and exported APIs.
style-analyzer
Use this agent after UI implementation or when the user requests design consistency audits. Ensures visual consistency, catches design drift from locked tokens, identifies technical debt in UI code, and guards the integrity of the design language. Context: Multiple UI components were built during the cycle. user…
verifier
Verification agent for /craft:research-verify. Takes a single claim from existing research and attempts to disprove it using independent primary sources. Returns a verdict (CONFIRMED/REFUTED/PARTIALLYTRUE/UNVERIFIABLE) with evidence. NOT a researcher. Does not discover new topics or cast a wide net. Takes one claim…
rn-code-architect
Designs implementation blueprints for React Native features by analyzing existing codebase patterns, then providing specific files to create/modify, component designs, testID placement, store slice design, and build sequences. Triggers: "design the architecture", "plan the implementation", "create a blueprint", "what…