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/zeng3ld/gate4agent/claude-mdgit clone --depth 1 https://github.com/ZENG3LD/gate4agentWrote 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/zeng3ld/gate4agent/claude-md)<a href="https://agentmods.dev/instructions/zeng3ld/gate4agent/claude-md"><img src="https://agentmods.dev/badge/instructions/zeng3ld/gate4agent/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.00313 | $0.00313 |
| Opus 5 | $0.00156 | $0.00156 |
| Sonnet 5 | $0.00063 | $0.00063 |
| Haiku 4.5 | $0.00031 | $0.00031 |
Grade A, and why
gate4agent 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
gate4agent — agent harness / thin C2
Node (owns PTY/processes/workspaces/worktrees) + C2 (relay) + Harness
(task kernel, SQLite SWC) + TUI (gate4agent-tui harness mode,
gate4agent-tui-light direct-C2). Plans/handoffs/audits live in the
owner's private workspace documentation tree, not in this repository.
Local endpoints & credentials
- node pipe
\\.\pipe\gate4agent-node, api:18310; primary c2 pipe\\.\pipe\gate4agent-c2, api:18320; harness operator read:18330. - Operator credential:
g4aho_+ 64 hex, envGATE4AGENT_HARNESS_OPERATOR_TOKEN. Node/c2 secrets:GATE4AGENT_NODE_TOKEN,GATE4AGENT_NODE_TOKEN_<NORMALIZED_ID>(uppercase, non-alnum→_),GATE4AGENT_C2_TOKEN. Env-only, never argv. - Windows E2Es run only via
target\release\windows-headless-supervisor.exe <ms> <ABS exe> --exact <fn>. crates/gate4agent-tuiis its own cargo workspace and carries a path dependency on../../../uzor/uzor-tui— every TUI build compiles the uzor dependency tree.
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 · 21 lines · 313 tokens per session scan A 8a9b9167e096
gate4agent CLAUDE.md is an instructions file published in the GitHub repository ZENG3LD/gate4agent (9 stars, last pushed 16d ago), licensed MIT. It adds 313 tokens to every session, about $0.0016 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
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.