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 mcp/eliottreich/taskbounty-check/taskbounty-checkgit clone --depth 1 https://github.com/eliottreich/taskbounty-checkWrote 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/eliottreich/taskbounty-check/taskbounty-check)<a href="https://agentmods.dev/mcp/eliottreich/taskbounty-check/taskbounty-check"><img src="https://agentmods.dev/badge/mcp/eliottreich/taskbounty-check/taskbounty-check.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
taskbounty-check 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 5d 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
{
"taskbounty-check": {
"command": "npx",
"args": [
"-y",
"taskbounty-check"
],
"env": {}
}
}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.
- 5d ago First seen · 10 lines scan A e1fcaea36853
taskbounty-check is an MCP server published in the GitHub repository eliottreich/taskbounty-check (2 stars, last pushed 2mo ago), licensed MIT. 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-08-31.
Other mcp servers, from other repositories
github-actions
GitHub Actions MCP — view runs, read logs, re-run jobs, and manage CI/CD. Runs locally from the mcp-server-github-actions npm package.
gha-intel
Workflow timing analysis, configuration audit and billing insight for GitHub Actions. Runs locally from the @barissozudogru/gha-intel-mcp npm package. Needs 1 environment variable to run.
lastping
Monitoring that agents set up for themselves — cron jobs, CI/CD pipelines and AI agent runs. Remote server at mcp.lastping.dev.
blacksmith
MCP server for Blacksmith CI - query runs, analyze test failures, detect flaky tests. Runs locally from the blacksmith-mcp npm package. Needs 2 environment variables to run.
ecz-id-mcp-verifier
Local-first, read-only ECZ-ID verifier over MCP (stdio): checks, reports, explains, routes. Runs locally from the @ecocitizenz/ecz-id-mcp-verifier npm package.
github-actions-audit
GitHub Actions workflow security audit - 21 checks: pinning, permissions, secrets, injection. Remote server at unbearable-dev--github-actions-audit.apify.actor.