Borrowing it
Nothing to install: this file belongs to avansaber/tailtest. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/avansaber/tailtest/main/CLAUDE.mdgit clone --depth 1 https://github.com/avansaber/tailtestWrote 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/avansaber/tailtest/claude-md)<a href="https://agentmods.dev/instructions/avansaber/tailtest/claude-md"><img src="https://agentmods.dev/badge/instructions/avansaber/tailtest/claude-md/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/instructions/avansaber/tailtest/claude-md"><img src="https://agentmods.dev/badge/instructions/avansaber/tailtest/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.07383 | $0.07383 |
| Opus 5.5 | $0.02953 | $0.02953 |
| Sonnet 5.5 | $0.01477 | $0.01477 |
| Haiku 4.5 | $0.00738 | $0.00738 |
Grade A, and why
tailtest CLAUDE.md scanned grade A 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Not just `requests` / `axios`. Include `smtplib`, `socket`, `urllib`, `http.client`, `ftplib`, `imaplib`, and any `subprocess` call reaching an external process. How it starts
The opening of the file, as written. The whole thing — 426 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tailtest
You are running with the tailtest plugin. Your job: automatically run the test cycle the user would otherwise ask for manually. Generate production-like scenarios for what was just built, execute them, and surface only what fails.
Step 0: Verify APIs before writing test code
Before writing any test code, read the source file and confirm:
- Every class, function, and method you plan to call in the test actually exists in the module
- Every import resolves to a real name in the file
Scope: verifies imports resolve and named attributes exist. Does not validate full call signatures. If a method does not exist, do not invent it -- adjust the scenario to test what actually exists.
Step 1: At the start of every user turn, check for pending work
Read .tailtest/session.json. If pending_files is non-empty:
Before generating: re-read the source file to understand what it actually does. Derive scenarios from the source's intent and behaviour -- not from your implementation plan or assumptions about what should exist.
- Note the pending files list
- Skip any filtered files (filter rules in Step 2)
- If nothing remains after filtering: clear
pending_filesto[], proceed to the user's message - Before generating, check for ramp-up framing: if
session.jsonhas"ramp_up": true, count the entries whosestatusis"ramp-up"(call this N). If N > 0 and all remaining pending_files entries havestatus: "ramp-up"(pure ramp-up batch, no mixed new-file entries), emit exactly one line now:tailtest: running initial coverage scan on {N} file(s)...If the batch is mixed (contains both"ramp-up"and"new-file"entries), skip the framing line. - Generate scenarios for all remaining files as one unit of work -- treat
"ramp-up"entries identically to"new-file"(generate scenarios, write test, execute, report) - Write test file and execute (Steps 4–5)
- Report failures -- stay silent if all pass (Step 6)
- Write
"pending_files": []back to.tailtest/session.json - Then address the user's message
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 · 426 lines · 7,383 tokens per session scan A ec88608cff60
tailtest CLAUDE.md is an instructions file published in the GitHub repository avansaber/tailtest (11 stars, last pushed 4mo ago), licensed MIT. It adds 7,383 tokens to every session, about $0.0295 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.