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/asmyshlyaev177/test-proxy-recorder/claude-mdgit clone --depth 1 https://github.com/asmyshlyaev177/test-proxy-recorderWhat 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.00022 | $0.00022 |
| Opus 5 | $0.00011 | $0.00011 |
| Sonnet 5 | $0.00004 | $0.00004 |
| Haiku 4.5 | $0.00002 | $0.00002 |
Grade A, and why
test-proxy-recorder CLAUDE.md 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 yesterday.
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
See AGENTS.md for the repo structure cheatsheet, commands, and conventions.
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.
- yesterday First seen · 2 lines · 22 tokens per session scan A 811fca32c3e5
test-proxy-recorder CLAUDE.md is an instructions file published in the GitHub repository asmyshlyaev177/test-proxy-recorder (116 stars, last pushed 4d ago), licensed MIT. It adds 22 tokens to every session, about $0.0001 per session on Opus 5. 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 instructions, from other repositories
playwright CLAUDE.md
Instructions for microsoft/playwright, covering monorepo packages, browser packages, tooling packages, key directories and build.
playwright copilot-instructions.md
Instructions for microsoft/playwright, a project described as: Playwright is a framework for Web Testing and Automation. It allows testing Chromium, Firefox and WebKit with a single API.
claude-browser-test-skills CLAUDE.md
Instructions for Autodesk/claude-browser-test-skills, covering claude.md, what this repo is, layout, conventions when editing skills and validate before publishing.
playwright-fieldkit AGENTS.md
Instructions for jpbaking/playwright-fieldkit: Follow the Portable Agent Authoring guides for every skill or harness change.
lastest CLAUDE.md
Claude Code instructions for las-team/lastest, covering claude.md, critical rules, commands, tesseract. part of the default compose stack; set and ocrserviceurl=http://localhost:8891 in .env.local.
lastest AGENTS.md
AGENTS.md instructions for las-team/lastest, covering agents.md — lastest, what is lastest?, mcp server, available tools (50 total, all prefixed lastest) and typical workflow.