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 agents/get-tmonier/argot/calibration-contractgit clone --depth 1 https://github.com/get-tmonier/argotWrote 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/get-tmonier/argot/calibration-contract)<a href="https://agentmods.dev/agents/get-tmonier/argot/calibration-contract"><img src="https://agentmods.dev/badge/agents/get-tmonier/argot/calibration-contract.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.00000 | $0.02493 |
| Opus 5 | $0.00000 | $0.01247 |
| Sonnet 5 | $0.00000 | $0.00499 |
| Haiku 4.5 | $0.00000 | $0.00249 |
Grade A, and why
calibration-contract 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 5d 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 — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
G7 Calibration Contract
Status: binding (era-13.5 gate G7)
Code: crates/argot-core/src/scoring/calibration.rs — run_calibrate (multi-seed median threshold)
The problem: symmetric firing cancels recall
During era-13 Phase 10 development, every new optional contribution tested (cluster-rare-threshold rule, Phase-4 ShapePrimitive penalties) was measured against the calibrated threshold and found to add ~zero recall. The cause is structural:
Any additive contribution that fires symmetrically on calibration hunks and fixture hunks inflates the per-corpus threshold by the same magnitude it adds to fixture scores. The net catch impact is ~zero.
Empirical evidence: the era-13 Phase A scout (docs/research/evidence/era13-final.md
§ cancellation) confirmed that with cluster_rare_threshold=2, all three corpora
(faker-js, fastapi, hono) had exactly 200–280 rare-branch fires per calibration
seed. The threshold rose by exactly cluster_bonus = 5.0 — matching the
observed scout t_sym − t_asym = 5.0000 on every corpus.
Why suppressing on the cal path is mathematically sound
The cancellation argument assumes both paths use the same scorer. The fix is to break that symmetry at the calibration boundary, not inside the scorer.
Era-11 cluster_bonus is already asymmetric by construction
Calibration hunks are sampled from model_a_files — files whose callee bags are
typical for their cluster. By construction, these files' callees are within
their cluster's attested set, so the cluster-absent-callee branch of
weighted_contribution_for_file does not fire on calibration hunks. Era-11's
cluster_bonus is asymmetric without any special plumbing.
New optional contributions are not asymmetric by construction
The cluster-rare rule fires when a callee is attested in ≤ N cluster files — a
Zipf-distribution property shared by typical code and anomalous code alike.
Calibration hunks from model_a_files call rare-attested functions too (e.g.
build utilities, test helpers that appear in one file). Shape primitives based
on AST patterns (exception handling ratios, call scope fractions) also fire
on calibration hunks unless the corpus is carefully curated.
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.
- 5d ago First seen · 230 lines · 0 tokens per session scan A 97e3023e09d2
calibration-contract is an agent published in the GitHub repository get-tmonier/argot (48 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,493 tokens. 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-30.
Other agents, from other repositories
harness-doctor
Check a claudeconf-generated harness against its RECORDED constitution profile — advisory, evidence-driven, read-only. Use when the user asks to check, diagnose, or "doctor" their harness, verify pins/wiring/drift, see whether branch protection matches the enforcement checklist, or whether a profile upgrade is…
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.
lead
Workflow orchestrator. Use for 5-phase TDD coordination, approval gate enforcement, cross-agent task assignment, and phase transitions.
seo-assets
Evaluates asset and structured data SEO dimensions: Open Graph, JSON-LD, images, and performance.
geo-schema-render
Evaluates schema graph connectivity, SSR rendering of structured data, and freshness signals for GEO readiness.
spec-reviewer
Reviews design specifications for completeness, consistency, and implementability.