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/jakerains/CitrusRulesWrote 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/jakerains/citrusrules/development-workflow)<a href="https://agentmods.dev/rules/jakerains/citrusrules/development-workflow"><img src="https://agentmods.dev/badge/rules/jakerains/citrusrules/development-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/jakerains/citrusrules/development-workflow"><img src="https://agentmods.dev/badge/rules/jakerains/citrusrules/development-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.00011 | $0.01482 |
| Opus 5.5 | $0.00004 | $0.00593 |
| Sonnet 5.5 | $0.00002 | $0.00296 |
| Haiku 4.5 | $0.00001 | $0.00148 |
Grade A, and why
development-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 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.
How it starts
The opening of the file, as written. The whole thing — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: DevelopmentWorkflowTracker type: Agent Requested description: Research, plan, implement, and track progress on new features with structured task lists and progress tracking based on Claude Code methodologies glob: **/*.{js,ts,tsx,jsx,py,java,go,rb,php} priority: high
Development Workflow Assistant
As your development assistant, I'll help build new features or components by following a structured approach based on advanced AI planning methodologies. This rule helps maintain consistent implementation workflows and thorough documentation.
Planning Strategy
I'll use extended thinking mode for complex planning. When you want more thorough analysis, prompt me with:
- "think" - Medium analysis depth
- "think hard" - Deep analysis with multiple considerations
- "ultrathink" - Maximum analysis for complex architectural decisions
5-Phase Development Workflow
Phase 1: Research & Discovery
- Understand Requirements: Clarify the feature scope, constraints, and success criteria
- Technical Analysis: Assess current architecture, dependencies, and integration points
- User Journey Mapping: Define how users will interact with this feature
- Risk Assessment: Identify potential challenges, blockers, and mitigation strategies
Phase 2: Planning & Architecture
- Technical Design: Create detailed implementation approach with architecture diagrams
- Task Breakdown: Split work into manageable, testable chunks with clear acceptance criteria
- Dependency Mapping: Identify what needs to be built first and integration requirements
- Timeline Estimation: Provide realistic effort estimates with buffer for unknowns
Phase 3: Implementation
- Environment Setup: Ensure development environment is ready with all dependencies
- Incremental Development: Build feature in small, testable increments
- Code Quality: Follow established patterns, add comprehensive tests, and document decisions
- Progress Tracking: Regular check-ins with clear status updates and blocker identification
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 · 163 lines · 11 tokens per session scan A 5dc7d0901614
development-workflow is a cursor rule published in the GitHub repository jakerains/CitrusRules (2 stars, last pushed 1y ago), licensed MIT. It adds 11 tokens to every session and 1,482 once invoked, about $0.0000 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.