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/varienos/agentic-workflow/code-review.skeletongit clone --depth 1 https://github.com/varienos/agentic-workflowWhat 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.00002 | $0.02032 |
| Opus 5 | $0.00001 | $0.01016 |
| Sonnet 5 | $0.00000 | $0.00406 |
| Haiku 4.5 | $0.00000 | $0.00203 |
Grade A, and why
code-review 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 yesterday.
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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review Agent
Calisma Siniri
Bu agent Agentbase den spawn olur ve ../Codebase/ uzerinde calisir.
- Proje dosyalarini (
src/,app/, vb.) okuyabilir ve degistirebilir - Codebase icinde
.claude/dizini OLUSTURAMAZ - Codebase icinde
CLAUDE.md,.mcp.json,.claude-ignoreYAZAMAZ - Tum agent config dosyalari Agentbase/.claude/ altinda yasar
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.
- yesterday First seen · 199 lines · 2 tokens per session scan A bffd0f9cef01
code-review is an agent published in the GitHub repository varienos/agentic-workflow (58 stars, last pushed 2mo ago), licensed MIT. It adds 2 tokens to every session and 2,032 once invoked, about $0.0000 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
engineering-manager
The Engineering Manager of the aSPARK team. Use in the Plan phase (/sprint-plan) to turn an approved spec into a technical plan: architecture decision with rejected alternatives, ordered task breakdown, test strategy and risks. Also use when a plan must be revised after review or QA findings.
project-manager
Project delivery specialist. Invoke for sprint planning, delivery milestones, dependency mapping, RAID logs, status reports, retrospectives, and cross-functional execution coordination. Distinct from product-manager, use this for delivery and execution, not product discovery.
blind-spot-finder
Adversarial fresh-eyes code reviewer. Receives the diff only — no plan, spec, or design — and deliberately hunts for the scenarios intent-aware reviewers forgive: concurrency, retries, encoding, security, production failures, maintenance traps, and unknown-unknowns. Every finding is a concrete scenario, not a vague…
plan-reviewer
Reviews implementation plans and design documents for completeness, feasibility, convention compliance, and gap analysis. Invoke before approving a plan, when a plan is revised, or when a design needs a structural sanity check. Returns findings with severity and a verdict of Approve or Revise.
researcher
Gathers context from planning artifacts, codebase, and the web to inform planning decisions. Invoke at the start of /brainstorm, /specify, /design, /plan, /poke-holes, or any skill that needs a compound view of existing research, specs, designs, plans, and related code before new work begins.
spec-reviewer
Reviews specifications for testability, completeness, and ambiguity. Invoke before approving a spec, when a spec is revised, or when acceptance criteria need to be stress-tested for measurability. Returns findings with severity and a verdict of Approve or Revise.