Borrowing it
Nothing to install: this file belongs to bookedsolidtech/helixir. 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/bookedsolidtech/helixir/main/CLAUDE.mdgit clone --depth 1 https://github.com/bookedsolidtech/helixirWrote 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/bookedsolidtech/helixir/claude-md)<a href="https://agentmods.dev/instructions/bookedsolidtech/helixir/claude-md"><img src="https://agentmods.dev/badge/instructions/bookedsolidtech/helixir/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/bookedsolidtech/helixir/claude-md"><img src="https://agentmods.dev/badge/instructions/bookedsolidtech/helixir/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.01227 | $0.01227 |
| Opus 5.5 | $0.00491 | $0.00491 |
| Sonnet 5.5 | $0.00245 | $0.00245 |
| Haiku 4.5 | $0.00123 | $0.00123 |
Grade A, and why
helixir 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 2mo 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Behavioral Rules
Non-Negotiable Rules
These rules are enforced by hooks and cannot be overridden by any agent instruction:
- NEVER use
--no-verifyto skip git hooks — hooks are safety gates, not obstacles - NEVER commit secrets, credentials, API keys, or tokens to any file
- NEVER force-push to
main,master,staging, orproductionbranches - NEVER push without all applicable quality gates passing (run
pnpm preflightor equivalent) - NEVER install packages without verifying they exist in the npm registry first
Verification Requirements
- Read files before editing them — understand existing code before modifying
- Verify package existence before installing:
npm view <package>or check npmjs.com - Confirm current state before claiming status — check git, files, build output
- Check tool availability before assuming it is installed
Attribution
Do NOT include AI attribution in commits, PR bodies, code comments, or any content. When block_ai_attribution is enabled in .rea/policy.yaml, the commit-msg hook REJECTS commits containing structural AI attribution (Co-Authored-By with AI names, 'Generated with [Tool]' footers, etc.). The attribution-advisory hook also blocks gh pr create/edit and git commit commands with attribution. You must remove all attribution markers before committing — the hooks will NOT silently fix them.
Human-in-the-Loop Escalation
When you encounter an unexpected blocker, ambiguous requirement, or situation not covered by the current context:
- STOP — do not invent a workaround or make assumptions
- Describe the situation clearly: what you tried, what failed, what you need
- Wait for explicit human instruction before proceeding
The cost of pausing is always lower than the cost of acting incorrectly.
Policy File
Read .rea/policy.yaml at the start of every session to confirm:
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.
- 2mo ago First seen · 96 lines · 1,227 tokens per session scan A 852ae88113ae
helixir CLAUDE.md is an instructions file published in the GitHub repository bookedsolidtech/helixir (5 stars, last pushed 4mo ago), licensed MIT. It adds 1,227 tokens to every session, about $0.0049 per session on Opus 5.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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.