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.
git clone --depth 1 https://github.com/waynesutton/markdown-siteWrote 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/rules/waynesutton/markdown-site/workflow)<a href="https://agentmods.dev/rules/waynesutton/markdown-site/workflow"><img src="https://agentmods.dev/badge/rules/waynesutton/markdown-site/workflow/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/waynesutton/markdown-site/workflow"><img src="https://agentmods.dev/badge/rules/waynesutton/markdown-site/workflow.svg" alt="Reviewed on agentmods" width="80" 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.00512 | $0.00512 |
| Opus 5.5 | $0.00205 | $0.00205 |
| Sonnet 5.5 | $0.00102 | $0.00102 |
| Haiku 4.5 | $0.00051 | $0.00051 |
Grade A, and why
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 1mo 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
Workflow
Before starting any non-trivial task (3+ steps or touches architecture)
- Stop. Write a PRD to
prds/<feature-name>.mdbefore touching code.- PRD files end in
.md, not.prd - Include: problem, proposed solution, files to change, edge cases
- For bug fixes: problem, root cause, fix, verification steps
- PRD files end in
- Add tasks to
TASK.mdunder## To Doas checkable items - If anything is unclear, ask before implementing
During implementation
- Work task by task. Mark
[x]as you go inTASK.md - Never mark a task complete without verifying it works
- Use subagents for research, exploration, and parallel analysis
- One task per subagent for focused execution
- When given a bug: just fix it. Find the root cause in logs/errors/types. No handholding needed.
- If something goes sideways: STOP and re-plan. Don't keep pushing.
- Before shipping: ask yourself "Would a staff engineer approve this?"
After every feature or fix
Always update both project docs. No exceptions:
TASK.md- Move completed items to## Completedwith bullet details and datechangelog.md- Add keepachangelog.com format entry. Rungit log --date=short -n 10for real dates. No placeholders, no future months.files.md- Update if new files were added or descriptions changed
Self-improvement
- After any user correction: note the pattern in
prds/lessons.mdto prevent repeat - If a fix feels hacky: pause and implement the elegant solution instead
- Simple obvious fixes: skip the reflection, just fix it
- Review
prds/lessons.mdat the start of sessions when relevant
PRD rules
- All PRDs live in
prds/folder - File name:
prds/<feature-or-problem-slug>.md - Extension is always
.mdnot.prd
Subagent strategy
- Offload research and exploration to subagents to keep the main context clean
- Throw more compute at complex problems via subagents
- Use one subagent per focused task, not one subagent for everything
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.
- 1mo ago First seen · 54 lines · 512 tokens per session scan A 2758b048c6f4
workflow is a cursor rule published in the GitHub repository waynesutton/markdown-site (627 stars, last pushed 4mo ago), licensed MIT. It adds 512 tokens to every session, about $0.0020 per session on Opus 5.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
coach
Agile Markdown coach mode. AI is the dev pair, the human is the product manager. Hard rules refuse, working agreements nudge.
md-feedback-workflow
This project uses md-feedback for structured human review of implementation plans.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.