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/ssbun/csl-agent-kit/task-reviewnpx skills add SSBun/csl-agent-kit --skill task-reviewgit clone --depth 1 https://github.com/SSBun/csl-agent-kitWrote 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/ssbun/csl-agent-kit/task-review)<a href="https://agentmods.dev/skills/ssbun/csl-agent-kit/task-review"><img src="https://agentmods.dev/badge/skills/ssbun/csl-agent-kit/task-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.00060 | $0.00674 |
| Opus 5 | $0.00030 | $0.00337 |
| Sonnet 5 | $0.00012 | $0.00135 |
| Haiku 4.5 | $0.00006 | $0.00067 |
Grade A, and why
task-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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Review
Run one evidence-based review pass without changing the reviewed work.
Contract
- Never infer review from risk, task state, or another workflow.
- Return feedback only: no edits, task-state changes, reports, remediation, re-review, or approval.
- Review any task state as its snapshot; explicit unfinished work is not a defect.
- Route Reviewer–Editor remediation or approval to
adversarial-review, and whole-subject audits elsewhere.
Workflow
- Target priority: named task; focused or owning task; supplied artifact or result; PR/MR, diff, or fixed point. Ask only if absent. See Review Workflow for Git details.
- Give the Reviewer the request/criteria, applicable Target/Result/Verification, result and diff, rules or spec, checks, and limitations. Exclude the author's defense, preferred conclusion, and proposed answer.
- Use exactly one fresh, read-only subagent when possible. It may inspect evidence and run non-destructive checks, but must not edit, change task state, or delegate. Never launch a nested host CLI.
- If unavailable or failed, run the same pass inline and label
Review mode: non-independent self-review; otherwise labelReview mode: independent subagent. - Return feedback in the user's language and stop.
Lenses
- Code: behavior, callers, edges, regressions, safety, compatibility, tests, and maintainability.
- Documents and designs: claims, requirements, consistency, feasibility, failure modes, and validation.
- Configuration and assets: behavior, compatibility, defaults, consumers, and validation.
- No-file results: compare the claimed Result and evidence with the request or task Target.
Read only enough surrounding context to prove an issue; do not expand into an unrelated audit.
Findings
- Critical Findings: demonstrated target failure or material correctness, security, privacy, data-integrity, regression, or compatibility harm.
- Concerns: demonstrated non-critical problems with concrete impact.
- Unverified Risks: material uncertainty from missing evidence or checks; not confirmed findings.
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 56 lines · 60 tokens per session scan A 056cbd4b8bd3
task-review is a skill published in the GitHub repository SSBun/csl-agent-kit (10 stars, last pushed 3d ago), licensed MIT. It adds 60 tokens to every session and 674 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-31.
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…