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 skills/mih-nig-afe/mcp-dev-loop-trello-cursor-github/trello-dev-loopnpx skills add Mih-Nig-Afe/MCP-Dev-Loop-Trello-Cursor-GitHub --skill trello-dev-loopgit 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.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.00058 | $0.00742 |
| Opus 5 | $0.00029 | $0.00371 |
| Sonnet 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 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.
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.
- 3d 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 2mo ago), licensed MIT. It adds 58 tokens to every session and 742 once invoked, about $0.0003 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 skills, from other repositories
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
commit-push-pr
Commit selected local changes, push the branch, and create or update a GitHub pull request with BitFun attribution. Use when the user asks to 提交 PR、提代码、commit and push、开 PR、create a pull request, or wants a Claude Code-like one-command PR publishing flow from BitFun.
commit
Create a git commit with changeset enforcement.
commit
Create structured git commits by analyzing staged and unstaged changes and grouping them logically into one or more commits with clear, descriptive messages. Use when the user asks to commit, says "commit this" or "commit my changes", wants help writing a commit message, or has finished a chunk of work that needs…
git-commit
Creates git commits following Conventional Commits format with type/scope/subject and detailed markdown body. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md. Each change type gets its own markdown heading (# emoji + type), with…
commit
Stage and commit changes using conventional commits format.