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/bun913/mcp-testrail/claude-mdgit clone --depth 1 https://github.com/bun913/mcp-testrailWrote 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/bun913/mcp-testrail/claude-md)<a href="https://agentmods.dev/instructions/bun913/mcp-testrail/claude-md"><img src="https://agentmods.dev/badge/instructions/bun913/mcp-testrail/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.1 | $0.00406 | $0.00406 |
| Opus 5 | $0.00203 | $0.00203 |
| Sonnet 5 | $0.00081 | $0.00081 |
| Haiku 4.5 | $0.00041 | $0.00041 |
Grade A, and why
mcp-testrail 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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- PlayWright-MCP-Repo CLAUDE.md — 100% identical, 0 lines differ
What it actually says
Claude Instructions for MCP TestRail Project
Project Overview
This is an MCP (Model Context Protocol) server for TestRail integration built with TypeScript. When working on this project, always reference the documentation in the AI/ directory for context and guidance.
Development Workflow
Before making any changes, review AI/development-workflow.md for the complete development process including:
- Environment setup
- Build and test commands
- Debugging procedures
- Project structure
Key Commands to Remember
- Development:
npm run start:fastmcp - Build:
npm run build - Test:
npm test - Format:
npm run format - Debug:
npm run debug - Production:
npm run start:stdio
Project Structure
src/
├── client/ # TestRail API client implementation
├── server/ # MCP server implementation
├── shared/ # Common schemas and types
├── stdio.ts # stdio mode entry point
└── sse.ts # SSE mode entry point
Important Notes
- Always run tests after making changes:
npm test - Use Biome for code formatting:
npm run format - Node.js version requirement: 20.18.1 ~ 22.14.0
- The project uses ES modules (
"type": "module") - MCP Inspector is available for debugging via
npm run debug
When Making Changes
- Check existing documentation in
AI/directory - Follow the development workflow in
AI/development-workflow.md - Run tests and formatting before committing
- Update relevant documentation if adding new features
Environment Variables Required
TESTRAIL_URL: Your TestRail instance URLTESTRAIL_USERNAME: TestRail usernameTESTRAIL_API_KEY: TestRail API key
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 · 47 lines · 406 tokens per session scan A 1b82dd6e3c79
mcp-testrail CLAUDE.md is an instructions file published in the GitHub repository bun913/mcp-testrail (44 stars, last pushed 2mo ago), licensed MIT. It adds 406 tokens to every session, about $0.0020 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
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).