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/copilot-instructionsgit 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/copilot-instructions)<a href="https://agentmods.dev/instructions/footprintjs/footprint/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/footprintjs/footprint/copilot-instructions.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.01018 | $0.01018 |
| Opus 5 | $0.00509 | $0.00509 |
| Sonnet 5 | $0.00204 | $0.00204 |
| Haiku 4.5 | $0.00102 | $0.00102 |
Grade A, and why
footPrint copilot-instructions.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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
footprint.js — Copilot 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 happens as side effects of the single DFS traversal. Never walk the tree after execution.
Architecture
src/lib/
├── memory/ → Transactional state (SharedMemory, StageContext, TransactionBuffer)
├── schema/ → Validation (Zod optional, duck-typed)
├── builder/ → Fluent DSL (FlowChartBuilder, flowChart())
├── scope/ → Per-stage facades + recorders + providers
├── reactive/ → TypedScope<T> deep Proxy (typed property access, $-methods)
├── decide/ → decide()/select() decision evidence capture
├── engine/ → DFS traversal + narrative + handlers
├── runner/ → FlowChartExecutor
└── contract/ → I/O schema + OpenAPI
Entry points: footprintjs (public) and footprintjs/advanced (internals).
Key API — TypedScope (Recommended)
import { flowChart, FlowChartExecutor, decide } from 'footprintjs';
interface State {
creditScore: number;
riskTier: string;
decision?: string;
}
const chart = flowChart<State>('Intake', async (scope) => {
scope.creditScore = 750; // typed write (no setValue needed)
scope.riskTier = 'low'; // typed write
}, 'intake')
.addDeciderFunction('Route', (scope) => {
return decide(scope, [
{ when: { riskTier: { eq: 'low' } }, then: 'approved', label: 'Low risk' },
], 'rejected');
}, 'route', 'Route based on risk')
.addFunctionBranch('approved', 'Approve', async (scope) => {
scope.decision = 'Approved';
})
.addFunctionBranch('rejected', 'Reject', async (scope) => {
scope.decision = 'Rejected';
})
.setDefault('rejected')
.end()
.build();
const executor = new FlowChartExecutor(chart);
await executor.run();
executor.getNarrative(); // causal trace with decision evidence
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 · 119 lines · 1,018 tokens per session scan A 9c1dff300417
footPrint copilot-instructions.md is an instructions file published in the GitHub repository footprintjs/footPrint (20 stars, last pushed 3d ago), licensed MIT. It adds 1,018 tokens to every session, about $0.0051 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.