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/dukbong/cc-save-plan/itgit clone --depth 1 https://github.com/dukbong/cc-save-planWhat 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.00008 | $0.00620 |
| Opus 5 | $0.00004 | $0.00310 |
| Sonnet 5 | $0.00002 | $0.00124 |
| Haiku 4.5 | $0.00001 | $0.00062 |
Grade A, and why
it 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Save Plan Command
Copy the latest auto-generated plan file from ~/.claude/plans/ to your project's .claude/plan/ directory.
Instructions
-
Validate Arguments
- Check if a plan name was provided via
$ARGUMENTS - If empty, respond with: "Usage: /stash:it <plan_name>"
- Extract the plan name from
$ARGUMENTS
- Check if a plan name was provided via
-
Sanitize Filename
- Remove special characters except alphanumeric, hyphens, and underscores
- Ensure the filename ends with
.mdextension - Example: "My Plan!" becomes "My-Plan.md"
-
Find Latest Plan File
- Search for the most recent
.mdfile in~/.claude/plans/ - Use:
ls -t ~/.claude/plans/*.md 2>/dev/null | head -1 - If no files found, respond with: "No plan files found in ~/.claude/plans/. Run /plan first."
- Search for the most recent
-
Create Target Directory
- Create
.claude/plan/in the current working directory if it doesn't exist - Use:
mkdir -p "$(pwd)/.claude/plan"
- Create
-
Check for Duplicate Files
- Check if a file with the same name already exists in
.claude/plan/ - If it exists, use AskUserQuestion to ask the user:
- Question: "A plan file named '[filename]' already exists. What would you like to do?"
- Options:
- "Overwrite the existing file"
- "Save with a new version number (e.g., plan-name-v2.md)"
- "Cancel the operation"
- Check if a file with the same name already exists in
-
Copy the File
- Based on user choice:
- Overwrite: Copy directly to
.claude/plan/[name].md - Version: Find the next available version number and save as
[name]-v[N].md - Cancel: Exit with message "Operation cancelled."
- Overwrite: Copy directly to
- Use:
cp "[source]" "$(pwd)/.claude/plan/[target].md"
- Based on user choice:
-
Confirm Success
- Respond with: "Plan saved successfully to .claude/plan/[filename].md"
- Include the full path for clarity
Example
User: /stash:it feature-implementation
Output:
Plan saved successfully to .claude/plan/feature-implementation.md
Full path: /home/user/project/.claude/plan/feature-implementation.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.
- 3d ago First seen · 68 lines · 8 tokens per session scan A 97200d001dce
it is a command published in the GitHub repository dukbong/cc-save-plan (2 stars, last pushed 7mo ago), licensed MIT. It adds 8 tokens to every session and 620 once invoked, about $0.0000 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.