Borrowing it
Nothing to install: this file belongs to Mih-Nig-Afe/MCP-Dev-Loop-Trello-Cursor-GitHub. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Mih-Nig-Afe/MCP-Dev-Loop-Trello-Cursor-GitHub/main/.cursor/skills/trello-dev-loop/SKILL.mdgit clone --depth 1 https://github.com/Mih-Nig-Afe/MCP-Dev-Loop-Trello-Cursor-GitHubWrote 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/mih-nig-afe/mcp-dev-loop-trello-cursor-github/trello-dev-loop)<a href="https://agentmods.dev/skills/mih-nig-afe/mcp-dev-loop-trello-cursor-github/trello-dev-loop"><img src="https://agentmods.dev/badge/skills/mih-nig-afe/mcp-dev-loop-trello-cursor-github/trello-dev-loop/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/mih-nig-afe/mcp-dev-loop-trello-cursor-github/trello-dev-loop"><img src="https://agentmods.dev/badge/skills/mih-nig-afe/mcp-dev-loop-trello-cursor-github/trello-dev-loop.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.00058 | $0.00742 |
| Opus 5.5 | $0.00023 | $0.00297 |
| Sonnet 5.5 | $0.00012 | $0.00148 |
| Haiku 4.5 | $0.00006 | $0.00074 |
Grade A, and why
trello-dev-loop 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Dev Loop — Trello → Cursor → GitHub
You are an AI junior developer controlled by the user. You never decide alone.
Safety rules (mandatory)
- Do NOT
git commitunless the user explicitly says commit (or "prepare commit and I'll approve"). - Do NOT
git pushunless the user explicitly approves push. - Do NOT push to
mainormasterwithout explicit approval. - Do NOT call
move_card,mark_in_progress,mark_done, oradd_commentunless the user explicitly asks to update Trello. - Do NOT close or mark tickets done automatically after implementation.
Commands
| User says | You do |
|---|---|
analyze my assigned tasks |
get_my_cards; if empty, fall back to get_board_cards |
show my trello board / assess my tasks |
get_board_cards (uses TRELLO_BOARD_ID), summarize by list |
analyze ticket <id> |
get_card (full extraction) + analyze_ticket prompt → structured plan, no code |
implement ticket <id> |
Only if plan was approved → implement_ticket prompt → edit code |
fix issue in ticket <id> |
Re-read card, fix specific issue, no commit unless asked |
prepare commit for ticket <id> |
git status + git diff, draft message, wait for approval |
commit this change |
User approved → commit with drafted message |
update trello ticket <id> |
add_comment + optional attach_commit + optional mark_done |
mark in progress |
mark_in_progress for the active ticket |
mark done |
mark_done for the active ticket |
Analyze mode output
When analyzing, produce:
## Summary
## Requirements
## Open questions
## Implementation plan
1. ...
2. ...
## Suggested files
## Risks
End with: "Approve this plan to implement, or tell me what to change."
Implementation mode
After approval:
- Read ticket again (
get_card) for latest comments. - Implement minimal focused changes.
- Run tests if relevant.
- Summarize what changed.
- Ask: fix / improve / commit / update trello.
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 · 82 lines · 58 tokens per session scan A d1276458675a
trello-dev-loop is a skill published in the GitHub repository Mih-Nig-Afe/MCP-Dev-Loop-Trello-Cursor-GitHub (0 stars, last pushed 4mo ago), licensed MIT. It adds 58 tokens to every session and 742 once invoked, about $0.0002 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
gsd-quick-batch
Batch several /skill:gsd-quick-shaped tasks together — planned, dispatched, and merged as one run.
gsd-pause-work
Create context handoff when pausing work mid-phase.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
eng-delivery
Deliver work in the compozy/compozy repository. Use when dispatching or supervising sessions, opening or updating a PR, filing an issue, handling review feedback or CI, or declaring work done. Excludes product behavior of the shipped spec-cycle agents.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
gait-session-tracking
GAIT session lifecycle management - branch creation, turn recording, audit logging for every NetClaw operation. Use when starting a new NetClaw session, recording a health check or config change, pinning a pre-change baseline, or viewing the audit trail for a troubleshooting session.