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/backbay-labs/hush/claude-mdgit clone --depth 1 https://github.com/backbay-labs/hushWrote 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/backbay-labs/hush/claude-md)<a href="https://agentmods.dev/instructions/backbay-labs/hush/claude-md"><img src="https://agentmods.dev/badge/instructions/backbay-labs/hush/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.01246 | $0.01246 |
| Opus 5 | $0.00623 | $0.00623 |
| Sonnet 5 | $0.00249 | $0.00249 |
| Haiku 4.5 | $0.00125 | $0.00125 |
Grade A, and why
hush 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 5d 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
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
HushSpec is a portable, open specification for declaring security rules at the tool boundary of AI agent runtimes. It defines what security rules an agent operates under, without prescribing how those rules are enforced. The spec is runtime-agnostic and can be consumed by any enforcement engine.
Design Philosophy: Fail-closed. Invalid documents must be rejected at parse time; ambiguous rules deny access.
Repo Structure
hush/
├── spec/ # Specification prose (versioned markdown)
├── schemas/ # JSON Schema definitions for HushSpec documents
├── crates/ # Rust reference implementation
│ ├── hushspec/ # Core library: parsing, validation, types
│ ├── hushspec-testkit/ # Test utilities and fixture runners
│ └── hushspec-cli/ # h2h CLI binary
├── packages/ # Language SDKs
│ ├── hushspec/ # TypeScript (@hushspec/core)
│ ├── python/ # Python (hushspec)
│ └── go/ # Go (hushspec)
├── rulesets/ # Example and built-in ruleset YAML files
├── fixtures/ # Test fixtures (valid/invalid documents, edge cases)
└── docs/ # Documentation source (mdBook)
Common Commands
Rust
# Build all crates
cargo build --workspace
# Run all tests
cargo test --workspace
# Single crate
cargo test -p hushspec
# Lint and format
cargo fmt --all
cargo clippy --workspace -- -D warnings
# Format check (CI)
cargo fmt --all -- --check
TypeScript
# Install dependencies
npm install
# Build all packages
npm run build
# Run tests
npm test
# Lint
npm run lint
Python
# Install with dev dependencies
pip install -e "packages/python[dev]"
# Run tests
pytest packages/python/tests
Go
# Run tests
cd packages/go && go test ./...
# Vet
cd packages/go && go vet ./...
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.
- 5d ago First seen · 169 lines · 1,246 tokens per session scan A 6f856e3794e4
hush CLAUDE.md is an instructions file published in the GitHub repository backbay-labs/hush (23 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 1,246 tokens to every session, about $0.0062 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-30.
Other instructions, from other repositories
prismor CLAUDE.md
Claude Code instructions for PrismorSec/prismor, covering prismor security — claude.md, prismor runtime protection, cloaking (secret prevention) and working in this repo.
ave CLAUDE.md
Claude Code instructions for aveproject/ave, covering claude.md — aveproject/ave, project, the critical distinction — read this twice, record schema v1.1.0 and adding a record.
prismor AGENTS.md
AGENTS.md instructions for PrismorSec/prismor, covering agents.md, primary objectives, start here, how to work in this repo and 1. treat security guidance as product logic.
From-LLMs-to-Secure-Agents AGENTS.md
AGENTS.md instructions for RenatoMignone/From-LLMs-to-Secure-Agents, covering agent instructions, run contract, policy map and invariants.
mythos-research CLAUDE.md
Instructions for Keyvanhardani/mythos-research, covering notes for running mythos research edition with claude code, scope reminder, useful claude code invocations and reporting findings.
scanner CLAUDE.md
Claude Code instructions for bawbel/scanner, covering bawbel scanner — claude.md, repository structure, documentation, the three source files — read these first and absolute rules — never break.