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/binsarjr/termul/claude-mdgit clone --depth 1 https://github.com/binsarjr/termulWrote 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/binsarjr/termul/claude-md)<a href="https://agentmods.dev/instructions/binsarjr/termul/claude-md"><img src="https://agentmods.dev/badge/instructions/binsarjr/termul/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.00004 | $0.00004 |
| Opus 5 | $0.00002 | $0.00002 |
| Sonnet 5 | $0.00001 | $0.00001 |
| Haiku 4.5 | $0.00000 | $0.00000 |
Grade A, and why
termul 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.
This is a copy
100% identical to deepseek-harness CLAUDE.md — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
AGENTS.md
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 · 2 lines · 4 tokens per session scan A 954ec5dad7ea
termul CLAUDE.md is an instructions file published in the GitHub repository binsarjr/termul (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 4 tokens to every session, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to deepseek-harness CLAUDE.md, differing in 1 line, and is treated as a copy.
Other instructions, from other repositories
pisper AGENTS.md
AGENTS.md instructions for ling-kong-ran/pisper, covering agents.md, project, architecture, commands and setup.
tmuxy CLAUDE.md
Claude Code instructions for flplima/tmuxy, covering tmuxy, project structure, cli usage, pane operations and tab operations.
terminal-use CLAUDE.md
Instructions for flipbit03/terminal-use, covering terminal-use (tu), build & test, architecture, conventions and git commits.
mars AGENTS.md
Instructions for Yazelix/mars, covering mars agent guide, workflow, source boundaries, validation and release workflow.
zashiki CLAUDE.md
Claude Code instructions for kounetsuman/zashiki, covering zashiki development conventions, comment conventions, testing, documentation (where design, specs, and context live) and issues vs. discussions.
agent-of-empires AGENTS.md
AGENTS.md instructions for agent-of-empires/agent-of-empires, covering repository guidelines, where to look, commands, code rules and tests.