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.
git clone --depth 1 https://github.com/trustmybot/pluginWrote 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/plugins/trustmybot/plugin/marketplace)<a href="https://agentmods.dev/plugins/trustmybot/plugin/marketplace"><img src="https://agentmods.dev/badge/plugins/trustmybot/plugin/marketplace/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/plugins/trustmybot/plugin/marketplace"><img src="https://agentmods.dev/badge/plugins/trustmybot/plugin/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
trustmybot marketplace 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 1mo 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.
What it actually says
{
"name": "trustmybot",
"metadata": {
"description": "LEGACY marketplace catalog — kept for backward compat. New installs should use trustmybot/marketplace (stable) or trustmybot/marketplace-rc (RC) instead. See https://github.com/trustmybot/plugin for the canonical stable channel."
},
"owner": {
"name": "trustmybot",
"url": "https://github.com/trustmybot"
},
"plugins": [
{
"name": "tmb",
"source": {
"source": "url",
"url": "https://github.com/trustmybot/plugin.git",
"ref": "main"
},
"description": "TMB multi-agent Claude Code plugin with SQLite trajectory MCP — STABLE channel (tags from main branch only)."
},
{
"name": "tmb-rc",
"source": {
"source": "url",
"url": "https://github.com/trustmybot/plugin.git",
"ref": "rc"
},
"description": "TMB release-candidate channel — points at the 'rc' branch which is fast-forwarded to whichever vX.Y.Z-rc.N tag is currently being validated. Install only if you want to test pre-release builds and tolerate breakage. Promotes to 'tmb' (main) once validated."
}
]
}
The plugins it lists here
This marketplace lists 1 plugin kept in the same repository. Each has its own page, its own measurements and its own install command.
What ships with it
1 file beside marketplace.json 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.
- 1mo ago First seen · 31 lines scan A 38adbcd0a702
trustmybot marketplace is a plugin published in the GitHub repository trustmybot/plugin (6 stars, last pushed 3d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
ci-review
CI-optimized code review: multi-agent parallel review with confidence scoring and atomic GitHub PR review posting via gh api.
relay
Delegate work packets from a lead Claude Code session to executor sessions in their own iTerm tabs, with session reuse instead of always spawning fresh.
agent-harness
Multi-agent harness for Claude Code: Planner→Generator→Evaluator sprints executed as background dynamic workflows (Agent-tool fallback), fable/opus/sonnet/haiku model routing with per-role reasoning effort, harness-engineering framework for design/diagnosis, and Anthropic 2026-04-04 P-G-E pattern.
erpaval
ERPAVal — autonomous software development workflow for Claude Code. Comprehensive standalone bundle: the erpaval workflow plus 10 vendored companion skills (product-discovery, research, ultraplan, tech-stack-builder, product-strategy, working-backwards, customer-research, meta-prompt-optimizer, product-design-shared…
hato
Carrier-pigeon messaging between Claude Code sessions — send messages and files, and get woken up by other sessions across your machines.
orodruin-labs marketplace
Plugin marketplace listing 1 plugin: nazgul.