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/Socialpranker/agentburnWrote 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/socialpranker/agentburn/agentburn)<a href="https://agentmods.dev/mcp/socialpranker/agentburn/agentburn"><img src="https://agentmods.dev/badge/mcp/socialpranker/agentburn/agentburn/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/socialpranker/agentburn/agentburn"><img src="https://agentmods.dev/badge/mcp/socialpranker/agentburn/agentburn.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
agentburn 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
{
"agentburn": {
"command": "uvx",
"args": [
"agentburn"
],
"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.
- 1mo ago First seen · 9 lines scan A 0ab31dce645f
agentburn is an MCP server published in the GitHub repository Socialpranker/agentburn (113 stars, last pushed 6d 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-30.
Other mcp servers, from other repositories
github
Lets the agent work with GitHub: search code, read and create issues and pull requests, and manage repositories through the GitHub API. Runs locally from the @modelcontextprotocol/server-github npm package. Needs 1 environment variable to run.
glitchtip
MCP server "glitchtip", hosted remotely at glitchtip.infra.developerz.ai, as configured in developerz-ai/ai-task-master.
hermes-action
Configurable bridge for external agents to delegate actions to Hermes Agent via CLI or MCP. Runs locally from the hermes-action-bridge npm package.
spectral
Spectral Python (SPy) is a Python module for hyperspectral image processing. Runs locally from the spectral Python package.
claude-handoff
Summarize & export a Claude Code session into one clean handoff.md for Gemini, GPT, or another Claude. Runs locally from the claude-handoff Python package.
capsule
Compact, source-linked context packs that reduce token waste for coding agents. Runs locally from the capsulectx npm package.