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/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/commands/jordangunn/nunchuck/plan-exec)<a href="https://agentmods.dev/commands/jordangunn/nunchuck/plan-exec"><img src="https://agentmods.dev/badge/commands/jordangunn/nunchuck/plan-exec/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/jordangunn/nunchuck/plan-exec"><img src="https://agentmods.dev/badge/commands/jordangunn/nunchuck/plan-exec.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.00000 | $0.00099 |
| Opus 5.5 | $0.00000 | $0.00040 |
| Sonnet 5.5 | $0.00000 | $0.00020 |
| Haiku 4.5 | $0.00000 | $0.00010 |
Grade A, and why
plan-exec 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
plan-exec
Execute tasks in the active plan under .plan/active/. Writes concrete Output and Handoff for each task and archives the plan once terminal.
This command delegates to the agent skill at skills/plan/plan-exec/.
Skill Root
- Path:
skills/
Skill Location
- Path:
skills/plan/plan-exec/ - Manifest:
skills/plan/plan-exec/SKILL.md
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 · 16 lines · 0 tokens per session scan A 42f9b4880c3e
plan-exec is a command published in the GitHub repository JordanGunn/nunchuck (9 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 99 tokens. 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
cancel-ralph
Cancel active Ralph Loop.
spec-forge
Use when generating software specifications — full chain ([Idea]→[Decompose]→[PRD]→SRS→Tech Design→Review) or individual documents.
constraints
A command for defining a project's quality standards through a short interview and a written CONSTRAINTS.md file. It records checks, thresholds, exceptions, and commands for enforcing them.
release
Git geçmişinden hedef kitleye uygun sürüm notları oluştur.
rclone_config_dump
Dump the config file as JSON.
dd-spec-test
Generate test spec (requires confirmed status).