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 skills add usrrname/cursorrules --skill dev-workflowgit clone --depth 1 https://github.com/usrrname/cursorrulesWrote 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/skills/usrrname/cursorrules/dev-workflow)<a href="https://agentmods.dev/skills/usrrname/cursorrules/dev-workflow"><img src="https://agentmods.dev/badge/skills/usrrname/cursorrules/dev-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/skills/usrrname/cursorrules/dev-workflow"><img src="https://agentmods.dev/badge/skills/usrrname/cursorrules/dev-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.00030 | $0.01435 |
| Opus 5.5 | $0.00012 | $0.00574 |
| Sonnet 5.5 | $0.00006 | $0.00287 |
| Haiku 4.5 | $0.00003 | $0.00144 |
Grade A, and why
dev-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.
How it starts
The opening of the file, as written. The whole thing — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lean and Agile Development Workflow Standards
This rule defines the workflow for AI agents to follow when implementing features from user stories, focusing on lean development principles and agile methodologies.
Critical Rules
- AI agents should read from the latest user story in
.cursor/.ai/that is not of "Done" or "Blocked" status. - No more than 2 stories or spikes can be in progress at any time.
- Break down complex problems into a manageable task list and update the relevant user story or task with this list
- Check off tasks one by one as they are completed
- Assist with fixing errors in the code
- Follow test-driven development when appropriate
- Maintain continuous communication with the user about progress
- If linting or committing fails, do not retry.
filters:
- type: file_extension pattern: "\.(js|ts|jsx|tsx|md)$"
- type: content pattern: "user story|feature request|backlog item"
actions:
- type: suggest
message: |
Follow the lean-agile workflow pattern:
- Break down the user story into atomic tasks
- Prioritize tasks based on dependencies
- Based on user goals and acceptance criteria, create a list of test cases and edge cases with scenarios for testing the business-critical functionality. This must be approved by the user.
- Implement each task incrementally
- Write tests and ensure they pass before moving to the next task
- Refactor as needed
- Maintain communication with the user
metadata: priority: high version: 1.0
Workflow Process
1. User Story Analysis
When given a user story or feature request:
- Mark the corresponding user story to
Status: In Progress - Read and analyze the user story requirements
- Break down the story into actionable tasks
- Check if any existing components or utilities can be reused
- Writing scenarios and expected outcomes.
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 · 182 lines · 30 tokens per session scan A 5ac706c27d20
dev-workflow is a skill published in the GitHub repository usrrname/cursorrules (11 stars, last pushed 6mo ago), licensed ISC. It adds 30 tokens to every session and 1,435 once invoked, about $0.0001 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 skills, from other repositories
analyze
Deep codebase analysis — complexity, coupling, dead code, tech debt hotspots.
explore
Read-only codebase exploration — understand structure, data flow, and conventions before changing anything.
incident
Production incident response — structured triage, hypothesis tree, safe remediation, incident record.
review
Code review checklist — catch bugs, security issues, and design problems before merging.
autopilot
Fully autonomous execution — clarify, plan, and execute without interruption.
chaos
Failure injection — stress test implementations under hostile conditions before shipping.