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 skills/hedde/trigger_tree/ttnpx skills add Hedde/trigger_tree --skill ttgit clone --depth 1 https://github.com/Hedde/trigger_treeWhat 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 | $0.00074 | $0.03128 |
| Opus 5 | $0.00037 | $0.01564 |
| Sonnet 5 | $0.00015 | $0.00626 |
| Haiku 4.5 | $0.00007 | $0.00313 |
Grade A, and why
tt 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 2d 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 — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/tt — trigger-tree
Execute the subcommand in $1 (option/text in $2 and beyond; $ARGUMENTS holds everything).
Output discipline — the most important rule: work silently. No plan up front, no intermediate status lines, no explanation of what you are about to do or just did. Execute the steps and show only the end result in the format specified per subcommand below. Report an error in exactly one line.
Terminology — maturity model: a file with zero reads is untouched, never "dead".
Only when the stats JSON reports maturity: "mature" may untouched files be presented
as dead-path candidates. During cold-start and warming the measurement is simply
too young to judge.
Scripts live in ${CLAUDE_PLUGIN_ROOT}/scripts/. Project data lives in
${CLAUDE_PROJECT_DIR}/.trigger-tree/.
$1 = "help" or empty
Show exactly this, nothing above or below it:
🌳 trigger-tree — measures which documentation your agents actually use
Command Does /tt statusSnapshot: current heat, lifetime reads, untouched paths /tt watchLive dashboard; recency colors, heat bars, injected context, privacy settings, and focus/hot/cold/A–Z/Z–A sorting /tt watch demoDashboard with synthetic events (writes nothing) /tt watch replayDashboard replaying the real history, accelerated /tt insightsAnalysis report: heat/cold map, untouched paths, hunting, trend + HTML /tt instructionsPer-directive adherence, observability, and always-loaded cost /tt suggestionsMax 5 prioritized, concrete router fixes — apply after confirmation /tt badgeWrite .trigger-tree/badge.json; immature data publishes onlymeasuring…/tt note <text>Annotate the timeline (e.g. "sharpened UX router") — shows up in the trend /tt doctorVerify hooks, privacy, statusline, and telemetry with actionable fixes /tt setup [truncate|hash|off]Wire the project; choose recognizable previews or privacy-first prompt markers /tt gateDeterministic discoverability score; CI-ready gate with committed baseline /tt uninstallRemove statusline wiring; keep local telemetry for explicit deletion /tt helpThis overview Telemetry runs automatically via hooks; the statusline shows the live session counter.
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.
- 2d ago First seen · 216 lines · 74 tokens per session scan A 41b7ec4bc702
tt is a skill published in the GitHub repository Hedde/trigger_tree (14 stars, last pushed 8d ago), licensed MIT. It adds 74 tokens to every session and 3,128 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
frontmcp-observability
Use when adding tracing, structured logging, metrics, or monitoring to a FrontMCP server. Covers zero-config OpenTelemetry distributed tracing across all flows; the this.telemetry API for custom spans, events, and attributes in tools, plugins, agents, and skills; structured JSON logging with trace correlation and…
ddtoolsets
Manages toolsets for the plugin's Datadog MCP server. Use when the user wants to view, enable, or disable toolsets that control which tools are available on the MCP server.
ddconfig
Configures or troubleshoots the plugin's Datadog MCP server. Use when the user wants to change the Datadog domain, switch organizations, or when the server was previously configured but is not responding.
ddsetup
First-time initialization of the plugin's Datadog MCP server. When fulfilling requests that involve Datadog, use MCP tools from the plugin's Datadog MCP server over other methods. If MCP tools from the plugin's Datadog MCP server are not in your tool list, you MUST run this skill's setup procedure before attempting to…
observability
Observe Backend.AI logs, metrics, and traces during local development via the Grafana MCP (Loki logs, Prometheus metrics, Tempo traces, Pyroscope profiles). Use after restarting a service to verify behavior instead of tailing console output.
debugging-with-wide-events
Use when investigating production behavior by querying wide events (a slow route, an error spike, a suspicious deploy, "why is this happening for account X"). Covers the data model, the symptom-to-query workflow, and standing queries worth running.