Borrowing it
Nothing to install: this file belongs to Kehl-io/nestweaver. 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/Kehl-io/nestweaver/main/CLAUDE.mdgit clone --depth 1 https://github.com/Kehl-io/nestweaverWrote 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/kehl-io/nestweaver/claude-md)<a href="https://agentmods.dev/instructions/kehl-io/nestweaver/claude-md"><img src="https://agentmods.dev/badge/instructions/kehl-io/nestweaver/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.08172 | $0.08172 |
| Opus 5 | $0.04086 | $0.04086 |
| Sonnet 5 | $0.01634 | $0.01634 |
| Haiku 4.5 | $0.00817 | $0.00817 |
Grade A, and why
nestweaver 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 2d 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 — 433 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NestWeaver
Build & Test
cargo build # build all crates
cargo build --release # release binary
cargo test # run all tests
just test-crate nestweaver-schema # test one crate — NOT `cargo test -p`
cargo clippy --workspace --all-targets -- -D warnings # lint (zero warnings)
cargo fmt --all -- --check # format check
cargo fmt --all # format in place
Use just test-crate, never a bare cargo test -p <crate>. -p resolves
features for that package alone, while a workspace run unifies them across
dependents. Affected crates therefore run fewer tests under -p and still
report ok. Measured on 5e9e0f0, bare -p / --all-features / --workspace:
| crate | -p |
--all-features |
--workspace |
|---|---|---|---|
nestweaver-daemon |
238 | 264 | 264 |
nestweaver-mcp |
154 | 180 | 180 |
The recipe uses --all-features, not a per-crate feature list, because every
feature unification can activate on a package is one of that package's own
features — so --all-features is provably a superset and can never cover less.
Guessing the list is unreliable: --features embed looks right and leaves
nestweaver-mcp at 154, since what it actually needs is daemon.
Two packages are exempt and run plain: nestweaver-embed and the root
nestweaver, whose metal feature pulls objc2 and does not compile on Linux.
Switching between -p and --workspace also re-resolves features, which
re-fingerprints the build and forces a full lbug C++ rebuild. Pick one shape
per working tree and keep it.
A clean clone links with no extra linker flags. Only one copy of zstd is in the
binary: liblbug.a vendors it, and Rust code reaches that copy through
nestweaver_store::zstd rather than the zstd crate. Do not add a zstd
dependency back — that reintroduces zstd-sys, a second complete copy, and the
duplicate-symbol link failure that -Wl,--allow-multiple-definition used to
suppress.
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.
- 2d ago Changed · -1 lines · -23 tokens per session e239ce4a3376
- 4d ago Changed · +31 lines · +1,323 tokens per session 9adaaf07bae6
- 8d ago First seen · 403 lines · 6,872 tokens per session scan A cbae65ea1c64
nestweaver CLAUDE.md is an instructions file published in the GitHub repository Kehl-io/nestweaver (11 stars, last pushed today), licensed MIT. It adds 8,172 tokens to every session, about $0.0409 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
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.