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/charlesjones-dev/claude-code-plugins-devWrote 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/charlesjones-dev/claude-code-plugins-dev/ai-performance)<a href="https://agentmods.dev/plugins/charlesjones-dev/claude-code-plugins-dev/ai-performance"><img src="https://agentmods.dev/badge/plugins/charlesjones-dev/claude-code-plugins-dev/ai-performance/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/charlesjones-dev/claude-code-plugins-dev/ai-performance"><img src="https://agentmods.dev/badge/plugins/charlesjones-dev/claude-code-plugins-dev/ai-performance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
ai-performance 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 10d 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": "ai-performance",
"version": "1.2.2",
"description": "Audits a codebase for performance bottlenecks and saves a timestamped report with an impact score for each finding, with an agent for unattended runs",
"author": {
"name": "Charles Jones",
"url": "https://charlesjones.dev"
},
"repository": "https://github.com/charlesjones-dev/claude-code-plugins-dev",
"license": "MIT",
"keywords": [
"ai",
"performance",
"optimization",
"analysis",
"bottleneck",
"scalability",
"skills"
]
}
What it installs
The manifest is a name and a version. 1 skill, 1 agent 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.
- 10d ago Changed · +1 lines 6d53f376e9b2
- 1mo ago First seen · 20 lines scan A c622c920d18f
ai-performance is a plugin published in the GitHub repository charlesjones-dev/claude-code-plugins-dev (35 stars, last pushed 6d 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-30.
Other plugins, from other repositories
hunch
A git-native reasoning graph of decisions, bugs, and invariants for your codebase — queried and enforced at reasoning time. Adds the hunch MCP tools plus /hunch:capture, /hunch:heal, /hunch:why, /hunch:fix, /hunch:fragile.
dev-loop
Three commands for the daily loop in Claude Code: fix a bug or apply a review report, commit with pre-flight checks, or run review, fix and commit as one flow, pausing after the review for your go-ahead.
duet
Claude Code plugin for reflection, code quality, writing, and design.
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…
workflow
Code review and worktree workflow commands.
diffctx
Selects the minimum code an LLM needs to review a git diff.