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.
npx agentmods add skills/beyondnetcode/evolith_arch32/architecture-governancenpx skills add beyondnetcode/evolith_arch32 --skill architecture-governancegit clone --depth 1 https://github.com/beyondnetcode/evolith_arch32Wrote 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/skills/beyondnetcode/evolith_arch32/architecture-governance)<a href="https://agentmods.dev/skills/beyondnetcode/evolith_arch32/architecture-governance"><img src="https://agentmods.dev/badge/skills/beyondnetcode/evolith_arch32/architecture-governance.svg" alt="Measured on agentmods" 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 | $0.00076 | $0.00811 |
| Opus 5 | $0.00038 | $0.00405 |
| Sonnet 5 | $0.00015 | $0.00162 |
| Haiku 4.5 | $0.00008 | $0.00081 |
Grade A, and why
architecture-governance 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 3d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture governance with Evolith
Validate a repository against an executable rule corpus, and report the verdict together with its coverage.
The one thing that matters
evolith validate returns four counts: checked, skipped, errored, total.
Never report a run as passing without stating skipped and errored. Those rules were
not evaluated. Their result is UNKNOWN, not passed. A run with 133 checked and 26 skipped is
not "133 rules passed" -- it is "133 evaluated, 26 unknown", and a blocking rule among the
unknown is a failure.
This is the whole reason the tool exists. Every other linter collapses "passed" and "never ran" into the same green, so their coverage and their compliance look identical.
How to run it
The repository must be an Evolith satellite: it needs an evolith.yaml. If there is none,
say so rather than initializing one uninvited -- evolith init writes to the user's repo.
evolith validate --engine opa --format json
If the CLI is not installed, use npx -y @beyondnet/evolith-cli validate --engine opa --format json.
Prefer --format json: it prints exactly one envelope on stdout and never prompts.
Reading the exit code
It is a taxonomy, not a boolean. Read it before reading the report.
| Code | Meaning | What to tell the user |
|---|---|---|
0 |
passed | Report the verdict, and still state the skipped count |
1 |
the tool failed | No verdict exists. Do not report compliance either way |
2 |
the gate blocked | A real verdict, and it says no |
3 |
invalid invocation | Nothing was evaluated. Fix the command |
1 and 3 are not weaker forms of 2. If you report them as "some issues found", you have
told the user their repository was examined when it was not.
Reading the report
From the JSON envelope's data:
status--passed,warningorfailedrulesChecked/rulesSkipped/rulesErrored/rulesTotalskippedRuleIds-- name them when the user asks what was not coveredissues[]-- each withblocking,ruleId,severity,fileselection-- which rulesets ran.source: core-defaultmeans the whole corpus; a caller selection means a narrower claim, and you must say so
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.
- 3d ago First seen · 78 lines · 76 tokens per session scan A cc807656b56b
architecture-governance is a skill published in the GitHub repository beyondnetcode/evolith_arch32 (0 stars, last pushed yesterday), licensed MIT. It adds 76 tokens to every session and 811 once invoked, about $0.0004 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 skills, from other repositories
command
Creates or modifies CLI commands in src/application/commands/. Use when adding a new command or subcommand, changing flags or the action handler, registering a command in cli.ts, or reviewing a command for thin-wrapper compliance. Do NOT use for implementing business logic — use use-case instead. Do NOT use for…
levelup-specify
Extract Context Directive Records (CDRs) from the current session after completing work. Identifies reusable patterns (rules, personas, examples, evals) and captures directive compliance cases for team-ai-directives.
evals-validate
Run evaluations and validate evaluator quality (SLA compliance, TPR/TNR, statistical accuracy). Executes PromptFoo or pytest DeepEval.
opensource-guide-coach
Use when a user wants guidance on starting, contributing to, growing, governing, funding, securing, or sustaining an open source project, or asks about contributor onboarding, community health, maintainer burnout, code of conduct, metrics, legal basics, or open source project adoption.
architecture-governance
Keep code changes conformant to a repo's real, declared architecture using ArchSteer. Use when starting work in an unfamiliar repo, before finishing/committing an architecturally significant change (new dependency, new data access, new external call, new layer), or when asked about a codebase's architecture, layers…
ai-usage-policy
Draft an organisation's AI acceptable-use policy — three data-sensitivity tiers with what may be put into a tool at each, permitted and prohibited uses stated as behaviours, a human-review matrix keyed to consequence, an approved-tool list with an exception route, and a named owner per rule. Use when a team needs…