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 agents/pdumicz/secret-shuttle/cursor-rules.examplegit clone --depth 1 https://github.com/pdumicz/secret-shuttleWhat 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.00000 | $0.00366 |
| Opus 5 | $0.00000 | $0.00183 |
| Sonnet 5 | $0.00000 | $0.00073 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
cursor-rules.example 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 yesterday.
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
Cursor Rules For Secret Shuttle
When working with production credentials, webhook signing secrets, API keys, or env var values:
- never put raw values in chat, files, logs, or screenshots
- use Secret Shuttle refs instead of raw values
- run
npx secret-shuttle initonce per project before the first secret operation - prefer
secret-shuttle provision(the magic path) — one approval to provision a project's secrets or a single--secret, with capture/inject driven for you - use
secret-shuttle provision --secret <NAME> --from random_32_bytesfor new secrets - to capture a secret revealed on a page,
secret-shuttle browser markthe controls thensecret-shuttle reveal-capture(blind mode is daemon-managed inside it) - to write a secret into a focused field,
secret-shuttle browser markthe field + submit control thensecret-shuttle inject-submit - verify with non-secret signals only —
secret-shuttle auditand ref fingerprints viasecret-shuttle secrets get-ref, never by revealing the value - do not inspect DOM, accessibility tree, console, network bodies, or clipboard while blind mode is active
- approve production actions in the Secret Shuttle window your browser opens — there is no CLI flag that bypasses approval
- use
secret-shuttle template run vercel-env-add ...to hand a secret to an external binary
Safe values to mention:
- refs such as
ss://stripe/prod/STRIPE_WEBHOOK_SECRET - fingerprints
- destination domains
- field names
- non-secret status
Unsafe values to mention:
whsec_...sk_live_...- service-role keys
- private tokens
- generated secret bodies
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.
- yesterday First seen · 32 lines · 0 tokens per session scan A 7027efc84f41
cursor-rules.example is an agent published in the GitHub repository pdumicz/secret-shuttle (4 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 366 tokens. 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.