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/rakovi4/continue-framework/agent-reviewnpx skills add rakovi4/continue-framework --skill agent-reviewgit clone --depth 1 https://github.com/rakovi4/continue-frameworkWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/rakovi4/continue-framework/agent-review)<a href="https://agentmods.dev/skills/rakovi4/continue-framework/agent-review"><img src="https://agentmods.dev/badge/skills/rakovi4/continue-framework/agent-review.svg" alt="Measured on agentmods" height="20"></a>What 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.00041 | $0.00542 |
| Opus 5 | $0.00020 | $0.00271 |
| Sonnet 5 | $0.00008 | $0.00108 |
| Haiku 4.5 | $0.00004 | $0.00054 |
Grade A, and why
agent-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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/agent-review — Fresh Eyes on Finished Work
A fresh-context pass that reads the latest work cold and surfaces any problem the
work contains. Distinct from /premortem: that imagines what the work is
missing; this audits what it holds. The two are complementary lenses, not a
repeated read.
Usage
/agent-review— review the latest work-unit commit (HEAD)/agent-review <ref>— review a specific commit or range
Workflow
- Load
.claude/agents/agent-review-agent.md. - Resolve the diff: default to the last commit (
HEAD); use<ref>if given. - Dispatch named agent
agent-review-agentwith the diff and one line of context on what the work unit did, and await its result before continuing. This skill must never return PASS before the review has actually run. - Surface the agent's verdict: PASS is silent; CONCERNS/BLOCK list each problem, its place in the diff, and the named missing guard, as follow-ups. Findings never revert the commit.
Dispatch context
When an orchestrator (/continue) dispatches this as a boundary review pass, the
agent runs concurrently with premortem — two independent fresh-context reads
of the same diff. The timing and the diff it reads in that path (every commit of the
just-completed scenario or task step, dispatched in that boundary unit's /refactor
batch — it does not run on mid-block units) are owned by /continue; see its
"Boundary Review Passes" section. A deterministic triage predicate runs before
that dispatch and may skip both passes for an inert boundary. When they do run,
/continue reads each finding's fixability tag and consumes the SAFE subset in an
inline auto-fix (a separate review-fix: commit), while a NEEDS_CLARIFICATION
finding — the last resort, gated by
.claude/templates/workflow/clarification-escalation-test.md — is resolved by a
single batched boundary quiz; see its "Triage & Auto-Fix" section. Run standalone, this skill reviews HEAD (or
<ref>) on demand. The agent is read-only; it reports, it does not edit.
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.
- 4d ago First seen · 44 lines · 41 tokens per session scan A 5133bbfa1bb7
agent-review is a skill published in the GitHub repository rakovi4/continue-framework (50 stars, last pushed 2d ago), licensed MIT. It adds 41 tokens to every session and 542 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…