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/hlalljie/agent-workflow-presetsWrote 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/hlalljie/agent-workflow-presets/documentation)<a href="https://agentmods.dev/rules/hlalljie/agent-workflow-presets/documentation"><img src="https://agentmods.dev/badge/rules/hlalljie/agent-workflow-presets/documentation/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/hlalljie/agent-workflow-presets/documentation"><img src="https://agentmods.dev/badge/rules/hlalljie/agent-workflow-presets/documentation.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.00525 | $0.00525 |
| Opus 5.5 | $0.00210 | $0.00210 |
| Sonnet 5.5 | $0.00105 | $0.00105 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
documentation 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 6d 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
Where information goes
Lasting docs live in README.md, docs/, and .env.example. Working docs (plans, research, open questions, plan decisions) live in .cursor/plans/ and follow workflow.mdc. Lasting docs never link to working docs, because plans move.
Put each piece of information in exactly one of these:
- What the project is and how to run it —
README.md - Where things live —
docs/folder-structure.md. It is also the list of every doc in the project. - Why a choice was made —
docs/decisions.md(format inworkflow.mdc) - How it works now —
docs/architecture.md: Overview, Parts, Flows, Constraints. Current state only, no history. - How to do one ops task (deploy, rollback, restore) —
docs/runbooks/<task>.md - Environment variables —
.env.exampleonly, one comment per variable - A part that outgrows
architecture.md—docs/<domain>/(README.mdfor Parts,dataflow.mdfor Flows), only when listed indocs/folder-structure.md. Propose the split; do not do it unprompted.
Create architecture.md, runbooks/, and a missing doc on first use, from the templates in write-docs, and list each in docs/folder-structure.md in the same change. Never create an empty doc, and never add a new kind of doc: if information fits none of the above, say so.
Keeping docs current
- Update docs in the same change as the code, yourself. A change needs a doc update if it changes where things live, a decision, a flow or boundary in
architecture.md, an ops step or env var, or what the project is or how to run it. write-docs has the checklist. - Each fact lives in one doc. Link to it; do not copy it.
- Delete what is no longer true. Do not leave it marked outdated.
- Comments in code say why, not what, in any language. Syntax is in
code-documentation.mdc. Markdown style is inmarkdown-formatting.mdc.
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.
- 6d ago First seen · 28 lines · 525 tokens per session scan A 752a678920e4
documentation is a cursor rule published in the GitHub repository hlalljie/agent-workflow-presets (2 stars, last pushed 6d ago), licensed MIT. It adds 525 tokens to every session, about $0.0021 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-10-10.
Other cursor rules, from other repositories
scrum-master
Scrum Master agent (Bob).
context-discipline
Manage AI context window efficiently - read before write, no re-reads, tool-call budgets, one-pass discipline.
swamr-state-manager
Swamr State Manager — tracks task progress, manages the execution pipeline, handles retries and escalation. Maintains swamr/state.json as the single source of truth for swarm progress.
pn-plugin-quality-gates
Keep Cursor plugin manifests, paths, and component metadata valid during plugin authoring.
github-repo-triage
Triage and maintain GitHub repos — issues, PRs, cherry-picks, releases, publishing.
task_structure_example.mouse
TaskID: MOUSE#TASK0001 # Example. MUST be unique & sequential. Title: "Example Task: Process User Survey Data and Generate Insights Report" Description: | This task involves processing raw user survey data, performing analysis, and generating a comprehensive insights report.