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/KlausFreiberufler/devflow-mcpWrote 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/klausfreiberufler/devflow-mcp/devflow)<a href="https://agentmods.dev/rules/klausfreiberufler/devflow-mcp/devflow"><img src="https://agentmods.dev/badge/rules/klausfreiberufler/devflow-mcp/devflow/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/klausfreiberufler/devflow-mcp/devflow"><img src="https://agentmods.dev/badge/rules/klausfreiberufler/devflow-mcp/devflow.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.00285 | $0.00285 |
| Opus 5.5 | $0.00114 | $0.00114 |
| Sonnet 5.5 | $0.00057 | $0.00057 |
| Haiku 4.5 | $0.00028 | $0.00028 |
Grade A, and why
devflow 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 2mo 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
DevFlow
This project uses DevFlow for structured AI development workflows.
Quick Start
devflow_status()→ check connection (browser opens for first auth)flow_list()→ find a free flow, ORflow_create({summary})to start onedevflow_init({flowId})→ begin your session — without this, edits are blocked- Follow
allowedActionsandnextStepfrom each tool response
Flow States
idea → planning → approval → ready → in_progress → review → done
Review states wait for user-approval in the DevFlow UI.
Iron Laws
- No code changes without active flow. Hooks block
apply_patch/edit/writeuntil.devflow-activeexists. - Plan first, code second. Submit
implementation_planviaflow_update({currentState: "approval"})before implementing. - TDD for changes that introduce behavior. Failing test → green → refactor.
- Knowledge-extend > create > defer > NEVER dismiss. When the wiki has a relevant ADR/pattern, extend it instead of creating a new one.
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.
- 2mo ago First seen · 32 lines · 285 tokens per session scan A ad116d1d3ef4
devflow is a cursor rule published in the GitHub repository KlausFreiberufler/devflow-mcp (1 stars, last pushed 2mo ago), licensed MIT. It adds 285 tokens to every session, about $0.0011 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-31.
Other cursor rules, from other repositories
slice-tasks
PLANNING SPINE STEP 2 of 3 — Slice the work: break a scoped PRD into vertical-slice stories in specs/epics/. Use after scope-work (step 1), before plan-work (step 3). Not a substitute for scope-work or plan-work.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
elite-orchestrator
Elite orchestrator for mission-critical, enterprise-scale tasks requiring strategic coordination of 7+ agents across all domains. Makes architectural decisions, manages risk, ensures business continuity, and delivers enterprise-grade outcomes. Use for platform migrations, security incidents, multi-system integrations…
project-onboarding-rule
Automatically onboards existing projects into the AI-driven development workflow.
linear-in-review
After finishing a Linear issue, set its status to In Review (never Done).
sprint-planning
BMAD BMM Agent: sprint-planning.