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/Pratham-Mishra04/trailWrote 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/plugins/pratham-mishra04/trail/claude-code)<a href="https://agentmods.dev/plugins/pratham-mishra04/trail/claude-code"><img src="https://agentmods.dev/badge/plugins/pratham-mishra04/trail/claude-code/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/plugins/pratham-mishra04/trail/claude-code"><img src="https://agentmods.dev/badge/plugins/pratham-mishra04/trail/claude-code.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
trail 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
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "trail",
"version": "0.1.3",
"description": "Capture process logs and let your AI agent debug them. Auto-wires the trail MCP server (list_sessions, get_logs) and ships a debugging skill that walks through capturing → querying → cleanup.",
"author": {
"name": "Pratham Mishra",
"url": "https://github.com/Pratham-Mishra04"
},
"homepage": "https://prathammishra.com",
"repository": "https://github.com/Pratham-Mishra04/trail",
"license": "MIT",
"keywords": ["logging", "debugging", "mcp", "stdout", "stderr", "observability"]
}
What it installs
The manifest is a name and a version. 1 skill, 1 MCP server travel with it, and installing the plugin installs all of them — 52 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 15 lines scan A 6e70cc17c4ec
trail is a plugin published in the GitHub repository Pratham-Mishra04/trail (8 stars, last pushed 4mo 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-31.
Other plugins, from other repositories
graph-it-live
Dependency, call-graph, impact, and architecture analysis for codebases.
polygraph
A polygraph for your state machine. The agent does the hard part for you: it instruments your code, builds any test doubles needed to run it, and captures real execution traces — then has an LLM derive a transition-function spec from the source (default: a SAM v2 strict-profile module with named…
token-master
Token-efficient code-understanding harness. Routes structural questions (callers, callees, impact, inheritors) to a prebuilt code graph instead of repeated grep and file-reads, cutting cumulative context tokens. Type /token-master in a repo to build the index and turn on routing.
ci-incident-medic
Triages failing GitHub Actions runs, hardens Dockerfiles, pre-flights Kubernetes manifests before they reach the cluster, and drafts blameless postmortems from incident evidence.
codebase-navigator
Gets an unfamiliar repo running locally by diagnosing and fixing broken setup, decodes opaque build systems, and does task-scoped change localization and end-to-end flow tracing, so you're productive on day one.
karellen-lsp-mcp
LSP-backed code intelligence for Claude Code via MCP and native LSP - navigate definitions, references, call hierarchies, type hierarchies, and diagnostics across codebases.