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/JuanMarchetto/agent-skillsWrote 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/juanmarchetto/agent-skills/post-run-analysis)<a href="https://agentmods.dev/plugins/juanmarchetto/agent-skills/post-run-analysis"><img src="https://agentmods.dev/badge/plugins/juanmarchetto/agent-skills/post-run-analysis/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/juanmarchetto/agent-skills/post-run-analysis"><img src="https://agentmods.dev/badge/plugins/juanmarchetto/agent-skills/post-run-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
post-run-analysis 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 2mo 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
{
"name": "post-run-analysis",
"description": "Automatic post-mortem analysis — parses logs, compares with history, identifies recurring patterns, proposes fixes, updates memory",
"version": "1.0.0",
"author": { "name": "Juan Marchetto" },
"homepage": "https://github.com/JuanMarchetto/post-run-analysis-skill",
"repository": "https://github.com/JuanMarchetto/post-run-analysis-skill",
"license": "MIT"
}
What it installs
The manifest is a name and a version. 1 skill, 3 commands travel with it, and installing the plugin installs all of them — 145 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.
- 2mo ago First seen · 10 lines scan A d2ec9131088d
post-run-analysis is a plugin published in the GitHub repository JuanMarchetto/agent-skills (5 stars, last pushed 7mo 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-09-03.
post-run-analysis compared with plugins from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| post-run-analysisJuanMarchetto/agent-skills | Plugin | 5 | 7mo ago | MIT | A | — | Claude Code |
| mochiDevZonayed/Mochi | Plugin | 3 | 8d ago | MIT | A | — | Claude Code |
| cross-code-organizermcpware/cross-code-organizer | Plugin | 391 | 7d ago | MIT | A | — | Claude Code |
| context-guardmelodic-software/claude-code-plugins | Plugin | 30 | today | MIT | A | — | Claude Code |
| codies-memorypyros-projects/limitless | Plugin | 2 | 5d ago | MIT | A | — | Claude Code |
| claude-brainmemvid/claude-brain | Plugin | 585 | 9mo ago | MIT | A | — | Claude Code |
| loreconvolabyrinth-analytics/loreconvo | Plugin | 12 | 5d ago | none | A | — | Claude Code |