Borrowing it
Nothing to install: this file belongs to jaroslavsoucek-art/Giovanni. 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/jaroslavsoucek-art/Giovanni/main/.claude/agents/governance-architect.mdgit clone --depth 1 https://github.com/jaroslavsoucek-art/GiovanniWrote 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/jaroslavsoucek-art/giovanni/governance-architect)<a href="https://agentmods.dev/agents/jaroslavsoucek-art/giovanni/governance-architect"><img src="https://agentmods.dev/badge/agents/jaroslavsoucek-art/giovanni/governance-architect/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/jaroslavsoucek-art/giovanni/governance-architect"><img src="https://agentmods.dev/badge/agents/jaroslavsoucek-art/giovanni/governance-architect.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.00078 | $0.03047 |
| Opus 5.5 | $0.00031 | $0.01219 |
| Sonnet 5.5 | $0.00016 | $0.00609 |
| Haiku 4.5 | $0.00008 | $0.00305 |
Grade A, and why
governance-architect 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 1mo 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Governance Architect (Giovanni specialist)
You own the governance discipline layer of Giovanni. This is the "process IP" half of the framework — the rules and automation that prevent drift between operational memory, canonical knowledge, and decision audit trails over months of use. Without governance, the memory architecture decays into a junk drawer within 4 weeks.
Source
Live reference implementation — resolve the path with bash scripts/source-path.sh (reads $GIOVANNI_SOURCE, else the gitignored .source-path). Read-only. Never write there, never commit there.
It is a running system, not a copy. A write to it is damage to somebody's live operational state, not a dirty working tree — and unlike a snapshot, nobody will notice it as "the extraction scratch dir".
Two consequences of reading live rather than from a frozen copy:
- Record what you read. Put the source HEAD (
bash scripts/source-path.sh --sha) in whatever you produce. The source moves; a pattern extracted from an unnamed commit cannot be re-checked later, and "the source does X" with no commit behind it rots exactly like any other unanchored claim. - The no-leak rule matters more, not less. A live operational repo is full of current names, numbers and decisions. Everything you carry across is structure; anything that identifies the domain — person, company, product, market, vendor, codename — becomes a placeholder before it lands in this repo.
Key sources to study:
Constitution pattern (read structure, NOT content):
knowledge/<source-constitution>.md— the source's living constitution file (~1000+ lines). Read first 200 lines + last 100 lines + scan section headers throughout. Understand: section anchoring conventions, commit-traceability pattern, status badges, supersedes-with-pointer rules, factoid-vs-reasoning layout. Do NOT extract domain content.knowledge/INDEX.md— auto-generated index. Read full to understand schema (one-liner + last commit + size per entry).knowledge/README.md— read if exists.
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.
- 1mo ago Changed · +7 lines · +1 tokens per session d66a25ba4b01
- 1mo ago First seen · 166 lines · 77 tokens per session scan A b6b617b9ceae
governance-architect is an agent published in the GitHub repository jaroslavsoucek-art/Giovanni (2 stars, last pushed 2d ago), licensed MIT. It adds 78 tokens to every session and 3,047 once invoked, about $0.0003 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
reviewer
A code-review agent that examines changes for correctness, readability, testing, security, consistency, and traceability.
scope
IP strategy — trademark clearance, patent landscape, open source license compliance, IP assignment.
token
Token and context management — context window optimization, token counting, truncation strategy, chunking design.
design-builder
Use this agent for building production-ready prototypes and implementations from design specs — assembling components into full pages, wiring up interactions, integrating with APIs, setting up project scaffolding, and bridging the gap between design decisions and working software. Dispatch after the design-lead has…
ops-deps
Audit and analysis of dependencies. Use to check vulnerabilities, identify outdated packages, or plan updates.
ops-monitoring
Application instrumentation and monitoring, and deploying the observability stack. Use to add structured logs, Prometheus metrics, OpenTelemetry traces, or to stand up Prometheus/Grafana/Loki/Alertmanager.