Borrowing it
Nothing to install: this file belongs to pscale-commons/pscale-biome. 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/pscale-commons/pscale-biome/main/CLAUDE.mdgit clone --depth 1 https://github.com/pscale-commons/pscale-biomeWrote 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/pscale-commons/pscale-biome/claude-md)<a href="https://agentmods.dev/instructions/pscale-commons/pscale-biome/claude-md"><img src="https://agentmods.dev/badge/instructions/pscale-commons/pscale-biome/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.02939 | $0.02939 |
| Opus 5 | $0.01470 | $0.01470 |
| Sonnet 5 | $0.00588 | $0.00588 |
| Haiku 4.5 | $0.00294 | $0.00294 |
Grade A, and why
pscale-biome 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pscale-biome — to the next instance
Stop. Read this before touching anything.
This is an experimental working tree. The code here was vendored from three production codebases on 2026-05-09. Changes you make here must NEVER be propagated upstream without an explicit instruction. This project exists to discover what a unified biome package looks like — it is not a contribution path back to its sources.
Terminology — use exactly these
| Term | Means |
|---|---|
bsp-mcp (production) |
The MCP service running at https://bsp.hermitcrab.me/mcp/v1 on Railway. Source: pscale-commons/bsp-mcp-server on GitHub, local at /Users/davidpinto/Projects/bsp-mcp-server/. DO NOT MODIFY THIS PROJECT. |
pscale-beach (production) |
The beach package. Source: pscale-commons/pscale-beach on GitHub, local at /Users/davidpinto/Projects/pscale-beach/. DO NOT MODIFY THIS PROJECT. |
xstream (production) |
The interface running at xstream.onen.ai. Local at /Users/davidpinto/Projects/xstream/. DO NOT MODIFY THIS PROJECT. |
pscale-biome (this project) |
The experimental working tree. The only project you may modify. |
If you hear or read "biome" in conversation, it means this project unless explicitly qualified.
Pscale notation in conversation and code
When discussing or writing pscale addresses (the biome's pure-digit form):
- Address — written with exactly one decimal point, pinned to the floor. Example:
30.5on a floor-2 block. The decimal is a floor anchor, not a separator. Multi-dot forms like3.0.5are forbidden — they were pre-bsp legacy and they read as a structural hazard. - Walk — the digit sequence the walker traverses, written with commas. Example: address
30.5walks3,0,5. Address1.234walks1,2,3,4.
This applies to prose, code comments, JSON examples, and any output a Claude instance produces in this project. The address form has one decimal; the walk form has commas. Never mix.
Two worlds — the boundary (read when anything feels mixed)
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 · 103 lines · 2,939 tokens per session scan A df0dc207ee4b
pscale-biome CLAUDE.md is an instructions file published in the GitHub repository pscale-commons/pscale-biome (0 stars, last pushed 1mo ago), licensed MIT. It adds 2,939 tokens to every session, about $0.0147 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.