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 plugins/hedde/trigger_tree/marketplace/plugin marketplace add Hedde/trigger_treegit clone --depth 1 https://github.com/Hedde/trigger_treeGrade A, and why
trigger-tree 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 yesterday.
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": "trigger-tree",
"owner": {
"name": "Hedde van der Heide",
"url": "https://github.com/Hedde"
},
"description": "See which docs your AI actually discovers \u2014 local documentation telemetry for Claude Code",
"plugins": [
{
"name": "trigger-tree",
"displayName": "trigger-tree",
"version": "1.30.0",
"source": "./",
"description": "Local, zero-token documentation discovery: live dashboard, heat maps, router fixes, and setup diagnostics",
"category": "documentation",
"tags": [
"docs",
"telemetry",
"observability"
]
}
]
}
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.
- yesterday First seen · 24 lines scan A 34c431ea6a20
trigger-tree is a plugin published in the GitHub repository Hedde/trigger_tree (14 stars, last pushed 8d 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-30.
Other plugins, from other repositories
claude-code-plugin
Use Datadog directly in Claude Code through a preconfigured Datadog MCP server. Query logs, metrics, traces, dashboards, and more through natural conversation. This plugin is in preview.
slideops
Plugin marketplace listing 1 plugin: slideops.
slideops
Turn a repository into a slide deck, then find out the day it stops matching the code. Ships slideops (repo to deck, with citation-based freshness checking) and slides-to-pdf (any hash-navigated HTML deck to a verified PDF).
magnifito
Plugin marketplace listing 1 plugin: ai-doc-system.
ai-doc-system
Tier a repository's docs by authority, validate frontmatter, generate an agent-readable index, and enforce it with a blocking gate.
han-communication
Foundational communication plugin for the Han suite. Owns the canonical readability standard, the writing-voice profile, and the explanation standard for talking to a reader who will not implement the work, plus the readability-guidance skill that surfaces the first two into a calling skill's own context for in-voice…