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/mcp360/mtarsier/claude-mdgit clone --depth 1 https://github.com/mcp360/mTarsierWrote 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/mcp360/mtarsier/claude-md)<a href="https://agentmods.dev/instructions/mcp360/mtarsier/claude-md"><img src="https://agentmods.dev/badge/instructions/mcp360/mtarsier/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.00178 | $0.00178 |
| Opus 5 | $0.00089 | $0.00089 |
| Sonnet 5 | $0.00036 | $0.00036 |
| Haiku 4.5 | $0.00018 | $0.00018 |
Grade A, and why
mTarsier 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 4d 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
mTarsier — Claude Code Instructions
See AGENTS.md for full project guide, architecture, conventions, and key file paths.
Quick Rules
- Do not use
unwrap()in Rust — use?ormap_err - Do not hardcode hex colors — use Tailwind CSS variable tokens
- Do not add a new Tauri command without registering it in both
commands/mod.rsandlib.rs - Keep React components under 150 lines
src-tauri/binaries/is gitignored — never commit compiled binaries- Branch names must follow
<type>/<description>— see AGENTS.md for the full prefix list (feature/,fix/,perf/,refactor/,chore/,docs/,test/,release/)
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.
- 4d ago First seen · 13 lines · 178 tokens per session scan A 4c3867b5b26c
mTarsier CLAUDE.md is an instructions file published in the GitHub repository mcp360/mTarsier (50 stars, last pushed 4mo ago), licensed MIT. It adds 178 tokens to every session, about $0.0009 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
mcpscore AGENTS.md
Instructions for mcp-box/mcpscore, covering agent instructions for mcpscore and gotchas (learned the hard way).
pixabay-mcp-server CLAUDE.md
Claude Code instructions for hanoak/pixabay-mcp-server, covering claude.md, project overview, tech stack (decided — do not relitigate without discussion), architecture & folder conventions and coding standards.
zaezd AGENTS.md
AGENTS.md instructions for EvilFreelancer/zaezd, covering zaezd - agent brief, state of the repository, commands, how work is delivered and layers.
metmuseum-mcp CLAUDE.md
Instructions for mikechao/metmuseum-mcp, covering claude.md, project overview, development commands, install dependencies (requires pnpm) and type checking.
metmuseum-mcp AGENTS.md
Instructions for mikechao/metmuseum-mcp, covering repository guidelines, project structure & module organization, build, test, and development commands, coding style & naming conventions and testing guidelines.
brick-mcp-app CLAUDE.md
Instructions for dend/brick-mcp-app, covering brick builder mcp app, important rules, specs, tech stack and key commands.