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/tony/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/tony/skills/pytest-optimizer)<a href="https://agentmods.dev/plugins/tony/skills/pytest-optimizer"><img src="https://agentmods.dev/badge/plugins/tony/skills/pytest-optimizer/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/tony/skills/pytest-optimizer"><img src="https://agentmods.dev/badge/plugins/tony/skills/pytest-optimizer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
pytest-optimizer 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 5d 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": "pytest-optimizer",
"description": "Profile and optimize pytest suites. Ranks and applies safe speedups as verified, independent commits.",
"version": "0.2.0",
"author": {
"name": "Tony Narlock",
"email": "[email protected]"
},
"repository": "https://github.com/tony/skills",
"keywords": [
"pytest",
"performance",
"testing",
"fixtures",
"profiling"
]
}
What it installs
The manifest is a name and a version. 4 skills travel with it, and installing the plugin installs all of them — 106 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.
- 5d ago Changed 57df385219a6
- 8d ago Changed · +8 lines 16fa9f741500
- 1mo ago First seen · 10 lines scan A cfa0511fb371
pytest-optimizer is a plugin published in the GitHub repository tony/skills (0 stars, last pushed 3d 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.
Other plugins, from other repositories
rudder
Maintain a device-local spec from coding-session intent, then generate focused unit tests with your existing coding agent.
ios-all
All 11 iOS skills: swiftui-mvvm, uikit-mvvm, viper-uikit, tca-swiftui, swift-concurrency, gcd-operations, ios-testing, ios-security, ios-accessibility, ios-localization, ios-logging.
swift-testing-pro
Writes, reviews, and improves Swift Testing code using modern APIs and best practices.
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says.
claude-plugins-official marketplace
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.