Borrowing it
Nothing to install: this file belongs to enthouan/trello-mcp. 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/enthouan/trello-mcp/main/.agents/skills/trello-mcp-release/SKILL.mdgit clone --depth 1 https://github.com/enthouan/trello-mcpWrote 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/enthouan/trello-mcp/trello-mcp-release)<a href="https://agentmods.dev/skills/enthouan/trello-mcp/trello-mcp-release"><img src="https://agentmods.dev/badge/skills/enthouan/trello-mcp/trello-mcp-release/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/enthouan/trello-mcp/trello-mcp-release"><img src="https://agentmods.dev/badge/skills/enthouan/trello-mcp/trello-mcp-release.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.00056 | $0.02588 |
| Opus 5 | $0.00028 | $0.01294 |
| Sonnet 5 | $0.00011 | $0.00518 |
| Haiku 4.5 | $0.00006 | $0.00259 |
Grade A, and why
trello-mcp-release 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 10d 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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trello MCP Release
Guardrails
mainis protected. Do not commit or push directly tomain; all file changes must land through a PR.- The user's review of the release PR is the only normal approval boundary. After opening the release PR, ask the user to review that exact PR and wait for their approval.
- Once the user says the release PR is reviewed or approved, continue automatically for that exact
vX.Y.Z: wait for required checks, merge it, push the tag, verify workflows/GHCR, create the GitHub Release, and close the milestone. Do not ask separately for merge approval or publish approval. - Do not move, delete, or retag existing release tags.
- In this repo, the normal release artifact is an annotated Git tag, GHCR images, and a GitHub Release titled exactly
vX.Y.Z. - Release tags should point at the current
origin/maincommit after the release prep PR has merged. - Keep secrets out of commits, logs, PR text, and release notes.
Refresh State
Run these first:
git fetch --prune --tags origin
git status --short --branch
git log --oneline --decorate -n 10 origin/main
gh pr list --repo enthouan/trello-mcp --state open --json number,title,url,isDraft
gh issue list --repo enthouan/trello-mcp --state all --limit 300 \
--json number,title,state,milestone,projectItems,url
gh api repos/enthouan/trello-mcp/milestones --paginate \
--jq '.[] | {number,title,state,open_issues,closed_issues,description}'
gh run list --repo enthouan/trello-mcp --branch main --limit 10 \
--json databaseId,name,headSha,status,conclusion,createdAt,url
gh release list --repo enthouan/trello-mcp --limit 10
git tag --list 'v*.*.*' --sort=-v:refname | head -n 10
gh workflow view Release --repo enthouan/trello-mcp --yaml
Then choose the target version from the current package.json, CHANGELOG.md,
existing tags, merged work, and semver impact. Stop if the target vX.Y.Z tag
or GitHub release already exists.
If the release maps to a GitHub milestone or roadmap slice, confirm that there are no open milestone issues and that related project items are in a completed state before preparing the PR.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 233 lines · 56 tokens per session scan A 7098909c90ba
trello-mcp-release is a skill published in the GitHub repository enthouan/trello-mcp (4 stars, last pushed today), licensed MIT. It adds 56 tokens to every session and 2,588 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
github
GitHub via gh CLI: PRs, issues, reviews, repos, auth.
goal-release
Cut a release end to end: use the draft-release skill to open the release PR and draft GitHub release, wait for CI to turn green, run the merge-pr skill to merge the release PR, then update the Homebrew formula from the published release assets. Use when the user wants to draft and merge a release in one go, or…
taiyi-integration
A project workflow skill for closing a TaiyiForge change and recording it in a CHANGELOG.md file. It checks review results, tests, and the state of the working tree before archiving the change.
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…
release-pr-review
Review pass on an open release PR (release/ → main) — the step between git-wrapup and release-and-publish when a project releases in gated release PR mode. Reads the PR's commit range through the code-simplifier lens plus a correctness review, verifies whatever an automated reviewer left on the PR, lands fixes as…
parallel-pr-review
Use when asked to "review the open PRs", review a batch or stack of pull requests, or run a recurring PR-review pass on a repo — especially with many PRs, stacked branches, conflicts, or security-sensitive changes. Covers grouping, fan-out to review subagents, verdict synthesis, and posting.