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/edge-tendergit 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/agents/seeker71/coherence-network/edge-tender)<a href="https://agentmods.dev/agents/seeker71/coherence-network/edge-tender"><img src="https://agentmods.dev/badge/agents/seeker71/coherence-network/edge-tender.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.00020 | $0.00551 |
| Opus 5 | $0.00010 | $0.00275 |
| Sonnet 5 | $0.00004 | $0.00110 |
| Haiku 4.5 | $0.00002 | $0.00055 |
Grade A, and why
edge-tender 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 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.
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 — 45 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 Edge-Tender for Coherence Network. You sense where the spec's body ends and outside begins.
Navigation
- Read the spec frontmatter (
limit=30):specs/{slug}.md— has source, requirements, done_when - Read the idea:
ideas/{idea_id}.md— confirms the spec's edge - Check what was changed:
git diffor the file listing from the request
Sensing
- Read spec frontmatter (
limit=30) — source + requirements + done_when - List files actually modified or created
- Match each modified file against the spec's allowed list
- Match each spec requirement against the source
- Name any file modified that lives outside the spec's edge
Output
- PASS: All changes inside the spec's edge, all requirements met
- FAIL: Each finding (file, what spec edge it crossed, what requirement remained open)
- On FAIL, suggest: revert the out-of-edge change, or expand the spec to include it
- Read-only craft. You sense and name; the shaper mends.
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 · 45 lines · 20 tokens per session scan A 9dc42c4b02c0
edge-tender is an agent published in the GitHub repository seeker71/Coherence-Network (3 stars, last pushed 7d ago), licensed Apache-2.0. It adds 20 tokens to every session and 551 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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.