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 instructions/edonadei/caliper/agents-mdgit clone --depth 1 https://github.com/edonadei/caliperWrote 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/instructions/edonadei/caliper/agents-md)<a href="https://agentmods.dev/instructions/edonadei/caliper/agents-md"><img src="https://agentmods.dev/badge/instructions/edonadei/caliper/agents-md.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.00538 | $0.00538 |
| Opus 5 | $0.00269 | $0.00269 |
| Sonnet 5 | $0.00108 | $0.00108 |
| Haiku 4.5 | $0.00054 | $0.00054 |
Grade A, and why
caliper AGENTS.md 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 4d 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Caliper — agent instructions
Contributor setup, formatting, and linting details live in
.github/CONTRIBUTING.md— GitHub's conventional location, not the repo root. Read it there.
Updating docs after API changes
When any of the following change, update all three locations before marking the task done:
- A
caliper runCLI flag is added, removed, or renamed - The
.eval.yamlspec format changes (new fields, removed fields, renamed keys) - The judge behavior changes (how
expect:orassert:are evaluated) - The results JSON schema changes (
RunMeta,AttemptRecord, etc.)
Locations to update:
README.md— CLI reference table and any relevant prose sectionsskills/evaluate-skill/REFERENCE.md— the source skill referenceskills/grill-skill/REFERENCE.md— the grill-skill reference
Formatting
ruff is the single formatting and linting authority for this repo, pinned to
ruff==0.15.20. Run ruff format . and ruff check . before finishing. Never
hand-reformat lines outside the scope of your change — the formatter is the
only style authority, and manual reflow inflates diffs. CI enforces
ruff format --check . and ruff check . on every PR. See
.github/CONTRIBUTING.md for details.
Decision docs
This repo keeps its domain model and design decisions in version control:
docs/CONTEXT.md— the glossary / ubiquitous language. A glossary only: no implementation details, no specs, no scratch notes. This is where the grill-with-docs and domain-modeling skills read and write terms. In this repo it lives atdocs/CONTEXT.md, not the repo root — look there.docs/adr/— Architecture Decision Records (0001-*.md, …), one short entry per hard-to-reverse, non-obvious, real-trade-off decision.
Both are committed and ship with the repo. Reference them freely from code
comments, docstrings, and docs — e.g. see docs/CONTEXT.md → Regression or
docs/adr/0001-attempt-outcome-taxonomy.md. Because the files clone with the
repo, these links resolve for everyone. Prefer a short comment that links the
record over re-explaining the decision inline.
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.
- 4d ago First seen · 47 lines · 538 tokens per session scan A 46578c825b4c
caliper AGENTS.md is an instructions file published in the GitHub repository edonadei/caliper (50 stars, last pushed 4d ago), licensed MIT. It adds 538 tokens to every session, about $0.0027 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-30.
Other instructions, from other repositories
agent-skill-evals AGENTS.md
AGENTS.md instructions for akshay5995/agent-skill-evals, covering agent skill evals agent guide, why this repo exists, repo map, before changing code and product rules.
skills-evals typescript.instructions.md
TypeScript conventions for this repo.
skills-evals copilot-instructions.md
Instructions for ahnafyy/skills-evals: Prefer small, focused pull requests. Run the full test suite before committing.
ai-toolkit AGENTS.md
Instructions for pipefy/ai-toolkit, covering repository guidelines, documentation map, project structure, import namespace migration: pipefysdk → pipefy and src/pipefysdk/init.py (transitional shim).
superpowers-reasonix AGENTS.md
Instructions for christopherarter/superpowers-reasonix, covering project guidance, skills — stop. load a skill before you act, red flags — these thoughts mean stop. you are rationalizing and priority.
ai-mind AGENTS.md
Instructions for HWYD/ai-mind, covering agents, version spec workspace continuity (mandatory), 项目定位, 事实来源优先级 and 开始大改前先读什么.