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/dowdiness/incr/agents-mdgit clone --depth 1 https://github.com/dowdiness/incrWrote 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/dowdiness/incr/agents-md)<a href="https://agentmods.dev/instructions/dowdiness/incr/agents-md"><img src="https://agentmods.dev/badge/instructions/dowdiness/incr/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.01214 | $0.01214 |
| Opus 5 | $0.00607 | $0.00607 |
| Sonnet 5 | $0.00243 | $0.00243 |
| Haiku 4.5 | $0.00121 | $0.00121 |
Grade A, and why
incr 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 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Canonical entry point for contributors and coding agents in dowdiness/incr. Read before making changes.
Project Overview
incr is a Salsa-inspired incremental recomputation library in MoonBit. A MoonBit workspace: the library lives under incr/, checked docs under docs/, examples under examples/. See docs/architecture.md for the package map.
Target facades: Input, Derived, ReachableDerived, DerivedMap, InputField, EagerDerived, Effect, Relation, MapRelation, Accumulator, Scope, plus RuntimeContext / Freshness / InputFieldOwner. Legacy names (Signal/Memo/TrackedCell/Reactive/FunctionalRelation/Database) are gone — see CHANGELOG for mapping.
Project Structure
moon.work ← Workspace root
incr/ ← Library module
incr.mbt, traits.mbt ← Root facade (re-exports + `create_*` helpers)
types/ ← Pure value types (CellId, Revision, ReadError, …)
cells/ ← Engine: handles, Runtime coordinator
cells/internal/ ← shared, pull, push, datalog, kernel (compiler-enforced)
tests/ ← Integration tests against the public API
docs/ ← Checked docs workspace member + docs/README.md index
examples/ ← Standalone workspace modules
scripts/ ← check-engine-isolation.sh, check-workspace-boundaries.sh, bump-version.sh
Tests inside incr/cells/ live beside source: *_test.mbt (black-box) and *_wbtest.mbt (white-box, same package). Generated pkg.generated.mbti files are regenerated by moon info — never edited by hand.
Build & Test
moon check # Type-check; run after every edit
moon build # Compile
moon test # Full suite (~1205 test blocks)
moon bench --release
moon fmt # 2-space indent; `moon fmt` enforces all formatting
moon info # Regenerate all pkg.generated.mbti files
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 · 89 lines · 1,214 tokens per session scan A 2ddddd5e07e7
incr AGENTS.md is an instructions file published in the GitHub repository dowdiness/incr (5 stars, last pushed 4d ago), licensed Apache-2.0. It adds 1,214 tokens to every session, about $0.0061 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 instructions, from other repositories
yunomi CLAUDE.md
Instructions for kazuph/yunomi, covering yunomi プロジェクト固有ルール, 開発・テスト時のサーバー起動, この環境のyunomi更新, 構文エラーの回避 and 主要ファイル.
moonbit-agent-skills AGENTS.md
Instructions for hyfdev/moonbit-agent-skills, covering working in this repository (agent instructions), rules, local check sequence (mirror of ci) and layout.
moonbit-ic-cdk AGENTS.md
Instructions for eliezhao/moonbit-ic-cdk, covering project agents.md guide, project structure, coding convention and tooling.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.