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/footprintjs/footprint/agents-mdgit clone --depth 1 https://github.com/footprintjs/footPrintWrote 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/footprintjs/footprint/agents-md)<a href="https://agentmods.dev/instructions/footprintjs/footprint/agents-md"><img src="https://agentmods.dev/badge/instructions/footprintjs/footprint/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.09077 | $0.09077 |
| Opus 5 | $0.04539 | $0.04539 |
| Sonnet 5 | $0.01815 | $0.01815 |
| Haiku 4.5 | $0.00908 | $0.00908 |
Grade A, and why
footPrint 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 — 643 lines — stays where its author put it; the contents beside it link to each section on GitHub.
footprint.js — AI Coding Instructions
This is the footprint.js library — the flowchart pattern for backend code. Self-explainable systems that AI can reason about.
Core Principle
Collect during traversal, never post-process. All data collection (narrative, metrics, manifest, identity) happens as side effects of the single DFS traversal pass. Never walk the tree again after execution.
Architecture — Library of Libraries
src/lib/
├── capture/ → Value-capture/retention primitives (RetentionPolicy 'full'|'summary'|'off', read/write summary markers) — shared by the readTracking (#14) + writeTracking (#13c-A) dials; RFC-001 builds on it
├── memory/ → Transactional state (SharedMemory, StageContext, TransactionBuffer, EventLog)
├── schema/ → Validation abstraction (Zod optional, duck-typed detection)
├── builder/ → Fluent DSL (FlowChartBuilder, flowChart(), DeciderList, SelectorFnList)
├── scope/ → Per-stage facades + recorders + providers
├── reactive/ → TypedScope<T> deep Proxy (typed property access, $-methods, cycle-safe)
├── decide/ → decide()/select() decision evidence capture (filter + function)
├── recorder/ → CompositeRecorder, KeyedStore<T>, SequenceStore<T>, BoundaryStateStore<TState>, composition primitives
├── pause/ → Pause/Resume (PauseSignal, FlowchartCheckpoint, PausableHandler)
├── engine/ → DFS traversal + narrative + 13 handlers
├── runner/ → High-level executor (FlowChartExecutor)
└── contract/ → I/O schema + OpenAPI generation
Dependency DAG: capture (standalone leaf) <- memory <- scope <- reactive <- engine <- runner, schema <- engine, builder (standalone) -> engine, contract <- schema, decide -> scope
Three entry points:
import { ... } from 'footprintjs'— public APIimport { ... } from 'footprintjs/trace'— execution tracing: runtimeStageId, commitLog queries, storage primitives (KeyedStore, SequenceStore, BoundaryStateStore)import { ... } from 'footprintjs/advanced'— engine internals (also re-exports trace)
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 · 643 lines · 9,077 tokens per session scan A a13a30d3c743
footPrint AGENTS.md is an instructions file published in the GitHub repository footprintjs/footPrint (20 stars, last pushed 3d ago), licensed MIT. It adds 9,077 tokens to every session, about $0.0454 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
ai-workflow AGENTS.md
Instructions for cunhaax/ai-workflow, covering ai workflow template, rules — non-negotiable, project overview, commands and architecture.
trackly-cli CLAUDE.md
Claude Code instructions for trackly-app/trackly-cli, covering trackly-cli, tech stack, backend production source of truth, directory structure and key commands.
vibetags com-example-config-AsyncTestConfig.instructions.md
Instructions for PIsberg/vibetags, covering copilot instructions for asynctestconfig and immutable type.
pupila CLAUDE.md
Instructions for FranRom/pupila, covering claude.md, where things live, stack, run locally and repo layout.
claude-bridge AGENTS.md
Instructions for kadaba/claude-bridge, covering agents.md — using claude-bridge from any ai coding cli, two independent channels, 1. coordination (the conversation), 2. file transfer (the bytes) — same for every tool and workflows.
McpServer AGENTS.md
AGENTS.md instructions for sharpninja/McpServer, covering agent instructions, session start, rules, byrd test gate and where things live.