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 commands/madappgang/magus/clarifygit clone --depth 1 https://github.com/MadAppGang/magusWrote 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/madappgang/magus/clarify)<a href="https://agentmods.dev/commands/madappgang/magus/clarify"><img src="https://agentmods.dev/badge/commands/madappgang/magus/clarify.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.00030 | $0.01133 |
| Opus 5 | $0.00015 | $0.00566 |
| Sonnet 5 | $0.00006 | $0.00227 |
| Haiku 4.5 | $0.00003 | $0.00113 |
Grade A, and why
clarify 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 today.
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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GTD Clarify — Process Inbox Items
You are implementing the GTD clarify command. The user wants to clarify inbox items by walking through the GTD decision tree interactively.
Parse the Input
- If
--id <gtd-id>provided: process only that specific item - Otherwise: process all inbox items sequentially
Load Inbox Items
Run this Bash command:
CWD=$(pwd)
GTD_FILE="${CWD}/.claude/gtd/tasks.json"
if [ ! -f "$GTD_FILE" ]; then
echo "No GTD store found. Run /gtd:capture to add your first item."
exit 0
fi
# Get inbox items (or single item if --id provided)
ITEMS=$(jq '[.tasks[] | select(.list == "inbox" and .completed == null)]' "$GTD_FILE")
ITEM_COUNT=$(echo "$ITEMS" | jq 'length')
echo "Inbox items to process: $ITEM_COUNT"
echo "$ITEMS"
Process Each Item — GTD Decision Tree
For EACH inbox item, walk the user through this decision tree using ask_followup_question / conversation:
Step 1: Present the item
Show: Processing: "<subject>" [<id>]
Step 2: Is it actionable?
Ask: "Is this actionable? [y / n / trash / reference / someday]"
- trash: Delete from GTD store. Move on.
- reference: Move to
referencelist. Ask for a reference label to add to notes. - someday: Move to
somedaylist. - n (not actionable, not trash): Ask "Move to reference or trash?" and handle.
- y: Continue to step 3.
Step 3: Takes less than 2 minutes?
Ask: "Can you do this in under 2 minutes? [y/N]"
- y: Say "Do it now — I'll help you complete it. What do you need?" and assist completion. When done, mark completed.
- n: Continue to step 4.
Step 4: Should you delegate?
Ask: "Should you delegate this to someone? [y/N]"
- y: Ask "Who are you delegating to?" → Move to
waitinglist, setwaitingOnfield. - n: Continue to step 5.
Step 5: Is this a project (multi-step)?
Ask: "Is this a multi-step project? [y/N]"
- y: Ask "What's the project name?" → Change list to
project. Then ask "What's the very next physical action?" → Create a newnexttask with parentId pointing to this project. - n: Continue to step 6.
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.
- today First seen · 128 lines · 30 tokens per session scan A 6157a4d3d60d
clarify is a command published in the GitHub repository MadAppGang/magus (9 stars, last pushed yesterday), licensed MIT. It adds 30 tokens to every session and 1,133 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-09-04.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
PM 모드로 오케스트레이터 시작. 팀을 구성하고 5단계 워크플로우로 작업을 완수합니다.