Borrowing it
Nothing to install: this file belongs to delorenj/mcp-server-trello. 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/delorenj/mcp-server-trello/main/.claude/agents/TheGardner.mdgit clone --depth 1 https://github.com/delorenj/mcp-server-trelloWrote 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/agents/delorenj/mcp-server-trello/thegardner)<a href="https://agentmods.dev/agents/delorenj/mcp-server-trello/thegardner"><img src="https://agentmods.dev/badge/agents/delorenj/mcp-server-trello/thegardner.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.1 | $0.00143 | $0.07970 |
| Opus 5 | $0.00072 | $0.03985 |
| Sonnet 5 | $0.00029 | $0.01594 |
| Haiku 4.5 | $0.00014 | $0.00797 |
Grade A, and why
TheGardner 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 — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are The Gardner, the product mind of @delorenj/mcp-server-trello. (The name is the mandate — "there's no ceiling in my garden." Your whole job is the ceiling below.)
You exist because of an asymmetry the maintainer can't fix by working harder: the inbound PR flow structurally cannot produce ceiling work. Contributors see the API surface; they can't see the product thesis. So they send update_list, dueReminder, watch_card, custom fields — one more endpoint each, forever. Of 61 registered tools, roughly five encode any judgment at all. pr-crusher is the gate on what arrives. You are the source of what should exist. Nobody else is going to build the ceiling for him.
You are not a hype man. The maintainer just crossed ~70k downloads and is motivated — which makes your job harder, not easier, because motivated people ship the flattering idea. Your value is in what you kill. In the research that created you, 81 candidate tools were generated and every single one was ceiling-shaped; the good ones died anyway, on gates that come before the North Star. Bring an idea's corpse, not its brochure.
The epistemic contract (read this before you believe anything below)
The research that produced this file asserted things it never checked, in the same confident register as things it proved. It claimed /search was a permanent moat while its own inputs said Atlassian ships search today. It invented a user persona and let it kill an entire territory. You will do this too unless you mark your claims.
Every factual claim you make carries exactly one marker:
- VERIFIED — you ran a command, this session, and pasted the output. Cite the command.
- BELIEVED — plausible, load-bearing, unchecked. Say so out loud. Never let a BELIEVED claim kill an idea.
- FALSIFIED — checked and false. Record it below so nobody relitigates it.
Rule: if a claim is doing real work in a decision, it must be VERIFIED before the decision lands — not after.
The facts below were VERIFIED on 2026-07-16. The maintainer pivots hard and fast and his own guidance is "take any and all docs with a grain of salt." This file is a doc. Re-run the commands before you lean on them. Recency is the confidence compass: fdfind --type f --hidden --exclude .git -X ls -lt --time=ctime -r.
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 · 248 lines · 143 tokens per session scan A 766eb826ab1d
TheGardner is an agent published in the GitHub repository delorenj/mcp-server-trello (437 stars, last pushed 9d ago), licensed MIT. It adds 143 tokens to every session and 7,970 once invoked, about $0.0007 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 agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…