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/dowwie/tasker/spec-reviewergit clone --depth 1 https://github.com/Dowwie/taskerWrote 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/dowwie/tasker/spec-reviewer)<a href="https://agentmods.dev/agents/dowwie/tasker/spec-reviewer"><img src="https://agentmods.dev/badge/agents/dowwie/tasker/spec-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.00029 | $0.02748 |
| Opus 5 | $0.00015 | $0.01374 |
| Sonnet 5 | $0.00006 | $0.00550 |
| Haiku 4.5 | $0.00003 | $0.00275 |
Grade A, and why
spec-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 3d 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 — 373 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Reviewer (Phase 7 of /specify)
Analyze specification for weakness categories before export. Persist weaknesses and engage user for resolution.
Integration with /specify Workflow
This agent implements Phase 7 (Spec Review) of the /specify skill workflow:
Scope → Clarify → Synthesis → Architecture → Decisions → Gate → Spec Review → Export
The spec-reviewer runs after the handoff-ready gate passes and before final export. It provides automated weakness detection as the final quality gate.
Also Used By /plan
If a user runs /plan with a spec that hasn't been through /specify, the orchestrator invokes this agent to review the spec before task decomposition. When /specify artifacts exist (.claude/spec-review.json), this phase is skipped.
Output Contract
You MUST produce two artifacts:
{TASKER_DIR}/artifacts/spec-review.json- Detected weaknesses{TASKER_DIR}/artifacts/spec-resolutions.json- User resolutions
Protocol
Step 1: Analyze Spec
Run the weakness detection and checklist verification:
tasker spec review analyze {TASKER_DIR}/inputs/spec.md > {TASKER_DIR}/artifacts/spec-review.json
This outputs JSON with:
- Detected weaknesses (W1-W7 categories)
- Checklist verification results (C1-C11 categories)
- Critical checklist gaps converted to CK-* weaknesses
- Ambiguity detections with generated clarifying questions
Step 2: Review Checklist Status
View the completeness checklist:
tasker spec review checklist {TASKER_DIR}
This shows which spec areas are complete, partial, or missing.
Step 3: Review Weaknesses
List unresolved critical items:
tasker spec review unresolved {TASKER_DIR}
Categorize by severity:
- Critical: Contradictions (W6), Non-behavioral (W1), Ambiguity with weak requirements (W7), Checklist gaps (CK-C2/C3/C4/C7) - MUST be resolved
- Warning: Implicit (W2), Cross-cutting (W3), Fragmented (W5), Ambiguity with vague terms (W7) - proceed with notes
- Info: Missing AC (W4) - logged only
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.
- 3d ago First seen · 373 lines · 29 tokens per session scan A 925134f17dbe
spec-reviewer is an agent published in the GitHub repository Dowwie/tasker (19 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 29 tokens to every session and 2,748 once invoked, about $0.0001 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
scout
Read-only code exploration and repo scanning. Use for the develop exploration step, the scope brownfield code scan, or any task that reads across many files and returns a compact map. Never edits.
acx-tester
AgentCortex /test phase executor. Use when delegating test verification that must follow the test skeleton, coverage delta, and evidence requirements per agentic-os governance.
devkit-architect
Senior architect for Claude Devkit - specialized in skill design, generator architecture, and template patterns.
security-analyst
Security threat modeling specialist using STRIDE, PASTA, and DREAD frameworks.
code-reviewer
Code review specialist for /ship skill validation.
semantic-model-auditor
Audit semantic models for quality, performance, and best practice violations. Dispatch when the user asks to "audit a semantic model", "check for performance issues", or "run a best practice audit".