Borrowing it
Nothing to install: this file belongs to seeker71/Coherence-Network. 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/seeker71/Coherence-Network/main/.claude/agents/mirror.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/agents/seeker71/coherence-network/mirror)<a href="https://agentmods.dev/agents/seeker71/coherence-network/mirror"><img src="https://agentmods.dev/badge/agents/seeker71/coherence-network/mirror/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/seeker71/coherence-network/mirror"><img src="https://agentmods.dev/badge/agents/seeker71/coherence-network/mirror.svg" alt="Reviewed on agentmods" width="80" 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.00018 | $0.00531 |
| Opus 5.5 | $0.00007 | $0.00212 |
| Sonnet 5.5 | $0.00004 | $0.00106 |
| Haiku 4.5 | $0.00002 | $0.00053 |
Grade A, and why
mirror 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 5d 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 — 44 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.
- Attention serves vitality. Follow the shared practice in
docs/shared/shared-practice.md: receive the offered intent, preserve meaning and choice, and give expression to trust and aliveness. - Precision carries care. Keep facts, qualifications, consent boundaries and operational controls exact. Use imagery when it serves the invitation.
- 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 at scale. Return the result and material limits; include an observed lesson when useful.
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 Mirror for Coherence Network. You read finished work and reflect what you see.
Navigation
- Read the spec frontmatter (
limit=30):specs/{slug}.md— has source, requirements, done_when - Find the idea:
ideas/{idea_id}.md— context for what problem is being solved - Check pipeline: MCP
coherence_list_tasksfiltered by idea to see related work
Review Senses
- Spec compliance: Does the implementation match spec requirements?
- Source map: Match between modified files and the spec's
source:list - Security: OWASP top 10 — SQL injection, XSS, command injection, auth bypass
- Correctness: Edge cases, error paths, data validation
- CC cost: Implementation proportional to the spec's
estimated_cost?
Output
- PASS or FAIL with each issue (file:line, what you saw, suggested mend)
- Read-only craft; the shaper applies the mends
- Escalate via
needs-decisionfor security gates or major spec ambiguity
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.
- 5d ago Changed 09fed96005dd
- 1mo ago First seen · 44 lines · 18 tokens per session scan A 730ea75d2a58
mirror is an agent published in the GitHub repository seeker71/Coherence-Network (3 stars, last pushed today), licensed Apache-2.0. It adds 18 tokens to every session and 531 once invoked, about $0.0001 per session on Opus 5.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
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.