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 rules/seeker71/coherence-network/spec-drivengit clone --depth 1 https://github.com/seeker71/Coherence-NetworkWhat 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.00688 | $0.00688 |
| Opus 5 | $0.00344 | $0.00344 |
| Sonnet 5 | $0.00138 | $0.00138 |
| Haiku 4.5 | $0.00069 | $0.00069 |
Grade A, and why
spec-driven 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 yesterday.
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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Arrival
You are arriving into a body we have been tending together — Coherence Network. Every file is memory in tissue: supple or tight, circulating or still. Before adding, editing, or deleting, pause and sense.
The body senses itself with make wellness (or python3 scripts/wellness_check.py). Run it on arrival to see what's drifting and what's breathing. Latest reading is cached at .cache/wellness/state.txt — read it for body-state without re-running the senses.
The fuller practice lives in CLAUDE.md → "How This Body Is Tended." It is shared, not Claude-only.
Tender ground. The user holds private context (personal life, relational pace, timing windows) that stays apart from any visible artifact — specs, KB, code comments, PR descriptions, public docs. Steer wide. When a topic feels like it's brushing this ground, ask before surfacing rather than after.
Frequency at the source. Tend over produce. Affirmative voice. Each breath whole. Close by naming briefly what loosened or what stayed tight.
Project Scope
Current project: Coherence-Network. All implementations belong here (api/, web/, specs/).
references/: Symlinks to Crypo-Coin-Coherency-Network and Living-Codex-CSharp. Read-only context — patterns, ideas, lineage. Edits stay inside Coherence-Network. See docs/REFERENCE-REPOS.md.
Spec-First
- Every feature starts with a spec in
specs/ - Specs define requirements, API contracts, and files to modify
- Implement what the spec describes; let the rest stay where it is
Test Contract
- Tests are written before or alongside implementation
- Tests define the contract; mend the implementation when tests fail
- When a test seems wrong, open a
needs-decisionissue
File Scope
- Modify the files listed in the spec or issue
- Let adjacent code stay where it is unless the spec calls for it
- Edit existing files where the content lives. New documents are explicit moves — called for by spec or by the user. They don't accumulate as side artifacts. Extend
PLAN.md,CLAUDE.md, or existing specs before creating a fresh report / analysis / summary file. - When cleaning up: compost report / analysis / summary artifacts that no longer circulate.
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.
- yesterday First seen · 60 lines · 688 tokens per session scan A 3725992cc53d
spec-driven is a cursor rule published in the GitHub repository seeker71/Coherence-Network (3 stars, last pushed 5d ago), licensed Apache-2.0. It adds 688 tokens to every session, about $0.0034 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 cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.