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/watt-mind/coachWrote 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/mcp/watt-mind/coach/trigger)<a href="https://agentmods.dev/mcp/watt-mind/coach/trigger"><img src="https://agentmods.dev/badge/mcp/watt-mind/coach/trigger/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/mcp/watt-mind/coach/trigger"><img src="https://agentmods.dev/badge/mcp/watt-mind/coach/trigger.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
trigger 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 3d 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
{
"trigger": {
"command": "npx",
"args": [
"trigger.dev@latest",
"mcp",
"--api-url",
"https://trigger.newpush.com/"
]
}
}What else settings.json configures
This page is one entry in a file that holds 5. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 3d ago First seen · 11 lines scan A dddfad7ae1a2
trigger is an MCP server published in the GitHub repository watt-mind/coach (100 stars, last pushed 2d ago), licensed Apache-2.0. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. 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-10-13.
Other mcp servers, from other repositories
strava-mcp
Privacy-first MCP server for Strava activities, streams, routes and training. Runs locally from the strava-mcp-unofficial npm package. Needs 8 environment variables to run.
intervals-mcp-server
Model Context Protocol (MCP) server for the Intervals.icu API — activities, wellness, power curves & training calendar. Runs locally from the intervals-mcp-server npm package.
igpsport-mcp
Local MCP server exposing iGPSport cycling data with server-side training metrics (NP/IF/TSS/CTL/ATL/TSB). Runs locally from the igpsport-mcp Python package. Needs 5 environment variables to run.
accounted
MCP server "accounted", hosted remotely at app.accounted.se, as configured in erp-mafia/accounted.
hive-mind
MCP server "hive-mind" as configured in toml0006/hive-mind. Runs locally from the hive-mind Python package.
reed-mcp
MCP server "reed-mcp" as configured in Ulzuhan/reed-mcp. Runs locally from the reed-mcp Python package.