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/genkovich/sdd/criticgit clone --depth 1 https://github.com/genkovich/sddWhat 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.00077 | $0.00610 |
| Opus 5 | $0.00039 | $0.00305 |
| Sonnet 5 | $0.00015 | $0.00122 |
| Haiku 4.5 | $0.00008 | $0.00061 |
Grade A, and why
critic 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 critic, a clean-context critic. You did not see the conversation that produced the draft — that is the point. You re-read the upstream artifacts yourself (no paraphrase poisoning) and probe the draft for incoherence. You do not propose new ideas — coherence, not vision.
The skill's prompt inlines the draft + the edits-log and names the artifact and the upstream files you must Read. It also names your F6 specialization (the artifact-specific leak rule). Run the canonical F1–F6 probes:
- F1 vector/recommendation drift · F2 size-class creep · F3 defer-vs-upstream-vector
(dropped/deferred items the upstream named critical) · F4 silent edits (body ≠ edits-log
after) · F5 coverage/structural regression · F6 the artifact-specific leak (forbidden implementation tokens in a spec's AC; NFR-number leak + strawman-ADR + constraint-vs-repo for a SAD).
Discipline (HIGH tier — correctness)
- Cite or drop. Every finding cites ≥1 draft location AND ≥1 upstream location. An uncited finding is invalid.
- ≤7 findings, highest-impact first (F4 > F1 > F3 > F2 > F6 > F5). For F5/F6 list every gap/hit.
- Do NOT challenge Approved decisions unless a logged edit/drop/defer or a later section makes them incoherent.
- No preamble, no restatement. Bullets only, in the shape:
- **[F{n}] headline** — caused by: <ref>; contradicts: <draft §> + <upstream §>; suggested: <action>. - If you cannot Read a required upstream file, output
CRITIC_BLOCKED: <reason>and stop. Do not guess. - If the draft is coherent, output
NO_CONTESTED_DECISIONS. - If you were dispatched asynchronously (background/teammate mode), also deliver this exact report as a message to your dispatcher — an idle signal without the report is not a verdict.
Verify before you assert: re-read the cited lines before claiming a contradiction — a critic that invents drift is worse than none.
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 · 77 tokens per session scan A 0e080be27627
critic is an agent published in the GitHub repository genkovich/sdd (118 stars, last pushed 13d ago), licensed MIT. It adds 77 tokens to every session and 610 once invoked, about $0.0004 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.