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/vince-gonzalez/gonzalgoWrote 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/commands/vince-gonzalez/gonzalgo/why-this-axiom)<a href="https://agentmods.dev/commands/vince-gonzalez/gonzalgo/why-this-axiom"><img src="https://agentmods.dev/badge/commands/vince-gonzalez/gonzalgo/why-this-axiom/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/commands/vince-gonzalez/gonzalgo/why-this-axiom"><img src="https://agentmods.dev/badge/commands/vince-gonzalez/gonzalgo/why-this-axiom.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.00019 | $0.00377 |
| Opus 5 | $0.00010 | $0.00188 |
| Sonnet 5 | $0.00004 | $0.00075 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
why-this-axiom 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 11d 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.
What it actually says
Use the lean-axiom-provenance skill to explain why the declaration named in
$ARGUMENTS depends on an axiom, and whether the dependence is one that could be
rerouted.
Run gonzalgo why against the project's dump and read the path it returns. Each
hop is labelled stmt or proof and that label carries the answer:
- A statement edge means the theorem's own type mentions something that reaches the axiom. Removing it changes what the theorem says. Report it as required, not as a defect.
- A proof edge means a tactic or lemma choice put it there. A path made only of proof edges is the case worth investigating.
Then say what would actually be involved:
gonzalgo impacton the constant the path passes through, to show what a change would touch, split into dependents that name it in a statement and dependents that only use it in a proof.- Whether the constant is one that can be made constructive at all. A choice-free
type does not imply a constructive instance exists —
Classical.propDecidablehas a choice-free type, is reached by 91,858 theorems, and cannot be replaced.
Quote the path verbatim. Do not claim a constructive proof exists; this reports what the existing proof rests on and does not search for another one. If the answer is that the dependence is required by the statement, say so plainly — that is a real answer and the common one.
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.
- 11d ago First seen · 33 lines · 19 tokens per session scan A 521f2672a8b8
why-this-axiom is a command published in the GitHub repository vince-gonzalez/gonzalgo (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 19 tokens to every session and 377 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-08-31.
Other commands, from other repositories
brainblast-deploy-plan
Deployment Intelligence for Anchor programs. Run before anchor deploy so you know how much SOL you need and the exact ordered transaction sequence — instead of working it out by hand.
brainblast-oracle
Live On-Chain Intelligence: is the oracle fresh? Before you price anything against a Pyth / Switchboard / Chainlink feed, check when its account was last written.
brainblast-rico-maps
Runs a two-part token check on any Solana contract address (CA).
costguard-live
Plan and ingest an opt-in, consent-gated live billing check for a provider, conducted via the playwriter MCP server (read-only browser reads over your logged-in session). costguard never drives the browser itself.
proofrag
Evaluate a RAG/LLM app — generate a golden set, judge it, and produce a scorecard.
goal-audit
Attack the goal's own acceptance criteria — ledger integrity, negative control, and mutation probe (does not consume an iteration).