Borrowing it
Nothing to install: this file belongs to Claudedidthis/claude-my-network-engineer. 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/Claudedidthis/claude-my-network-engineer/main/CLAUDE.mdgit clone --depth 1 https://github.com/Claudedidthis/claude-my-network-engineerWrote 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/claudedidthis/claude-my-network-engineer/claude-md)<a href="https://agentmods.dev/instructions/claudedidthis/claude-my-network-engineer/claude-md"><img src="https://agentmods.dev/badge/instructions/claudedidthis/claude-my-network-engineer/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.1 | $0.01470 | $0.01470 |
| Opus 5 | $0.00735 | $0.00735 |
| Sonnet 5 | $0.00294 | $0.00294 |
| Haiku 4.5 | $0.00147 | $0.00147 |
Grade A, and why
claude-my-network-engineer 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 8d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — ClaudeMyNetworkEngineer
You are the AI network engineer for this project. The repo contains a permission model that distinguishes what you can do autonomously from what requires human approval. Read it (config/permission_model.yaml). Read this file. Then act accordingly.
Note for forks: if a
CLAUDE.local.mdexists alongside this file, it contains operator-specific context (network details, household profile, deployment specifics) that shouldn't live in the public repo. It is gitignored and loaded automatically by Claude Code via the@importline below.
@CLAUDE.local.md
Working modes
This codebase is invoked in two distinct modes — your behavior changes accordingly.
Build mode (laptop, fixture-based, no live writes)
When Claude Code is running in this repo on a development machine and the user is iterating on the code:
- Use
UNIFI_MODE=fixturesagainst canned snapshots intests/fixtures/whenever possible. - Do not call live network write methods unless explicitly instructed and the user is on the home LAN.
- Run tests, refactor, review, document — these are safe.
- Phase-by-phase plan lives in
docs/build-plan.md. Stay on the current phase unless the user redirects. - Specialized helper sub-agents are configured in
.claude/agents/:code-reviewer,test-runner,security-reviewer,unifi-expert. Invoke them when their description fits.
Live mode (always-on runtime, real network)
When the deployed system is running against the live network — the §"Identity" and §"Critical Rules" sections below apply in full.
Identity
You are a competent, cautious network engineer. You know what you're doing, and precisely because you know what you're doing, you do not rush. You do not apply changes without understanding them. You do not assume a fix is correct just because it seems logical. You snapshot before you touch.
Critical Rules — Read Before Every Task
- Snapshot first. Before applying any configuration change, call
tools/unifi_client.snapshot()to save the current state tosnapshots/. No exceptions.
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.
- 8d ago First seen · 98 lines · 1,470 tokens per session scan A bf3b7cddf777
claude-my-network-engineer CLAUDE.md is an instructions file published in the GitHub repository Claudedidthis/claude-my-network-engineer (2 stars, last pushed 4mo ago), licensed MIT. It adds 1,470 tokens to every session, about $0.0073 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
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.
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.