Borrowing it
Nothing to install: this file belongs to a777ance/claude-code-homelab. 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/a777ance/claude-code-homelab/main/CLAUDE.mdgit clone --depth 1 https://github.com/a777ance/claude-code-homelabWrote 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/a777ance/claude-code-homelab/claude-md)<a href="https://agentmods.dev/instructions/a777ance/claude-code-homelab/claude-md"><img src="https://agentmods.dev/badge/instructions/a777ance/claude-code-homelab/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.02570 | $0.02570 |
| Opus 5 | $0.01285 | $0.01285 |
| Sonnet 5 | $0.00514 | $0.00514 |
| Haiku 4.5 | $0.00257 | $0.00257 |
Grade A, and why
claude-code-homelab 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 7d 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Briefing for Claude Code. This repo is a setup guide — not a live system. Do not attempt to deploy or SSH anywhere from here.
House style: ordering & typography
These conventions apply across every A777ance repo — current and future. (Adopted 2026-06-05.)
- Time-based content reads newest-first (reverse-chronological). Logs, changelogs, decision logs (ADR / FIN), known-issues and issue trackers, FAQs, metrics and review logs, and "Handled For You" entries all lead with the most recent item. Apply this within the time-based section even when the whole file isn't time-based.
- Alphabetical lists run Z → A (descending).
- Walkthroughs: reverse the blocks, keep the steps. In a step-by-step guide, present the major sections/blocks in reverse order (last block first — it helps "block" the work), but keep the numbered steps within each block in forward order so every procedure stays followable. A walkthrough's table of contents mirrors the reversed block order. Never renumber — step and stage numbers stay fixed, so the intended execution order is always readable from the numbers.
- Font: Gill Sans MT everywhere. Every surface — customer-facing or internal — uses
Gill Sans MT. Web/CSS stack:
'Gill Sans MT', 'Gill Sans', Calibri, 'Trebuchet MS', sans-serif.
Bifrost — active command schema (loads every session)
Bifrost is the A777ance command-composition schema — a keyboard-spatial notation
(~ ! @ # $ % ^ & * () swept left→right, each glyph an archetype fulfilled by slash
commands + a plain-language sub-prompt). It is active from the first token of every
session, in every repo: adopt the ~ lazy-anchor posture — fire the first token ASAP
(the model stays high), let continuity coalesce mid-flight — and read Bifrost notation
per the schema whenever used.
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.
- 7d ago First seen · 169 lines · 2,570 tokens per session scan A 71d41f04ca6b
claude-code-homelab CLAUDE.md is an instructions file published in the GitHub repository a777ance/claude-code-homelab (2 stars, last pushed 27d ago), licensed MIT. It adds 2,570 tokens to every session, about $0.0128 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
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).
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.
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).
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.