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/yeominux/md-feedback/md-feedback-workflowgit clone --depth 1 https://github.com/yeominux/md-feedbackWhat 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.00333 | $0.00333 |
| Opus 5 | $0.00167 | $0.00167 |
| Sonnet 5 | $0.00067 | $0.00067 |
| Haiku 4.5 | $0.00033 | $0.00033 |
Grade A, and why
md-feedback-workflow 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 2d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 2d ago First seen · 48 lines · 333 tokens per session scan A 411c20ea29a0
md-feedback-workflow is a cursor rule published in the GitHub repository yeominux/md-feedback (5 stars, last pushed 5mo ago), with no licence file. It adds 333 tokens to every session, about $0.0017 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 cursor rules, from other repositories
skill-and-agent-references
Reference skills, agents, and commands by their registered name (never by filesystem path), and decompose oversized commands or agents by extracting sections into skills with by-name references.
spec-implementation-hygiene
Keep production code free of spec/phase metadata and back-compat shims; capture migrations in spec-local upgrade scripts instead.
coding-standards-demo.crux
Team coding standards and best practices.
zip-contents-protection.crux
⟦CRUX:zip-contents-protection.md P.⊛{¬auto-Δ scripts/create-crux-zip.py w/o user req!}.
savee
Use the Savee MCP tools when the task involves design inspiration, visual references, moodboards, or the user's own saved work.
no-crux-frontmatter
This is a regular rule file that does not have crux: true in its frontmatter. It should be ignored by the CRUX compression hook.