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 skills/wrongstack/wrongstack/auto-reviewnpx skills add WrongStack/WrongStack --skill auto-reviewgit clone --depth 1 https://github.com/WrongStack/WrongStackWhat 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.00067 | $0.01641 |
| Opus 5 | $0.00034 | $0.00821 |
| Sonnet 5 | $0.00013 | $0.00328 |
| Haiku 4.5 | $0.00007 | $0.00164 |
Grade A, and why
auto-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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auto Review — Built-in Plugin
Overview
The wstack-auto-review plugin (built into @wrongstack/core) detects
every git-tracked file change during a session and automatically dispatches
a review subagent. It extends the Chimera review pipeline but fires
mid-session on every change, not just at session end.
iteration.completed → git diff → debounce → chimera.review_needed event
↓
Director spawns review subagent
(provider/model from config)
↓
Severity-ranked report → session + mailbox
↓
chimera.review_complete event
↓
parseReviewSeverity → shouldCascade
↓ (if threshold crossed)
chimera.cascade_needed event
↓
Director spawns follow-up agents
(security-scanner, bug-hunter)
Status
This is a built-in plugin (packages/core/src/plugins/auto-review-plugin.ts),
NOT a skill-based watcher. It is loaded automatically but disabled by default.
Enable it in your config:
{
"extensions": {
"wstack-auto-review": {
"enabled": true,
"provider": "deepseek",
"model": "deepseek-chat",
"fallbackProfile": "reliable",
"modelSelection": "round-robin",
"debounceMs": 15000,
"maxFilesPerBatch": 15,
"cascadeOn": "high",
"maxCascadeDepth": 2
}
}
}
Requirements
--directorflag (Director mode) — the subagent spawning pipeline (execution.ts) requires the Director to be active. Without it, review events are silently skipped.gitavailable in the session working directory.
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 · 180 lines · 67 tokens per session scan A bbf69307eda4
auto-review is a skill published in the GitHub repository WrongStack/WrongStack (240 stars, last pushed yesterday), licensed MIT. It adds 67 tokens to every session and 1,641 once invoked, about $0.0003 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 skills, from other repositories
research-repository
Build a repository that makes findings findable, reusable, and cumulative across teams. Use when the same research keeps getting redone. For synthesising one study, use affinity-diagram.
design-negotiation
Advocate for design quality, scope, and timeline with partners and leadership using evidence and shared goals. Use in the conversation itself. For the commercial vocabulary behind it, use business-design (ux-strategy).
version-control-strategy
Define version control for design files, components, and libraries — branching, naming, and release. Use when file history is chaotic. For design system contribution rules, use design-system-governance (design-systems).
presentation-deck
Structure a design presentation for a specific audience and decision. Use when presenting internally. For a portfolio narrative use case-study; for the written argument use design-rationale.
ux-writing
Write interface copy — microcopy, error messages, empty states, and CTAs. Use when the words are the deliverable. For content structure and ownership, use content-strategy (ux-strategy).
diary-study-plan
Design a diary study — prompts, cadence, duration, participant criteria, and analysis frame. Use when behaviour unfolds over days or weeks. For a single-session study, use usability-test-plan.