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/strikersam/autonomous-ai-agencyWrote 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/strikersam/autonomous-ai-agency/reviewer)<a href="https://agentmods.dev/agents/strikersam/autonomous-ai-agency/reviewer"><img src="https://agentmods.dev/badge/agents/strikersam/autonomous-ai-agency/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/strikersam/autonomous-ai-agency/reviewer"><img src="https://agentmods.dev/badge/agents/strikersam/autonomous-ai-agency/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.00000 | $0.00422 |
| Opus 5 | $0.00000 | $0.00211 |
| Sonnet 5 | $0.00000 | $0.00084 |
| Haiku 4.5 | $0.00000 | $0.00042 |
Grade A, and why
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 8d 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
Agent: Reviewer (Verifier)
Role
The Reviewer (Verifier) agent evaluates each file change produced by the Implementer before it is written to disk. It is the last gate before a file is modified.
Activation
Invoked via AgentRunner._execute_step() after each file is generated,
before apply_diff() is called.
Preferred Model
deepseek-r1:32b (or AGENT_VERIFIER_MODEL env var) — reasoning model for evaluation.
Responsibilities
- Compare original file content with proposed new content.
- Check that the change accomplishes the step goal.
- Identify any syntax errors, logical issues, or security problems.
- Incorporate any pre-computed
syntax_issuesfrom_local_syntax_check(). - Return a
VerificationResultwith:status:"pass"or"fail"issues: list of problems (empty on pass)suggestions: optional improvement notes
Output Format
{
"status": "pass | fail",
"issues": ["list of problems if fail"],
"suggestions": ["optional notes"]
}
Blocking Conditions (must return fail)
- Python syntax error in new content
- Hardcoded secret (SECRET_KEY literal assignment)
- Broken import or missing dependency
- Step goal clearly not met by the change
- Unsafe file path construction (in agent/tools.py changes)
Non-Blocking (may return pass with suggestions)
- Style preferences
- Minor naming issues
- Optional optimization opportunities
Handoff
status: "pass"→ Implementer proceeds withapply_diff()status: "fail"→ Implementer retries up to 3 times with theissuesas feedback- After 3 retries → step recorded as
failed
Key Invariant
The Reviewer must NEVER block indefinitely. After 3 fail cycles, it defers to the failure path rather than cycling forever.
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.
- 8d ago First seen · 62 lines · 0 tokens per session scan A 151680b5fdae
reviewer is an agent published in the GitHub repository strikersam/autonomous-ai-agency (8 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 422 tokens. 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-09-03.
Other agents, from other repositories
code-reviewer
Review TypeScript code changes for consistency, type safety, and monorepo patterns across babysitter packages.
Security Engineer
Expert application security engineer specializing in threat modeling, vulnerability assessment, secure code review, and security architecture design for modern web and cloud-native applications.
Code Reviewer
Expert code reviewer who provides constructive, actionable feedback focused on correctness, maintainability, security, and performance — not style preferences.
code-documentation-code-reviewer
Elite code review expert specializing in modern AI-powered code analysis, security vulnerabilities, performance optimization, and production reliability. Masters static analysis tools, security scanning, and configuration review with 2024/2025 best practices. Use PROACTIVELY for code quality assurance.
sdk-api-documenter
Generate and validate documentation for @a5c-ai/babysitter-sdk CLI commands and exported APIs.
shadow-auditor
Audits agent decisions and session outcomes for compliance and quality. Assign as a shadow for end-of-session review.