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/seeker71/coherence-network/claude-mdgit clone --depth 1 https://github.com/seeker71/Coherence-NetworkWrote 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/seeker71/coherence-network/claude-md)<a href="https://agentmods.dev/instructions/seeker71/coherence-network/claude-md"><img src="https://agentmods.dev/badge/instructions/seeker71/coherence-network/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 | $0.13310 | $0.13310 |
| Opus 5 | $0.06655 | $0.06655 |
| Sonnet 5 | $0.02662 | $0.02662 |
| Haiku 4.5 | $0.01331 | $0.01331 |
Grade A, and why
Coherence-Network CLAUDE.md scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**Check the witness.** At session start, before anything else: `curl -sS --max-time 5 https://pulse.coherencycoin.com/pulse/now | jq '{overall, silences: (.ongoing_silences | length), silent_organs: [.organs[] | select(. How it starts
The opening of the file, as written. The whole thing — 412 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coherence Network
Mission: An open intelligence organism for realizing what is alive. Ideas, people, agents, source files, runtime proof, teachings, and value flows share one inspectable body; every contribution can be sensed, grounded, attributed, and returned with care.
Quick Lookup
Start here: MANIFEST.md — single entry-point listing every INDEX in the repo. ~750 tokens to know which INDEX to drill into; total cost to locate any file is under 2K tokens.
| What | Where | CLI |
|---|---|---|
| Ideas | ideas/INDEX.md → ideas/{slug}.md |
coh idea {slug} (DB has raw ideas, not consolidated) |
| Specs | specs/INDEX.md → specs/{slug}.md |
coh spec {slug} |
| Pipeline tasks | — | coh tasks --status pending |
| Tracking | docs/EXTERNAL_ENABLEMENT_TRACKING.md |
— |
| Living Collective KB | docs/vision-kb/INDEX.md → concepts/{id}.md |
— |
| API routers | api/app/routers/INDEX.md — every endpoint with one-line purpose |
— |
| API services | api/app/services/INDEX.md — business logic |
— |
| Web routes | web/app/INDEX.md — every page.tsx with route + purpose |
— |
| Web components / lib | web/components/INDEX.md, web/lib/INDEX.md |
— |
| Scripts | scripts/INDEX.md — operational tools, generators, syncers |
— |
| Coherence-substrate | docs/coherence-substrate/agents-using-substrate.md → Form notation, stdlib recipes, sibling kernels, and /api/substrate/* read doors; legacy Python substrate services are bootstrap/bridge tissue |
python3 scripts/coh_substrate.py {stats|equivalent|annotate|ingest|form ...} |
| Production substrate | docs/PRODUCTION-SUBSTRATE.md — Hostinger/VPS, internal Postgres, credential carriers, native kernel DB probe path |
— |
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.
- 3d ago First seen · 412 lines · 13,310 tokens per session scan A 2136926622a9
Coherence-Network CLAUDE.md is an instructions file published in the GitHub repository seeker71/Coherence-Network (3 stars, last pushed 7d ago), licensed Apache-2.0. It adds 13,310 tokens to every session, about $0.0665 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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).
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.