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.
git clone --depth 1 https://github.com/Cristhianzl/claude-skills-czlWrote 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/commands/cristhianzl/claude-skills-czl/task)<a href="https://agentmods.dev/commands/cristhianzl/claude-skills-czl/task"><img src="https://agentmods.dev/badge/commands/cristhianzl/claude-skills-czl/task/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/cristhianzl/claude-skills-czl/task"><img src="https://agentmods.dev/badge/commands/cristhianzl/claude-skills-czl/task.svg" alt="Reviewed on agentmods" width="80" 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.00008 | $0.00148 |
| Opus 5.5 | $0.00003 | $0.00059 |
| Sonnet 5.5 | $0.00002 | $0.00030 |
| Haiku 4.5 | $0.00001 | $0.00015 |
Grade A, and why
task 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 1mo 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.
What it actually says
/task
Argument: $ARGUMENTS (task name or snippet).
- Without argument: list 🟡 (in progress) tasks from all
<roadmap file(s)>and ask which to mark - With argument: locate the task via Grep and mark it as ✅ (replace
⬜or🟡→✅)
Confirm
✅ <task>
Roadmap: <file>
Phase progress: <X/N>
Next suggested: <task> → /next
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.
- 1mo ago First seen · 23 lines · 8 tokens per session scan A 8ae12824d3d9
task is a command published in the GitHub repository Cristhianzl/claude-skills-czl (5 stars, last pushed 1mo ago), licensed MIT. It adds 8 tokens to every session and 148 once invoked, about $0.0000 per session on Opus 5.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 commands, from other repositories
weekly-review
Produce a weekly review from the evidence in the repository and the workspace: commits and pull requests merged or open, issues closed and opened, decisions logged, research log entries, action items done and overdue, and what stalled, then a short plan for next week; written to a dated file so reviews accumulate. Use…
todo-triage
Inventory every TODO, FIXME, HACK, and XXX comment, enrich each with age and author from git blame, classify them (bug risk, missing feature, cleanup, obsolete), and produce a prioritized triage table with recommended dispositions. Pass a path to limit the scan. Use when technical-debt comments have accumulated and…
status-report
Write a delivery status report as Markdown in the user's repository. Produce designed HTML or PDF only when asked.
support-model
Write a support model as Markdown in the user's repository. Produce designed HTML or PDF only when asked.
update-counts
Explicitly refresh public toolkit and committed marketplace source snapshots and numeric documentation.
stat
A project-status command for an embedded-software project. It reads saved project notes and shows the current state, progress, next action, or a fuller project overview.