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.
npx agentmods add instructions/rcampos09/performance-testing-skills/claude-mdgit clone --depth 1 https://github.com/rcampos09/performance-testing-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/instructions/rcampos09/performance-testing-skills/claude-md)<a href="https://agentmods.dev/instructions/rcampos09/performance-testing-skills/claude-md"><img src="https://agentmods.dev/badge/instructions/rcampos09/performance-testing-skills/claude-md.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.01963 | $0.01963 |
| Opus 5 | $0.00981 | $0.00981 |
| Sonnet 5 | $0.00393 | $0.00393 |
| Haiku 4.5 | $0.00196 | $0.00196 |
Grade B, and why
performance-testing-skills CLAUDE.md scanned grade B with 1 finding 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
allowed-tools: Read, Bash # optional; restricts tools when skill is active (omit to allow all tools) The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 First seen · 178 lines · 1,963 tokens per session scan B 40bc4b873db5
performance-testing-skills CLAUDE.md is an instructions file published in the GitHub repository rcampos09/performance-testing-skills (10 stars, last pushed 5mo ago), with no licence file. It adds 1,963 tokens to every session, about $0.0098 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
mcp-k6 CLAUDE.md
Claude Code instructions for grafana/mcp-k6, covering claude.md, project overview, architecture, core components and key dependencies.
mcp-k6 AGENTS.md
AGENTS.md instructions for grafana/mcp-k6, covering repository guidelines, project structure & module organization, build, test, and development commands, coding style & naming conventions and testing guidelines.
autoframe CLAUDE.md
Instructions for kint4/autoframe, covering autoframe — claude instructions, what is autoframe?, stack (non-negotiable), file locations and folder structure.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).