claude-tap is a local proxy and trace viewer for AI coding agents, recording and displaying their API requests, prompts, tool calls, responses, context, and token usage. It helps developers inspect and compare agent runs from tools such as Claude Code, Codex CLI, Gemini CLI, Cursor CLI, and others, while the catalogue skills and instruction support work with the project.
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/liaohch3/claude-tap/agents-mdgit clone --depth 1 https://github.com/liaohch3/claude-tapWrote 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/liaohch3/claude-tap/agents-md)<a href="https://agentmods.dev/instructions/liaohch3/claude-tap/agents-md"><img src="https://agentmods.dev/badge/instructions/liaohch3/claude-tap/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.01674 | $0.01674 |
| Opus 5 | $0.00837 | $0.00837 |
| Sonnet 5 | $0.00335 | $0.00335 |
| Haiku 4.5 | $0.00167 | $0.00167 |
Grade A, and why
claude-tap 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 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.
How it starts
The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maintainer Automation Notes
External contributors should start with CONTRIBUTING.md. This file documents stricter maintainer and agent automation workflows; it is not the public contribution checklist.
AGENTS 索引
本文件是贡献者规则的入口。详细策略文本位于 .agents/docs/standards/*.md。
Documentation Boundary
docs/ is reserved for public project documentation and README assets that open-source users or external contributors read directly. Maintainer policies, implementation plans, learning records, PR evidence, and recording assets belong under .agents/ so internal automation workflows stay out of the public docs tree.
Public user-facing documentation must be bilingual. Add or update the English document and the Simplified Chinese counterpart together; use README.md with README_zh.md, and use *.zh.md beside English guide files under docs/guides/.
Review Guidelines
When reviewing pull requests, prioritize findings that can cause correctness bugs, regressions, security or privacy issues, release failures, broken CI, broken packaging, or misleading evidence. Treat these as high-priority review findings.
Do not block on style-only or preference-only comments unless they make the code materially harder to maintain or violate an existing repository rule.
For every pull request, check:
- The implementation matches the requested scope and does not mix unrelated refactors, feature work, or generated artifacts.
- Tests contain meaningful assertions that would fail for realistic regressions, not only line coverage.
- UI, viewer, or evidence changes include real trace-backed screenshots or recordings when required by repository policy.
- Public documentation changes are bilingual, with matching English and Simplified Chinese updates.
- Workflow, release, credential, subprocess, network, filesystem, and dependency changes use least privilege and avoid leaking secrets.
- Commit titles, PR titles, PR bodies, and evidence links follow the repository contribution and preflight requirements.
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 · 111 lines · 1,674 tokens per session scan A fc3dd4d41d90
claude-tap AGENTS.md is an instructions file published in the GitHub repository liaohch3/claude-tap (3,173 stars, last pushed 10d ago), licensed MIT. It adds 1,674 tokens to every session, about $0.0084 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
hoop CLAUDE.md
Claude Code instructions for hoophq/hoop, covering claude.md, project overview, toolchain & prerequisites, architecture and module breakdown.
opencodex AGENTS.md
AGENTS.md instructions for lidge-jun/opencodex, covering agents.md, what this project is, repository layout, optional subsystems stay off the core path and the devlog directory.
goai AGENTS.md
AGENTS.md instructions for zendev-sh/goai, covering agents.md - goai, commands, architecture, key rules and adding providers.
bifrost AGENTS.md
AGENTS.md instructions for bifrost-proxy/bifrost, covering bifrost 项目开发规则, 执行心法, 执行模式与完成定义, 任务模式判定 and 变更类型与验证路由(先判定,后执行).
reddit-research-mcp CLAUDE.md
Claude Code instructions for dialog-tools/reddit-research-mcp, covering reddit research mcp server - development guide, project overview, key files, releasing new versions and automated release process.
gitlab-mcp-server mcp-best-practices.instructions.md
MCP protocol-level best practices for tool design, annotations, response formats, pagination, and security. Applies to all Go MCP server code.