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 skills add atlassian/trello-mcp-server --skill trello-usegit clone --depth 1 https://github.com/atlassian/trello-mcp-serverWrote 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/atlassian/trello-mcp-server/trello-use)<a href="https://agentmods.dev/skills/atlassian/trello-mcp-server/trello-use"><img src="https://agentmods.dev/badge/skills/atlassian/trello-mcp-server/trello-use.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00084 | $0.01825 |
| Opus 5 | $0.00042 | $0.00912 |
| Sonnet 5 | $0.00017 | $0.00365 |
| Haiku 4.5 | $0.00008 | $0.00183 |
Grade A, and why
trello-use 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 8d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trello MCP Server — Usage Skill
Trello MCP tools are action-dispatched (action: "..." selects the operation) and validate strictly: a field not used by the chosen action is rejected, not ignored.
1. Identify the current user first
Call trelloReadMember with action: "get_me" to get the authenticated user's profile, including prefs.timezone. Do this before any relative-time request ("today", "this week") for cards, Inbox, and search — most concretely, before trelloWriteCard/trelloWriteInbox create or update when the user gives a due date/time in local or relative terms (e.g. "tomorrow 1pm"): resolve prefs.timezone first, convert to UTC, then pass that as due. (Planner events use a different timezone source — see §3.)
2. ARI id format (critical — read before passing any id)
Every id-typed parameter (cardId, boardId, listId, workspaceId, checklistId, itemId, labelId, plannerCalendarId, providerAccountId) is an ARI, not a raw Trello object id. Most are workspace-scoped and follow this shape:
ari:cloud:trello::<entity>/workspace/<workspaceObjectId>/<entityObjectId>
The two exceptions (last two rows below) are not workspace-scoped: planner calendar has no workspace segment, and a third-party account is a different ARI namespace.
| Entity | Shape |
|---|---|
| board | ari:cloud:trello::board/workspace/<workspaceObjectId>/<boardObjectId> |
| card | ari:cloud:trello::card/workspace/<workspaceObjectId>/<cardObjectId> |
| list | ari:cloud:trello::list/workspace/<workspaceObjectId>/<listObjectId> |
| checklist | ari:cloud:trello::checklist/workspace/<workspaceObjectId>/<checklistObjectId> |
| check item | ari:cloud:trello::check-item/workspace/<workspaceObjectId>/<itemObjectId> |
| label | ari:cloud:trello::label/workspace/<workspaceObjectId>/<labelObjectId> |
| workspace | ari:cloud:trello::workspace/<workspaceObjectId> |
| planner calendar | ari:cloud:trello::planner-calendar/<calendarObjectId> (no workspace segment) |
| third-party account | ari:third-party:<provider>::account/<providerAccountId> (e.g. Google) |
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.
- 8d ago First seen · 83 lines · 84 tokens per session scan A a9140887c661
trello-use is a skill published in the GitHub repository atlassian/trello-mcp-server (51 stars, last pushed 11d ago), licensed Apache-2.0. It adds 84 tokens to every session and 1,825 once invoked, about $0.0004 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-30.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.