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/openafw/agentzt/claude-mdgit clone --depth 1 https://github.com/openafw/agentztWrote 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/openafw/agentzt/claude-md)<a href="https://agentmods.dev/instructions/openafw/agentzt/claude-md"><img src="https://agentmods.dev/badge/instructions/openafw/agentzt/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.01360 | $0.01360 |
| Opus 5 | $0.00680 | $0.00680 |
| Sonnet 5 | $0.00272 | $0.00272 |
| Haiku 4.5 | $0.00136 | $0.00136 |
Grade C, and why
agentzt CLAUDE.md scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- Before committing: reset `config/agents.json` to an empty `agents` array and `rm -rf How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Guidance for Claude Code (and other agents) working in this repository.
What this is
agentzt — Zero Trust for AI Agents. An AI agent reaches enterprise model APIs and
tools only through a zero-trust proxy, the same way a human reaches enterprise apps
through a ZTNA client + gateway. It does not replace ZTNA for humans; it secures the
agent→model and agent→tool path.
agentzt-client(src/client) — local proxy + per-agent identity. The agent points its model SDK at it (ANTHROPIC_BASE_URL=http://localhost:8787); the client attaches a short-lived token to every request and forwards to the gateway.agentzt-gateway(src/gateway) — PDP+PEP. Authenticates the agent, issues scoped short-lived tokens, enforces deny-by-default RBAC + ABAC + JIT, runs input/output guardrails, audits everything, then forwards to the real model API / tools.
Open source, Apache 2.0, repo: https://github.com/openguardrails/agentzt
Hard constraints — read before editing
- Zero runtime dependencies. No build step. Everything runs on Node ≥ 22.6 via
native TypeScript type-stripping (
node src/...ts). Do not add npm dependencies or a bundler.package.jsondeps stay empty (only@types/node+typescriptas devDeps for editor/typecheck). - Because of type-stripping, write erasable TypeScript only: no
enum, nonamespace, no constructor parameter properties, no decorators. Useimport typefor type-only imports and.tsextensions on every relative import (ESM). - The only allowed external process is
openssl, and only insrc/cli/tls.tsfor opt-in mTLS PKI setup. The runtime never shells out. - Use Node built-ins only:
node:http,node:https,node:crypto,node:tls, globalfetch. Note globalfetchcan't carry client certs — usesrc/client/transport.ts(which falls back tonode:https) for outbound client calls.
Commands
npm run demo # end-to-end: enroll, start gateway+client, drive 8 control checks, audit
npm run demo:mtls # same, over mutual TLS (needs openssl)
npm test # 28 checks (auth, RBAC, guardrails, ABAC, JIT, audit chain, mTLS)
npm run typecheck # tsc --noEmit (needs `npm i` once for typescript)
npm run gateway # start gateway (PDP+PEP)
AGENTZT_AGENT_ID=<id> npm run client # start client proxy for an agent
node src/cli/index.ts enroll --agent <id> --role <role> [--mtls]
node src/cli/index.ts roles | agents | audit [--verify] | tls init | tls issue --agent <id>
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 · 97 lines · 1,360 tokens per session scan C 811a29baac5f
agentzt CLAUDE.md is an instructions file published in the GitHub repository openafw/agentzt (10 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 1,360 tokens to every session, about $0.0068 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
caracal file-header.instructions.md
Use when creating or editing any source file. Enforces the mandatory copyright header format for all files.
warden AGENTS.md
AGENTS.md instructions for stephnangue/warden, covering warden — agent guide, where to start, the agent loop, provider skills and adding a skill for a new provider.
VaultysClaw CLAUDE.md
Instructions for vaultys/VaultysClaw, covering claude.md, commands, development, demo / simulator and build.
caracal console-example-naming.instructions.md
Use when writing, editing, or reviewing web console help, info pages, field examples, guided setup copy, or example-facing web console UI text. Enforces the approved Caracal demo naming universe.
VaultysClaw control-plane.instructions.md
Use when working on the control-plane package: Next.js App Router pages, API routes, database queries, React components, auth, or UI styling.
caracal docs-documentation.instructions.md
Use when writing, editing, or reviewing Caracal documentation under caracal/docs/. Enforces production-grade technical writing, page-flow awareness, and scoped coherent docs edits.