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/reviewtoolkits/cext-review-toolkit/task-workflownpx skills add ReviewToolkits/cext-review-toolkit --skill task-workflowgit clone --depth 1 https://github.com/ReviewToolkits/cext-review-toolkitWrote 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/reviewtoolkits/cext-review-toolkit/task-workflow)<a href="https://agentmods.dev/skills/reviewtoolkits/cext-review-toolkit/task-workflow"><img src="https://agentmods.dev/badge/skills/reviewtoolkits/cext-review-toolkit/task-workflow.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.00024 | $0.00714 |
| Opus 5 | $0.00012 | $0.00357 |
| Sonnet 5 | $0.00005 | $0.00143 |
| Haiku 4.5 | $0.00002 | $0.00071 |
Grade A, and why
task-workflow 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 5d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Workflow
Execute the standard development workflow for this task: $ARGUMENTS
Follow these steps in order. Do NOT skip any step.
Step 1: Create GitHub Issue
gh issue create --title "<title>" --body "<description>" --label "<label>"
Common labels: enhancement, bug, tests, documentation, refactor
Use the task description to write a clear issue title and body. The body should explain the context, what needs to change, and why.
Step 2: Create Feature Branch
Branch naming convention:
feat/<slug>for new featuresfix/<slug>for bug fixesrefactor/<slug>for refactoringtest/<slug>for test-only changesdocs/<slug>for documentation
git checkout -b <prefix>/<short-slug>
Step 3: Implement Changes
Read existing code before modifying it. Follow patterns already established in the codebase. Key conventions:
- Python 3.10+
- Double quotes for strings
- Type hints on all function signatures
- Docstrings on classes and public functions
- Tests use
unittest— never pytest - Scripts follow the
analyze()+main()pattern (see scan_common.py for arg parsing) - Add an entry to
CHANGELOG.mdunder## [Unreleased]in the appropriate section (Added/Enhanced/Fixed/Documentation). Format:- Description.
Step 4: Verify
Run formatting, linting, type checking, and all tests. ALL must pass before committing. NEVER install tools to the system Python, if necessary create a venv and install tools into it.
ruff format <changed-files>
ruff check <changed-files>
mypy
python -m unittest discover tests -v
If any tests fail, fix them before proceeding.
Step 5: Commit
Stage only the files you changed. Use conventional commit format. Always include the issue reference.
git add <specific-files>
git commit -m "$(cat <<'EOF'
<type>: <description>
<optional body>
Closes #<issue-number>
Co-Authored-By: Claude Opus 4.6 <[email protected]>
EOF
)"
Step 6: Push and Create PR
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.
- 5d ago First seen · 115 lines · 24 tokens per session scan A 11bd4a6e307d
task-workflow is a skill published in the GitHub repository ReviewToolkits/cext-review-toolkit (28 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 714 once invoked, about $0.0001 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…