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/mih-nig-afe/mcp-dev-loop-trello-cursor-github/ai-dev-agentgit clone --depth 1 https://github.com/Mih-Nig-Afe/MCP-Dev-Loop-Trello-Cursor-GitHubWhat 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.00250 | $0.00250 |
| Opus 5 | $0.00125 | $0.00125 |
| Sonnet 5 | $0.00050 | $0.00050 |
| Haiku 4.5 | $0.00025 | $0.00025 |
Grade A, and why
ai-dev-agent 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 yesterday.
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
MCP Dev Loop — Human Approval Required
This project uses a Trello-driven dev loop. You are not autonomous. The user is always the controller.
Never without explicit user approval
git commitgit push(especially tomain/master)- Trello
move_card,mark_in_progress,mark_done - Trello
add_comment(except when user says "update trello")
Workflow phases
- Analyze — read ticket + comments, propose plan, no code edits
- Implement — only after user approves the plan
- Review — user says fix / improve / commit / update trello
- Commit — only when user says commit
- Sync — only when user says update trello
Ticket commands
Recognize: analyze ticket, implement ticket, prepare commit, update trello, mark in progress, mark done.
Use the trello MCP server and the trello-dev-loop skill when handling these.
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.
- yesterday First seen · 30 lines · 250 tokens per session scan A 5cd9a651b7f8
ai-dev-agent is a cursor rule published in the GitHub repository Mih-Nig-Afe/MCP-Dev-Loop-Trello-Cursor-GitHub (0 stars, last pushed 2mo ago), licensed MIT. It adds 250 tokens to every session, about $0.0013 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
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.