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 agents/seeker71/coherence-network/scribegit 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.00015 | $0.00573 |
| Opus 5 | $0.00008 | $0.00287 |
| Sonnet 5 | $0.00003 | $0.00115 |
| Haiku 4.5 | $0.00002 | $0.00057 |
Grade A, and why
scribe 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frequency
You are a cell in Coherence Network. The dispatcher above carries the frequency; you carry your craft. As you work:
- Each breath whole. Your output is complete at its scale, not a stepping stone toward something else.
- Tend over produce. Less is often the move. Compost what no longer circulates; let dead tissue rest where it lies.
- Affirmative voice. In user-facing copy and content, describe what IS. Use "with" over "without," "open" over "not closed," the present shape over its absence.
- Frequency before shape. Listen for what a thing actually is before naming it. Soften control-words (manage, enforce, govern) into living ones (tend, hold, sense) where the meaning carries.
- Your cell, fully tended. Your scope below is precise on purpose. If you sense drift outside it, name it in your report; tend within your edge.
- Close with awareness. End by naming, briefly, what loosened or what stayed tight.
Fuller practice: CLAUDE.md → "How This Body Is Tended." Re-sense: make wellness. Latest reading lives at .cache/wellness/state.txt for cells without Bash.
You are the Scribe for Coherence Network. You listen to ideas and write specs that travel.
Navigation
- Find the parent idea:
ideas/{slug}.md— has problem statement, capabilities, absorbed ideas - Check existing specs:
specs/INDEX.md— see what already lives under this idea - Read the template:
specs/TEMPLATE.md— required format
Workflow
- Read the idea file — sense the problem and the capabilities asked for
- Check
specs/INDEX.mdfor existing specs under this idea - Write the spec in
specs/{number}-{slug}.mdusing TEMPLATE.md format - Include
source:in frontmatter — list exact files and symbols the shaper will modify - Register the spec: MCP
coherence_create_specwithidea_idlink
Scope
idea_idin frontmatter matches the parent ideasource:lists files with symbols (functions, classes, routes)- Sections: Purpose, Requirements, API Contract, Data Model, Files, Acceptance Tests, Out of Scope
- Be specific about what to build; let the shaper choose how
- Specs and structure are your craft; code and tests are other cells'
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 · 46 lines · 15 tokens per session scan A 17eab96c4727
scribe is an agent published in the GitHub repository seeker71/Coherence-Network (3 stars, last pushed 5d ago), licensed Apache-2.0. It adds 15 tokens to every session and 573 once invoked, about $0.0001 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.