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/amirsoleimani/claude-stash/pushgit clone --depth 1 https://github.com/AmirSoleimani/claude-stashWrote 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/amirsoleimani/claude-stash/push)<a href="https://agentmods.dev/commands/amirsoleimani/claude-stash/push"><img src="https://agentmods.dev/badge/commands/amirsoleimani/claude-stash/push.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.1 | $0.00009 | $0.00187 |
| Opus 5 | $0.00005 | $0.00093 |
| Sonnet 5 | $0.00002 | $0.00037 |
| Haiku 4.5 | $0.00001 | $0.00019 |
Grade A, and why
push 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 5d 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
Append the following item to .claude/stash.md in the current project.
Steps:
- If
.claude/stash.mddoes not exist, create it with this header:# Stash - Append a new line at the end of the file in this exact format:
Use today's date and the current time (24h, local).- [YYYY-MM-DD HH:MM] <item text> - Do not modify, renumber, or reorder any existing lines.
- Respond with a single short confirmation, e.g.
Pushed to stash (5 items total).— include the current total count.
Important: Do not start working on the item. The user is capturing it to handle later.
Item: $ARGUMENTS
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.
- 5d ago First seen · 24 lines · 9 tokens per session scan A f42366441cfb
push is a command published in the GitHub repository AmirSoleimani/claude-stash (10 stars, last pushed 3mo ago), licensed MIT. It adds 9 tokens to every session and 187 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
cc-spec
(Conductor) Define the problem and generate an approved spec.
cc-plan
(Conductor) Map implementation steps from an approved spec.
cc-resume
(Conductor) Restore full session context in a fresh Claude Code session.
cc-init
(Conductor) Initialize or re-sync the project environment.
cc-review
(Conductor) Review code changes against spec and standards.
cc-debug
(Conductor) Systematically diagnose and fix a bug.