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/cooltea001/cool-test-mcp/agents-mdgit clone --depth 1 https://github.com/CoolTea001/cool-test-mcpWrote 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/cooltea001/cool-test-mcp/agents-md)<a href="https://agentmods.dev/instructions/cooltea001/cool-test-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/cooltea001/cool-test-mcp/agents-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.00352 | $0.00352 |
| Opus 5 | $0.00176 | $0.00176 |
| Sonnet 5 | $0.00070 | $0.00070 |
| Haiku 4.5 | $0.00035 | $0.00035 |
Grade A, and why
cool-test-mcp AGENTS.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
AGENTS
Commit Rules
- Never run
git commitorgit pushunless the user explicitly asks for it. - Before committing, check for secrets and debug code; exclude large files (>1MB).
- Write commits in English, recording only significant changes.
- Format:
<type>(<module>): <description>, wheretypeis one offeat/fix/docs/style/refactor/perf/test/build/ci/chore/revert, and the description is no more than 50 characters. - For multiple changes, list them on separate lines with
- <type>: <description>.
Release & Tag Rules
Use a Releases + Tags model:
- Tags only publish the package: create a lightweight tag (
git tag <version>, no annotation/message), then push it to trigger CI publish. - Releases record the version log: create a GitHub Release with the body rendered in markdown and written in English. Cover these categories: feature additions/changes, bug fixes, and documentation updates.
- The Release's tag must match
package.jsonversion (the CI enforcesv*tag == package version). - Example: push the
vX.Y.Zlightweight tag, thengh release create vX.Y.Z --notes "<version log>".
Documentation & Test Sync
- After completing any coding task, synchronously update the README (
README.md/README.zh.md) and the e2e test (test-e2e.mjs) to reflect the changes.
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 · 22 lines · 352 tokens per session scan A 61da296ecf16
cool-test-mcp AGENTS.md is an instructions file published in the GitHub repository CoolTea001/cool-test-mcp (0 stars, last pushed 12d ago), licensed MIT. It adds 352 tokens to every session, about $0.0018 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-31.
Other instructions, from other repositories
planning-with-files AGENTS.md
AGENTS.md instructions for OthmanAdi/planning-with-files, covering agents.md — planning-with-files agent reference card, commit rules, release checklist (12 steps), version bump scope and changelog format.
loopx AGENTS.md
AGENTS.md instructions for huangruiteng/loopx, covering agent instructions, commit and pr hygiene, worktree and pr gate, dco sign-off and release contributor attribution.
relay AGENTS.md
AGENTS.md instructions for AgentWorkforce/relay, covering git workflow rules, never push directly to main, correct workflow, ... do work .. and stop here - let user merge.
uview-plus AGENTS.md
AGENTS.md instructions for ijry/uview-plus, covering agents, 提交规范, 发布规范 and uview-plus说明.
agentistics AGENTS.md
AGENTS.md instructions for blpsoares/agentistics, covering before starting implementation work, opening a pr, merging: squash a feature, merge a release, documentation and scope discipline.
teguma AGENTS.md
AGENTS.md instructions for Doyajin174/teguma, covering teguma 운영환경, 핵심 원칙, 브랜치·워크트리 규약, 커밋 규약 (conventional commits) and 1. 리뷰 절차.