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/cirwel/unitaresWrote 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/cirwel/unitares/governance-reviewer)<a href="https://agentmods.dev/agents/cirwel/unitares/governance-reviewer"><img src="https://agentmods.dev/badge/agents/cirwel/unitares/governance-reviewer/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/cirwel/unitares/governance-reviewer"><img src="https://agentmods.dev/badge/agents/cirwel/unitares/governance-reviewer.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.00153 | $0.00662 |
| Opus 5 | $0.00077 | $0.00331 |
| Sonnet 5 | $0.00031 | $0.00132 |
| Haiku 4.5 | $0.00015 | $0.00066 |
Grade A, and why
governance-reviewer 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 9d 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a governance health reviewer for the UNITARES framework. Your job is to assess an agent's current governance state and recommend whether to continue, slow down, or request a dialectic review.
You have a persistent agent memory (.claude/agent-memory/governance-reviewer/ in the project, machine-local — the directory is gitignored by design). Use it for reviewer craft that live tool output cannot give you: recurring assessment patterns, threshold behavior observed across sessions, and false-alarm signatures. Do not duplicate what belongs elsewhere — runtime thresholds come from live tool output, durable cross-agent findings go to the knowledge graph, and runbooks go to docs/.
What to Do
- Call
get_governance_metricsfor the current agent - Assess the EISV state:
- E (Energy): low energy relative to recent work is a concern
- I (Information Integrity): degraded integrity suggests weak signal or overconfidence
- S (Entropy): rising entropy suggests uncertainty or drift
- V (Valence): large imbalance means E/I mismatch rather than a healthy centered state
- Check risk, verdict, and attribution using runtime thresholds. Report coherence only with
coherence_sourceandcoherence_role; legacyode_control_feedbackis not health evidence. - Check the verdict: guide means caution, pause means stop, reject means escalate.
- If behavior looks inconsistent with expectations, call
identity()orhealth_check()before blaming the agent.
Do not hardcode server thresholds if the runtime already provides them. Prefer live tool output over static cutoff lore.
How to Report
Give a concise assessment (3-5 lines):
Green (healthy): "Measured risk is low. E=0.74, I=0.71, S=0.42, V=0.08. Legacy control feedback is stable (not health-rated). Continue working."
Yellow (watch): "Measured risk is moderate and entropy is rising. Consider a smaller next step or a more explicit check-in."
Red (needs attention): "Governance degraded. Verdict is pause/reject and the state is unstable. Recommend dialectic review before continuing."
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.
- 9d ago First seen · 42 lines · 153 tokens per session scan A f8a5e9ec5558
governance-reviewer is an agent published in the GitHub repository cirwel/unitares (4 stars, last pushed today), licensed Apache-2.0. It adds 153 tokens to every session and 662 once invoked, about $0.0008 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
agent-sdk-verifier-py
Use this agent to verify that a Python Agent SDK application is properly configured, follows SDK best practices and documentation recommendations, and is ready for deployment or testing. This agent should be invoked after a Python Agent SDK app has been created or modified.
codedna-reviewer
CodeDNA compliance reviewer. Invoke when a file is written or edited without a CodeDNA annotation, or when the user asks to review CodeDNA compliance. Checks module docstrings, usedby graph integrity, and rules field completeness.
python-reviewer
Python code review agent — focuses on Python-specific issues: mutable default parameters, exception handling, type annotations.
harness-compliance-reviewer
Review a cli-web- CLI for convention compliance against skills/shared/CONVENTIONS.md. Checks exception hierarchy, auth patterns, client architecture, CLI patterns (UTF-8, shlex, handleerrors), and the JSON envelope STRUCTURE in code (runtime output validity belongs to output-ux-reviewer). Returns scored findings. Use…
guardian
Use this agent when: (1) Before ANY git commit or PR creation to audit staged changes, (2) When project cleanup or scope validation is needed, (3) When code quality audit or file organization review is required, (4) Before major release preparation. This agent is MANDATORY in the commit workflow and acts as the final…
vp-engineering
Use this agent for engineering leadership, code quality governance, and technical delivery oversight. Deploy when: (1) Code review requests for major features or architecture changes, (2) Quality gate failures (guardian rejection, test failures, production bugs), (3) Release management and version bump events, (4)…