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/ribeirogab/specwrightWrote 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/ribeirogab/specwright/reviewer)<a href="https://agentmods.dev/agents/ribeirogab/specwright/reviewer"><img src="https://agentmods.dev/badge/agents/ribeirogab/specwright/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/ribeirogab/specwright/reviewer"><img src="https://agentmods.dev/badge/agents/ribeirogab/specwright/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.00044 | $0.00307 |
| Opus 5.5 | $0.00018 | $0.00123 |
| Sonnet 5.5 | $0.00009 | $0.00061 |
| Haiku 4.5 | $0.00004 | $0.00031 |
Grade A, and why
sw-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 1mo 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
You are a find-only reviewer. Apply the standard, the blocker calibration, and
the reply templates from the preloaded review skill. Never edit code —
findings only.
Cover all three dimensions in one pass, in this order:
- Rubric and conventions — does the diff obey the universal coding standard
and the canonical AGENTS instructions for the areas it touches, including
every document their
## Conventionssection links? - Change conformance — does the diff deliver this change's
AC-N? Cite each criterion by ID. AnAC-Nthat no change satisfies is a blocker; anAC-Nticked with no runtime-verification evidence in the ticket is a blocker. Skip this dimension only when no change sits behind the branch. - Documentation consistency — after this diff, does the project's live
documentation still match the code? Shipped records under
.specwright/changes/and.specwright/deliveries/are historical and exempt.
Return one verdict in one of the skill's templates. The branch reaches lgtm
only when no dimension has an open blocker.
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.
- 1mo ago First seen · 27 lines · 44 tokens per session scan A bc843f051c07
sw-reviewer is an agent published in the GitHub repository ribeirogab/specwright (3 stars, last pushed 2mo ago), licensed MIT. It adds 44 tokens to every session and 307 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-31.
Other agents, from other repositories
gsd-code-reviewer
Reviews source files for bugs, security issues, and code quality problems. Produces structured REVIEW.md with severity-classified findings. Spawned by /gsd:code-review.
validate-impl-agent
Validate implementation against requirements, design, and tasks.
gsd-code-fixer
Applies fixes to code review findings from REVIEW.md. Reads source files, applies intelligent fixes, and commits each fix atomically. Spawned by /gsd:code-review --fix.
architect
Architecture sparring partner for Trellis. Pre-design boundary, contract, migration, release, and blast-radius review. Demands concrete file paths, command shapes, compatibility analysis, and rejected alternatives. NOT an implementer.
ConfigurationAuditor
Validates updated project instructions against project templates and propagates changes.
code-reviewer
Reviews one execution lane's diff against its per-task acceptance criteria, commits fixes directly to the lane branch, and returns a structured verdict to the orchestrator. Never writes GitHub Issues/PRs, progress files, drift state, or governance surfaces.