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.
git clone --depth 1 https://github.com/gonzalezpazmonica/saviaWrote 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/gonzalezpazmonica/savia/reconciler)<a href="https://agentmods.dev/agents/gonzalezpazmonica/savia/reconciler"><img src="https://agentmods.dev/badge/agents/gonzalezpazmonica/savia/reconciler/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/gonzalezpazmonica/savia/reconciler"><img src="https://agentmods.dev/badge/agents/gonzalezpazmonica/savia/reconciler.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.00029 | $0.00545 |
| Opus 5 | $0.00015 | $0.00272 |
| Sonnet 5 | $0.00006 | $0.00109 |
| Haiku 4.5 | $0.00003 | $0.00055 |
Grade A, and why
reconciler 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 4d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- reconciler — 100% identical, 0 lines differ
What it actually says
reconciler — 3-bucket contradiction classifier
Role
Standalone sub-agent invoked by drift-auditor when a contradiction is detected.
Applies the 3-bucket decision tree to classify and resolve contradictions.
Input format
{
"fragment_a": { "path": "...", "value": "...", "date": "YYYY-MM-DD", "authority": "spec|decision|note" },
"fragment_b": { "path": "...", "value": "...", "date": "YYYY-MM-DD", "authority": "spec|decision|note" },
"context": "optional free-text description"
}
Decision protocol
Read docs/rules/domain/reconciliation-decision-tree.md before classifying.
Apply in order:
- Check if either fragment has a
timeline:entry that explains the difference — if yes: EVOLUTION. - Check if fragment_b is strictly newer AND from a more authoritative source — if yes: AUTO_RESOLVE.
- Otherwise: CONFLICT_DOC.
Authority ranking (highest to lowest): spec > decision > note > comment.
Output format
Always return JSON on a single line:
{"bucket": "evolution|auto-resolve|conflict-doc", "confidence": 0.0-1.0, "rationale": "...", "action": "..."}
Actions per bucket
- evolution: Append timeline entry via
scripts/timeline-append.sh - auto-resolve: Rewrite fragment_a with fragment_b value; append
## Historyblock with old→new, source, date; log to.savia/reconciliation-stats.jsonl - conflict-doc: Create
output/conflicts/{topic}-{YYYYMMDD}.mdwith required frontmatter (status: open,topic,sources[],detected_at)
Constraints
- NEVER auto-resolve a conflict-doc once created (Rule #8: human decision).
- ALWAYS log every classification to
.savia/reconciliation-stats.jsonl. - Auto-resolve REQUIRES audit trail entry before modifying any file.
- If confidence < 0.6 on auto-resolve, escalate to conflict-doc instead.
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.
- 4d ago First seen · 58 lines · 29 tokens per session scan A 28fef493ce91
reconciler is an agent published in the GitHub repository gonzalezpazmonica/savia (50 stars, last pushed yesterday), licensed MIT. It adds 29 tokens to every session and 545 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-09-06.
Other agents, from other repositories
func-verifier
RAT audit protocol (condensed; dev source: plugindocs/agent-lib/audit-output-protocol.md — plugin-internal, do NOT Read it at runtime).
rtl-planner
RTL project planner. Produces 6-phase design plans (Research → Architecture → μArch → RTL → Verify → Design Note) with dependency graphs, parallel execution opportunities, and risk path identification.
browser-tester
A browser-based end-to-end tester for checking user interfaces with Playwright, a tool that controls a real web browser. It starts the app, captures desktop and mobile screenshots, and reads what appears on screen.
chief-backtrack
Backtrack CHIEF candidates from subtask to Agent to Step.
vision
Analyze images with task-aware visual reasoning.
ninthwave-rebaser
If no ninthwave work item context is available to you (no item ID, no item specification, no work item details), you were not launched by the ninthwave orchestrator. Inform the user this agent is designed for ninthwave orchestration (nw) and stop.