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 commands/let-sunny/canicode/calibrategit clone --depth 1 https://github.com/let-sunny/canicodeWrote 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/let-sunny/canicode/calibrate)<a href="https://agentmods.dev/commands/let-sunny/canicode/calibrate"><img src="https://agentmods.dev/badge/commands/let-sunny/canicode/calibrate.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.00550 |
| Opus 5 | $0.00000 | $0.00275 |
| Sonnet 5 | $0.00000 | $0.00110 |
| Haiku 4.5 | $0.00000 | $0.00055 |
Grade A, and why
calibrate 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run the calibration pipeline for a single fixture, all active fixtures, or resume a failed run.
Input: $ARGUMENTS (fixture path, --all, or --resume <run-dir>)
Instructions
Run the calibration script:
npx tsx scripts/calibrate.ts $ARGUMENTS
The script (scripts/calibrate.ts) orchestrates:
- Analyze (CLI) —
calibrate-analyze - Design tree (CLI) — generate baseline + 6 stripped design-trees
- Convert (Agent, 7 parallel
claude -psessions) — baseline + 6 strip HTMLs - Measure (CLI) — visual-compare + code-metrics for all 7
- Gap Analyze (Agent,
claude -p) — if tier=full - Evaluate (CLI) —
calibrate-evaluate - Critic (Agent,
claude -p) — challenge proposals - Arbitrator (Agent,
claude -p) — final decisions, applies to rule-config.ts - Evidence (CLI) — enrich + prune calibration evidence
- Report (CLI) — aggregate gap report
index.jsontracks 14 internal sub-steps (e.g., screenshot capture, strip generation, post-processing split out separately). The 10 stages above are the logical grouping.
Modes
- Single fixture:
npx tsx scripts/calibrate.ts <fixture-path> - All active fixtures:
npx tsx scripts/calibrate.ts --all— discovers active fixtures, runs sequentially, checks convergence, runs regression check, generates aggregate report - Resume:
npx tsx scripts/calibrate.ts --resume <run-dir>
After the script completes
Report the summary:
- Which steps completed, skipped, or failed
- Similarity score (from the measure step summary)
- Proposals and decisions (from evaluate/arbitrator summaries)
- For
--allmode: fixtures ran/passed/failed/converged - Path to the run directory (or aggregate report for
--all)
Rules
- The script handles all orchestration — do NOT manually run individual steps.
- If the script fails, check
$RUN_DIR/index.jsonfor the failed step and error message. - To re-run from a failed step, use
--resume. Do NOT delete the run directory. - Fixtures run sequentially in
--allmode — each may modifyrule-config.ts.
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 · 48 lines · 0 tokens per session scan A 8fe46cc35a7c
calibrate is a command published in the GitHub repository let-sunny/canicode (10 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 550 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-31.
Other commands, from other repositories
release
Command "release" from GLips/Figma-Context-MCP, covering release and steps.
open
SoDam-Design-Kit open 대시보드 — 검증 이력·판정서·스크린샷을 브라우저로 열람 + 재검증.
setup
SoDam-Design-Kit 설정 마법사 — config.json 생성 + shadcn 컴포넌트 스캔으로 component-map 초기 시드.
detail-page
상세페이지 파이프라인 — 상품 데이터(CSV/JSON) → 카피 생성 → 페이지 코드 → 동일 검증 게이트 (Phase 3).
pipeline
디자인→코드 파이프라인 — Figma 읽기 → component-map 매핑 → shadcn/ui 코드 생성 → 검증 게이트.
marketing-asset
마케팅 소재 파이프라인 — 제목/부제(+명함은 추가 정보) → Satori+Sharp로 OG·포스터·배너·명함 이미지 생성 (Phase 3).