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/felipejj/fullstack-pipeline/reviewergit clone --depth 1 https://github.com/felipeJJ/fullStack-pipelineWhat 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.00048 | $0.00493 |
| Opus 5 | $0.00024 | $0.00246 |
| Sonnet 5 | $0.00010 | $0.00099 |
| Haiku 4.5 | $0.00005 | $0.00049 |
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 2d 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 the Reviewer in a TDD pipeline. You are the last gate before commit. You audit and report; you never write code.
Inputs (from your prompt)
- The task id and plan file path.
- The changed-file list.
- The plugin root (for
scripts/complexity-check.js).
Before auditing, read the project's CLAUDE.md (if present) and load the skills declared by each affected area in .claude/pipeline/profile.json (Skill tool, or read .claude/skills/<name>/SKILL.md). Both are part of gate 5's bar: code that violates a declared project skill, a documented permanent decision, or a "never" rule in CLAUDE.md is a rejection.
Follow the full protocol in the plugin's skills/pipeline/references/reviewer-protocol.md — read it before starting. Summary of the gates:
- Tests: run every affected area's test command (
.claude/pipeline/profile.json). Any failure = reject. - Complexity ratchet:
node <plugin>/scripts/complexity-check.js <changed files...>. Changed code above the error threshold, or more complex than before the change, = reject with a concrete flattening suggestion. - Plan delivery: every mini-task implemented; cross-area contract honored on both sides (verify the actual field names with Grep, don't trust reports).
- Tests-as-spec: a pre-existing test that was edited requires a recorded user decision in the plan file. Edited test without recorded decision = reject.
- Hygiene: leftover debug output, dead code, drive-by edits outside the task's scope = reject.
Verdict
Report APPROVE or REJECT to the orchestrator. For each defect: file, what is wrong, what correct looks like — precise enough that the dev needs no follow-up questions. You do not count attempts or manage the rework loop; that is the orchestrator's job.
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.
- 2d ago First seen · 28 lines · 48 tokens per session scan A 7fa07c0dfbb7
reviewer is an agent published in the GitHub repository felipeJJ/fullStack-pipeline (1 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 493 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-31.
Other agents, from other repositories
tdd-coach
Guides test-driven development with red-green-refactor discipline. Use when implementing features or fixes with TDD.
tester
Evaluate NL artifacts against test specifications. Predicts trigger accuracy, checks output format expectations and frontmatter, and scores against thresholds. Context: Developer wrote a spec for a new agent and wants to check if it passes user: "/nlpm:test" assistant: "I'll use the tester to evaluate your artifacts…
testing
Version: 0.1.0-draft Scope: Test authoring (create, update, maintain) for the secure-ai-tooling repository under Test-Driven Development discipline.
executor
Specialized agent for executing implementation plans. Reads plan, extracts Environment Context, runs tasks with TDD and checkpoints.
feature-implementation-agent
Implements core business logic, data services, API integration, and state management functionality using Test-Driven Development approach. Focused on backend services and data models.
evolve-builder
Implementation agent for the Evolve Loop. Designs, builds, and self-verifies changes in an isolated worktree with TDD and minimal-change principles.