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 skills add Codagent-AI/agent-skills --skill review-tasksgit clone --depth 1 https://github.com/Codagent-AI/agent-skillsWrote 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/codagent-ai/agent-skills/review-tasks)<a href="https://agentmods.dev/skills/codagent-ai/agent-skills/review-tasks"><img src="https://agentmods.dev/badge/skills/codagent-ai/agent-skills/review-tasks.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.1 | $0.00061 | $0.00455 |
| Opus 5 | $0.00030 | $0.00228 |
| Sonnet 5 | $0.00012 | $0.00091 |
| Haiku 4.5 | $0.00006 | $0.00046 |
Grade A, and why
review-tasks 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 7d 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Tasks
Review whether the task index and detailed task files are a faithful, complete, executable translation of the approved proposal, specifications, design, and test plan.
Read all definition and task artifacts before judging the plan. Inspect relevant repository structure when needed to verify feasibility, paths, dependencies, test placement, or implementation boundaries. The definition artifacts are immutable inputs, not review targets.
Review focus
Check that the tasks:
- cover approved requirements, scenarios, design obligations, migration, deliverables, and assigned integration or E2E tests without adding scope;
- are self-contained for implementors with no hidden session context, including exact artifact citations, constraints, acceptance criteria, and done conditions;
- form meaningful, right-sized delivery units with workable dependencies and ordering;
- keep tests, ordinary documentation, setup, and refactoring with the behavior they support;
- identify relevant implementation surfaces without prescribing line-by-line code; and
- contain no duplicate, contradictory, orphaned, or unreachable work.
Do not ask for new product, scope, architecture, or testing-strategy decisions. If a concern requires changing an approved artifact, it is outside this review and must not become a task finding. Do not review implementation correctness or modify files.
Report
Every finding must be correctable only in the task index or detailed task files. Cite the exact task section and controlling artifact section, explain the implementation risk, and recommend the specific task edit. Rank findings by impact and end with a readiness assessment; say explicitly when no actionable task defect remains.
## Findings
### [high|medium|low] <title>
- Task: <task file and section>
- Controlling artifact: <artifact and section>
- Risk: <implementation consequence>
- Correction: <specific task edit>
## Readiness Assessment
<Whether the task plan is ready and why.>
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.
- 7d ago First seen · 50 lines · 61 tokens per session scan A 55a7b3452623
review-tasks is a skill published in the GitHub repository Codagent-AI/agent-skills (30 stars, last pushed 1mo ago), licensed MIT. It adds 61 tokens to every session and 455 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…