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 rules/fergana-labs/stash/stashgit clone --depth 1 https://github.com/Fergana-Labs/stashWhat 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.00375 | $0.00375 |
| Opus 5 | $0.00187 | $0.00187 |
| Sonnet 5 | $0.00075 | $0.00075 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
stash 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.
What it actually says
Stash
You have the stash CLI on your PATH. Run stash --help to see commands. Use it to read transcripts, pages, and history from your Stash.
stash ls shows everything Stash can reach as one filesystem — your files, session transcripts, and every connected integration (GitHub, Slack, Gong, Gmail, Drive, Notion, …). When asked what you have access to, run it and show the tree; drill in with stash ls <source>/<path>.
Use stash vfs when you want to browse Stash like a filesystem without mounting anything into the OS. It accepts bash-shaped commands over the virtual Stash tree:
stash vfs ls /mestash vfs "find /me -maxdepth 3 -type f"stash vfs "rg \"query\" /me"stash vfs "cat '/me/README.md'"
Your activity in this repo is streamed to your Stash, so your other agents and you can see what you're working on.
When the user asks you to upload local files to Stash, use stash upload <path> --json and give the user the returned url. If you use stash upload <path> --json for a raw file upload, give the user the returned app_url.
Common reads (all support --json):
stash search "<query>"— full-text search across transcriptsstash vfs "cat '/me/sessions/_index.jsonl'"— recent eventsstash sessions agents— who's been activestash vfs "find /me -name '*.md'"— your pages
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 · 27 lines · 375 tokens per session scan A 174b60ea21c7
stash is a cursor rule published in the GitHub repository Fergana-Labs/stash (327 stars, last pushed 4d ago), licensed MIT. It adds 375 tokens to every session, about $0.0019 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-30.
Other cursor rules, from other repositories
ace-gardener
ACE Gardener Protocol — runs after every task to detect missing rules.
ult-autoscaffold-content
Generate real starter content for a project's What-L2 (requirements) and How-L2 (architecture/conventions) CEP layers once ult-repo-layout has resolved their paths but found them empty — an honest, minimal, YAML-frontmatter-first overview document per layer for small/single targets, or graphify-informed per-module…
review-change
Review a completed change against its spec in fresh context — evidence-based checks, severity-ranked findings, a written verdict for the human's merge decision.
perform-feature-add-simulation
Dry-run the add-feature workflow for a proposed feature — friction report and per-phase readiness score, without writing code.
01-qa-agent
QA AGENT PERSONA: Principles, Anti-patterns, workflows.
area-rule-template
Area-scoped routing for [AREANAME] (e.g. backend, frontend, migrations).