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/mdsakalu/agent-plugins/retiregit clone --depth 1 https://github.com/mdsakalu/agent-pluginsWrote 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/mdsakalu/agent-plugins/retire)<a href="https://agentmods.dev/commands/mdsakalu/agent-plugins/retire"><img src="https://agentmods.dev/badge/commands/mdsakalu/agent-plugins/retire.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.00016 | $0.00577 |
| Opus 5 | $0.00008 | $0.00289 |
| Sonnet 5 | $0.00003 | $0.00115 |
| Haiku 4.5 | $0.00002 | $0.00058 |
Grade A, and why
retire 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 3d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Retire a workspace (mark as retired, forget JJ workspace, preserve notes).
Resolve the metarepo path by reading ~/.claude/workspace-config.json and expanding ~ to $HOME.
The user's request: $ARGUMENTS
Steps
- Read
~/.claude/workspace-config.jsonto get the metarepo path. Expand~to$HOME. - Determine which workspace to retire:
- If
<repo>/<workspace>specified, use it - If just
<workspace>, search across repos - If no argument, infer from cwd
- If unable to determine, list workspaces and ask
- If
- Read
<metarepo>/notes/<repo>/<workspace>/workspace.jsonto get current state. - Confirm with the user before proceeding. Show:
- Workspace name, repo, type, purpose
- What will happen:
retireddate set in workspace.json, JJ workspace forgotten - Notes preserved at
<metarepo>/notes/<repo>/<workspace>/ - Ask explicitly: "Proceed with retiring
<repo>/<workspace>?"
- After confirmation:
a. Update workspace.json — set
"retired": "<today's date>"using jq:
b. Forget the JJ workspace from the trunk:jq --arg date "$(date +%Y-%m-%d)" '.retired = $date' workspace.json > tmp && mv tmp workspace.json
c. Ask the user if they also want to delete the workspace directory:cd <metarepo>/repos/<repo>/trunk && jj workspace forget <workspace-name>- If yes: remove
<metarepo>/repos/<repo>/<workspace>/ - If no: leave it (stale but harmless)
- Either way, notes survive at
<metarepo>/notes/<repo>/<workspace>/
- If yes: remove
- Report what was done.
Important
- Always resolve metarepo from
~/.claude/workspace-config.json, never hardcode paths. - ALWAYS confirm with the user before making changes.
- Never delete the notes directory — notes survive retirement.
- The
trunkworkspace should NEVER be retired. Refuse if the user tries. - Handle cases where the workspace directory is already gone.
- workspace.json is the source of truth, located at
notes/<repo>/<workspace>/workspace.json.
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.
- 3d ago First seen · 49 lines · 16 tokens per session scan A 38ec0a841702
retire is a command published in the GitHub repository mdsakalu/agent-plugins (4 stars, last pushed 3mo ago), licensed MIT. It adds 16 tokens to every session and 577 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-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.