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/jordangunn/nunchuck/task-closenpx skills add JordanGunn/nunchuck --skill task-closegit clone --depth 1 https://github.com/JordanGunn/nunchuckWrote 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/jordangunn/nunchuck/task-close)<a href="https://agentmods.dev/skills/jordangunn/nunchuck/task-close"><img src="https://agentmods.dev/badge/skills/jordangunn/nunchuck/task-close.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.00038 | $0.00177 |
| Opus 5 | $0.00019 | $0.00088 |
| Sonnet 5 | $0.00008 | $0.00035 |
| Haiku 4.5 | $0.00004 | $0.00018 |
Grade A, and why
task-close 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.
What it actually says
INSTRUCTIONS
- Refer to
metadata.references.
What ships with it
16 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.
- references/00_ROUTER.md 509 B
- references/01_SUMMARY.md 249 B
- references/02_TRIGGERS.md 365 B
- references/03_ALWAYS.md 313 B
- references/04_NEVER.md 238 B
- references/05_PROCEDURE.md 617 B
- references/06_FAILURES.md 276 B
- references/07_INSTRUCTIONS.md 382 B
- references/08_PROCEDURE.md 339 B
- scripts/include/pyproject.toml 280 B
- scripts/include/task_close_cli.py 1.7 KB runs code
- scripts/include/task_hash.py 2.2 KB runs code
- scripts/include/task_parse.py 2.4 KB runs code
- scripts/include/task_time.py 1.3 KB runs code
- scripts/run.sh 213 B runs code
- scripts/validate.sh 641 B runs code
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 · 31 lines · 38 tokens per session scan A d73b45982de5
task-close is a skill published in the GitHub repository JordanGunn/nunchuck (9 stars, last pushed 7mo ago), licensed MIT. It adds 38 tokens to every session and 177 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-31.
Other skills, from other repositories
syndic
Gère un parc de copropriétés en France avec vue portfolio consolidée. Couvre administration, comptabilité (décret 2005, plan comptable copro, 5 annexes), assemblées générales (convocation, PV, notification), appels de fonds, travaux, fournisseurs, recouvrement d'impayés et transition de syndic. Maîtrise les majorités…
friction-log
File contributor or agent papercuts as GitHub issues labeled friction, or investigate those issues as the daily friction-log Cloud Agent. Use when you hit repo friction, when asked to log friction, or when spawned to resolve open friction issues.
to-issues
Decompose a PRD and/or SPEC into implementable, vertically-sliced Issues with real blocking edges, then create them in your chosen platform (GitHub or Local). Use after /prd (and optionally /prd-to-spec) to turn requirements into agent-ready tickets. Triggers on: create issues, to-issues, 创建issue, 拆解issue, 生成卡片, 创建卡片…
recap-doc
Post-development recap document generator. Use when: AI/Codex has implemented a feature and the user needs a guided walkthrough of what changed and why, with blind-spot detection and anticipated questions. Not for: Q&A follow-up (use /recap-ask), technical share-out for teammates (use /tech-brief), or generic code…
runbook
Generate and update feature release runbooks from existing docs and codebase. Use when: creating operational runbook, release handbook, deployment checklist, pre-release preparation. Not for: incident response (v2), code review (use codex-code-review), architecture design (use architecture).
yida-agent-center
宜搭代理中心管理。查询、新增、编辑、撤销在职流程代理和离职代理，支持代处理流程、代提交流程、全部或部分流程范围。适用于设置流程审批的代理人。.