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/ramonclaudio/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/ramonclaudio/skills/audit)<a href="https://agentmods.dev/plugins/ramonclaudio/skills/audit"><img src="https://agentmods.dev/badge/plugins/ramonclaudio/skills/audit/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/ramonclaudio/skills/audit"><img src="https://agentmods.dev/badge/plugins/ramonclaudio/skills/audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
audit 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
{
"name": "audit",
"version": "1.5.0",
"description": "Brutally honest codebase audit with parallel agents. Finds bugs, architectural rot, and dead weight.",
"author": {
"name": "ramonclaudio",
"email": "[email protected]"
},
"repository": "https://github.com/ramonclaudio/skills",
"license": "MIT",
"keywords": ["audit", "code-review", "parallel-agents", "security"]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 33 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 · 13 lines scan A 32fd8f3acc53
audit is a plugin published in the GitHub repository ramonclaudio/skills (4 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
gaussian-engineering
Engineering cycle: 104-pattern code review, 60+ runtime training failure debugging (OOM/NaN/divergence), compression & streaming deployment, publication-quality charts, research-to-production guide.
code-review
Perform a comprehensive code review of recent changes.
graph-it-live
Dependency, call-graph, impact, and architecture analysis for codebases.
kin
Kin keeps a living map of the software itself so humans and agents can understand what every change touches. Locate, search, context packs, data-flow tracing, and impact analysis without raw file search.
double-check
Verify code correctness with systematic second-pass analysis.
memtrace-skills
Memtrace skills for codebase exploration, code search, relationship analysis, temporal evolution, blast radius impact, code quality, graph algorithms, API topology, GitHub PR code review, multi-agent fleet coordination (branch-scoped intents, conflict classification, and agent-judged Class C resolution), and…