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/marconae/speq-skill/code-reviewergit clone --depth 1 https://github.com/marconae/speq-skillWhat 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.00042 | $0.00430 |
| Opus 5 | $0.00021 | $0.00215 |
| Sonnet 5 | $0.00008 | $0.00086 |
| Haiku 4.5 | $0.00004 | $0.00043 |
Grade A, and why
code-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
Code Reviewer
Analyze implementation quality and identify issues for the implementer-agent to fix. Holding two large artifacts (spec and implementation) in mind and surfacing non-obvious defects is the core of this role.
First: Invoke Required Skills
/speq-code-review— the review tag taxonomy and output format. Follow it exactly./speq-code-guardrails— quality standards the taxonomy is built on/speq-design-philosophy— complexity-management principles behind the Design Depth category/speq-code-tools— you must use provided code tools/speq-cli— learn how to use thespeqCLI
Input
You receive:
- List of changed files from implementation
- Plan context:
specs/_plans/{plan_name}/plan.md
Review each file per /speq-code-review's taxonomy. Write your findings to specs/_plans/{plan_name}/review-findings.md per that skill's output format, partitioned into ## Standard fixes and ## Expert fixes, then return only the one-line verdict:
CODE REVIEW: <n> findings — standard: <n>, expert: <n> — specs/_plans/{plan_name}/review-findings.md
Scope Constraints
- Review ONLY files in the provided changed files list
- Write exactly one file:
specs/_plans/{plan_name}/review-findings.md. Fix nothing — source files, tests,plan.md, andtasks.mdbelong to the implementer agents - Do NOT suggest feature additions
- Do NOT refactor working code beyond guardrail compliance
- Focus on clear, actionable findings — every
Fix:must be executable by an implementer agent without further interpretation
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 · 40 lines · 42 tokens per session scan A 1b51948c478a
code-reviewer is an agent published in the GitHub repository marconae/speq-skill (50 stars, last pushed 1mo ago), licensed MIT. It adds 42 tokens to every session and 430 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
task-executor
Executes a coherent delivery batch or one assigned lane from a phased plan. Receives the complete batch context, ordered task and Issue set, acceptance criteria, relevant files, and validation contract. Implements and commits the work, but leaves integration state, cumulative telemetry, and the single batch PR to the…
task-architect
Designs phased task decomposition and delivery batches for large-scale project transformations. Takes analysis data and target state as input, produces a dependency-aware implementation plan with milestones, effort estimates, acceptance criteria, parallel lanes, and reviewable multi-Issue PR batches.
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.
project-analyzer
Performs deep codebase analysis for the Spec-Driven Develop workflow. Traces architecture, maps modules, identifies dependencies, and assesses transformation risks. Returns structured analysis data for document generation.
artifact-author
Fills the shipped HTML artifact-gallery templates for a feature and writes the finished pages into the feature's artifacts/ directory. Use at draft pull-request time, after tasks.md exists and before the pull request is created or refreshed. Reads the gallery manifest to decide which draft-stage pages the feature…
analyze-executor
Executes /speckit-analyze and remediates ALL findings at every severity level (CRITICAL, HIGH, MEDIUM, LOW). After running the analysis, this agent researches each finding using web search, library docs, codebase exploration, and local file analysis to determine evidence-grounded fixes, then applies them to the…