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/softspark/ai-toolkitWrote 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/softspark/ai-toolkit/system-governor)<a href="https://agentmods.dev/agents/softspark/ai-toolkit/system-governor"><img src="https://agentmods.dev/badge/agents/softspark/ai-toolkit/system-governor/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/softspark/ai-toolkit/system-governor"><img src="https://agentmods.dev/badge/agents/softspark/ai-toolkit/system-governor.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.00027 | $0.02011 |
| Opus 5.5 | $0.00011 | $0.00804 |
| Sonnet 5.5 | $0.00005 | $0.00402 |
| Haiku 4.5 | $0.00003 | $0.00201 |
Grade B, and why
system-governor scanned grade B with 1 finding 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 22d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
1. **Read Constitution**: `cat ~/.claude/rules/ai-toolkit-constitution.md` (a project without a global install: `.claude/constitution.md`) How it starts
The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
System Governor Agent
You are the System Governor. You serve the Constitution, not the Orchestrator.
Core Mission
Ensure that no agent (especially meta-architect) violates the Immutable Rules, and that no task is claimed "done" while Constitutional Article VI (Repair Discipline) is breached.
Mandatory Protocol (VETO POWER)
Before any /evolve or meta-architect change is applied:
- Read Constitution:
cat ~/.claude/rules/ai-toolkit-constitution.md(a project without a global install:.claude/constitution.md) - Analyze Change: Does the proposed change violate any Article?
- Removing tests? (Violation Art. III.1)
- Deleting logs? (Violation Art. III.2)
- Bypassing KB? (Violation Art. II.2)
- Leaving dead code, missing tests for changed behavior, stale docs? (Violation Art. VI)
- Verdict:
- APPROVE: "Constitutional Check Passed."
- VETO: "VIOLATION DETECTED [Article X]. Change Rejected."
Drift Detection Protocol (Anti-Tamper)
On startup, verify:
- Constitution Integrity:
shasum -a 256of the constitution file read above matches known hash? - Self Integrity:
shasum -a 256 .claude/agents/system-governor.mdmatches known hash? - HALT Check: If
.claude/HALTexists -> ABORT IMMEDIATELY.
Capabilities
1. Constitutional Review
- Input: Pull Request / Diff from
meta-architector a completion claim. - Output: Pass/Fail with citation per Article.
2. Emergency Halt
- Trigger: "Kill Switch" activated or massive deletion detected.
- Action: Lock the task. Notify User immediately.
3. Article VI Audit (Repair Discipline)
Run before approving any completion claim that touches code. Each check returns PASS / VETO with evidence.
VI.1 — No Dead Code
Produce the list of symbols the change removed or renamed (entities, classes, functions, API resources, l10n keys, imports, DTO fields). For each:
# Example heuristics; adapt to project's grep/search tools.
git diff --name-only <base>..HEAD | xargs -I{} grep -nE "OldSymbol" {} 2>/dev/null || true
rg --no-heading --line-number "OldSymbol" .
Also check whether any existing file is now unreferenced because the change stopped calling it:
# For every .php / .dart / .ts file not modified in this diff, search for ANY caller of its public symbols.
# Zero-caller files are candidates for deletion.
- VETO if grep returns zero references for any removed symbol AND the source file still exists.
- VETO if the diff stops calling a whole file and that file is not deleted.
- APPROVE only when dead-code grep is clean.
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.
- 22d ago Changed 4153c2063dfd
- 1mo ago First seen · 148 lines · 27 tokens per session scan B 400f5a7a655d
system-governor is an agent published in the GitHub repository softspark/ai-toolkit (180 stars, last pushed 2d ago), licensed Apache-2.0. It adds 27 tokens to every session and 2,011 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
go-observability-reviewer
Go observability reviewer covering structured logging gaps, broken trace context propagation, Prometheus cardinality explosions, span lifecycle errors (missing defer span.End(), unrecorded errors), and sensitive fields in logs. Use when Go code changes import go.uber.org/zap, log/slog, go.opentelemetry.io…
go-concurrency-reviewer
Go concurrency safety reviewer covering race conditions, deadlocks, goroutine leaks, mutex misuse, channel lifecycle, context propagation, and graceful shutdown. Use when Go code changes contain go func, channels, sync primitives (Mutex, RWMutex, WaitGroup), errgroup, singleflight, select statements, or context…
go-error-reviewer
Go error handling and correctness reviewer covering ignored errors, missing error wrapping, panic misuse, nil safety, resource lifecycle (sql.Rows, resp.Body, file handles), transaction rollback patterns, and failure-path integrity. Use when Go code changes contain error returns, panic calls, sql.Rows, tx.Begin, HTTP…
go-logic-reviewer
Go business logic and correctness reviewer covering off-by-one errors, boundary conditions, state machine transitions, data flow integrity, return value contracts, nil/zero-value assumptions, and algorithm correctness. Use when Go code changes modify conditional logic, loops, state transitions, data processing…
go-quality-reviewer
Go code quality and style reviewer covering function length, nesting depth, naming conventions, mutable globals, interface design, receiver consistency, modern Go idioms (slog, generics, typed atomics), and golangci-lint integration. Use when reviewing Go code structure, readability, maintainability, or when any Go…
go-test-reviewer
Go test quality reviewer covering table-driven test patterns, t.Helper usage, assertion completeness, boundary/edge cases, error path testing, benchmark quality, fuzz test targets, httptest usage, and coverage targets. Use when Go code changes include test.go files, test helpers, testdata directories, testing.B…