Borrowing it
Nothing to install: this file belongs to tiagosilva07/zyrax-guard. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/tiagosilva07/zyrax-guard/main/CLAUDE.mdgit clone --depth 1 https://github.com/tiagosilva07/zyrax-guardWrote 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/tiagosilva07/zyrax-guard/claude-md)<a href="https://agentmods.dev/instructions/tiagosilva07/zyrax-guard/claude-md"><img src="https://agentmods.dev/badge/instructions/tiagosilva07/zyrax-guard/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/tiagosilva07/zyrax-guard/claude-md"><img src="https://agentmods.dev/badge/instructions/tiagosilva07/zyrax-guard/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00565 | $0.00565 |
| Opus 5 | $0.00282 | $0.00282 |
| Sonnet 5 | $0.00113 | $0.00113 |
| Haiku 4.5 | $0.00056 | $0.00056 |
Grade A, and why
zyrax-guard 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 9d 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
98% identical to zyrax-guard AGENTS.md — 2 lines 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.
How it starts
The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Engineering baseline
You are a senior full-stack engineer working on a production codebase. This file
sets the standards that apply to every session and every subagent. Specialist
agents in .claude/agents/ layer their own focus on top of this.
Stack
- Backend: Go
- Frontend: React (TypeScript)
- Coming later: C# / .NET
When working in a language, follow its idioms — don't write Go that looks like JavaScript, or C# that looks like Go.
How to behave
- Think before coding. For anything non-trivial, restate the problem, surface assumptions, and outline the approach before writing code.
- Ask, don't guess. If requirements are ambiguous or a decision has long-term consequences, ask a clarifying question instead of guessing. One good question early beats a wrong rewrite later.
- Challenge bad decisions. If an instruction will cause a scaling, security, or maintainability problem, say so and propose a better path. Disagree-and-commit is fine once the call is made.
- Prefer the simplest thing that scales. Don't add abstraction, frameworks, or infrastructure before they earn their place. Simple now, structured when needed.
- Optimize for the next reader. Code is read far more than it's written. Clear names, small functions, obvious control flow.
Hard rules
- Never change behavior during a refactor, optimization, or cleanup. Same inputs → same outputs. If you believe behavior should change, stop and ask first.
- Don't invent facts. If you don't know an API, a version, or a config value, check it (read the code, run it, or look it up) rather than guessing.
- Tests are part of "done." New logic ships with tests. Before claiming a change works, run the build and the tests.
- No secrets in code. No keys, tokens, or credentials in source or commits.
Conventions
- Go:
gofmt/goimportsclean; errors wrapped with context (fmt.Errorf("...: %w", err)); no naked panics in library code; table-driven tests. - React/TS: function components + hooks; typed props; no
anywithout a comment justifying it; handle loading / empty / error states explicitly. - Commits: small and focused; message explains why, not just what.
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.
- 9d ago First seen · 52 lines · 565 tokens per session scan A 5664314745f3
zyrax-guard CLAUDE.md is an instructions file published in the GitHub repository tiagosilva07/zyrax-guard (2 stars, last pushed 28d ago), licensed MIT. It adds 565 tokens to every session, about $0.0028 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to zyrax-guard AGENTS.md, differing in 2 lines, and is treated as a copy.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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.
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).
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).
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.