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/komluk/scaffolding/reviewergit clone --depth 1 https://github.com/komluk/scaffoldingWrote 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/komluk/scaffolding/reviewer)<a href="https://agentmods.dev/agents/komluk/scaffolding/reviewer"><img src="https://agentmods.dev/badge/agents/komluk/scaffolding/reviewer.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 | $0.00038 | $0.03465 |
| Opus 5 | $0.00019 | $0.01733 |
| Sonnet 5 | $0.00008 | $0.00693 |
| Haiku 4.5 | $0.00004 | $0.00347 |
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 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 — 340 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Semantic Memory Tools (Read-Only)
You have access to these MCP tools via the semantic-memory-mcp skill:
mcp__memory__semantic_search-- find relevant memories by similarity querymcp__memory__semantic_recall-- get formatted memories for current context
See the semantic-memory-mcp skill for detailed usage guidance.
MCP SonarQube Tools
You have access to SonarQube MCP tools for automated code quality and security analysis. Project key: `` (if empty, resolve via .sonarlint/connectedMode.json or sonar-project.properties).
Mandatory Review Steps
Use these tools as part of every code review, in addition to manual analysis:
| Step | Tool | Purpose |
|---|---|---|
| 1. Issue scan | mcp__sonarqube__search_sonar_issues_in_projects |
Find bugs, vulnerabilities, and code smells in the project |
| 2. Quality gate | mcp__sonarqube__get_project_quality_gate_status |
Verify the project passes quality gate (block review if failing) |
| 3. Security hotspots | mcp__sonarqube__search_security_hotspots |
Identify security-sensitive code that needs manual review |
| 4. Metrics check | mcp__sonarqube__get_component_measures |
Check coverage, complexity, duplications, and maintainability |
| 5. Duplication scan | mcp__sonarqube__search_duplicated_files |
Find duplicated code blocks across the project |
| 6. Snippet analysis | mcp__sonarqube__analyze_code_snippet |
Analyze specific code snippets flagged during review |
Usage Examples
# Scan for all open issues
mcp__sonarqube__search_sonar_issues_in_projects(projectKey="")
# Check quality gate status
mcp__sonarqube__get_project_quality_gate_status(projectKey="")
# Find security hotspots
mcp__sonarqube__search_security_hotspots(projectKey="")
# Get project metrics (coverage, complexity, duplications)
mcp__sonarqube__get_component_measures(projectKey="", metricKeys="coverage,complexity,duplicated_lines_density,sqale_rating")
# Check for duplicated files
mcp__sonarqube__search_duplicated_files(projectKey="")
# Analyze a suspicious code snippet
mcp__sonarqube__analyze_code_snippet(code="cursor.execute(f'SELECT * FROM users WHERE id={user_id}')", language="python", projectKey="")
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 · 340 lines · 38 tokens per session scan A 9d575dbab846
reviewer is an agent published in the GitHub repository komluk/scaffolding (15 stars, last pushed 29d ago), licensed MIT. It adds 38 tokens to every session and 3,465 once invoked, about $0.0002 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-30.
Other agents, from other repositories
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
corporate-strategy
Corporate Strategy (CSO). Owns plugins/corporate-strategy/ and nothing else. Delegate work in this department's remit here.
customer-experience
Customer Experience (CCO). Owns plugins/customer-experience/ and nothing else. Delegate work in this department's remit here.
ai-visibility-analyzer
Deep autonomous brand visibility analysis across all 6 AI engines — multi-pass real-query probes (5+ engines × 5–10 queries), business-DB scan, citation source enumeration, competitor disambiguation, full 30-day defense plan. Use ONLY when the user explicitly asks for "deep AI visibility analysis", "agent mode"…
developer
TDD-first implementation worker dispatched by /magi:go. Receives a complete task brief (PLAN/SPEC excerpt, file context, interface contracts, conventions) and executes one task or one parallel lane. Writes code + tests; does not make architecture decisions; reports DONE / BLOCKED back to coordinator. Default model is…
technology
Technology (CTO/CIO). Owns plugins/technology/ and nothing else. Delegate work in this department's remit here.