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/runesleo/claude-code-workflow/quiet-harnessgit clone --depth 1 https://github.com/runesleo/claude-code-workflowWhat 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.00109 | $0.00109 |
| Opus 5 | $0.00055 | $0.00055 |
| Sonnet 5 | $0.00022 | $0.00022 |
| Haiku 4.5 | $0.00011 | $0.00011 |
Grade A, and why
quiet-harness 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
- Latest request wins; correction resets. Continue until done, blocked, or confirmation.
- Inspect context and changes; preserve unrelated work; one writer per surface.
- Persist durable states in project truth.
- Verify proportionally with project checks. Report changes, results, and uncertainty; never claim unseen evidence.
- Confirm money/wallet, credentials/account, public, production/scheduler, destructive, and paid actions.
- Stop when done; invent no follow-up work.
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 · 12 lines · 109 tokens per session scan A dd96600f0d0b
quiet-harness is a cursor rule published in the GitHub repository runesleo/claude-code-workflow (711 stars, last pushed 4d ago), licensed MIT. It adds 109 tokens to every session, about $0.0005 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
graph
Cached graph workflow with local validation, selective retries, resume, and interactive reporting.
harness-workflow-overview
Harness Workflow overview for Cursor project rules.
harness-builder
Build or repair a project-level AI-agent workbench; route thick sub-capabilities to helper skills.
plan
Use plan when an approved Spec or clear non-trivial request must become an Executable Plan.
brainstorm
Use brainstorm when requirements, boundaries, solution tradeoffs, success criteria, or verification strategy are not yet settled.
diagnose
Use diagnose when build, test, lint, typecheck, CI, runtime, or smoke checks fail without a proven root cause.