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 agentmods add rules/carmentacollective/carmenta/autonomous-development-workflowgit clone --depth 1 https://github.com/carmentacollective/carmentaWrote 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/carmentacollective/carmenta/autonomous-development-workflow)<a href="https://agentmods.dev/rules/carmentacollective/carmenta/autonomous-development-workflow"><img src="https://agentmods.dev/badge/rules/carmentacollective/carmenta/autonomous-development-workflow.svg" alt="Measured on agentmods" 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 | $0.00008 | $0.00493 |
| Opus 5 | $0.00004 | $0.00246 |
| Sonnet 5 | $0.00002 | $0.00099 |
| Haiku 4.5 | $0.00001 | $0.00049 |
Grade A, and why
autonomous-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 3d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 3d ago First seen · 78 lines · 8 tokens per session scan A 2e7a0c075ffb
autonomous-development-workflow is a cursor rule published in the GitHub repository carmentacollective/carmenta (2 stars, last pushed 2mo ago), with no licence file. It adds 8 tokens to every session and 493 once invoked, about $0.0000 per session on Opus 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
trigger.advanced-tasks
Comprehensive rules to help you write advanced Trigger.dev tasks.
cursorrules
Do NOT invent repository facts. Before editing, run: npm run knowledge:context -- --task=" " and read .ai/local/current-context.md.
design-patterns
Design patterns (GoF) and file size conventions for sweagent TypeScript codebase.
long-running-agents
Best practices for long-running agents (initializer/coding pattern, incremental progress, clean state).
500-rule-organization-enforcer
WHEN adding or modifying rule files ENSURE they follow the established organization structure.
dev
This rule is triggered when the user types @dev and activates the Full Stack Developer agent persona.