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/travmiller/paper-console/agents-mdgit clone --depth 1 https://github.com/travmiller/paper-consoleWrote 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/travmiller/paper-console/agents-md)<a href="https://agentmods.dev/instructions/travmiller/paper-console/agents-md"><img src="https://agentmods.dev/badge/instructions/travmiller/paper-console/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.01055 | $0.01055 |
| Opus 5 | $0.00528 | $0.00528 |
| Sonnet 5 | $0.00211 | $0.00211 |
| Haiku 4.5 | $0.00105 | $0.00105 |
Grade A, and why
paper-console 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions
Use a Unix-like shell for local development commands. On Windows, use WSL.
Project Context
Use readme.md as canonical project context for setup, architecture, and expected behavior.
Rules:
- Check
readme.mdbefore making architecture, workflow, or UX assumptions. - If instructions conflict, prefer: explicit user chat instructions, then
AGENTS.md, thenreadme.md. - Do not copy large sections of
readme.mdinto responses unless explicitly requested; summarize relevant parts.
Production Release Workflow
For production OTA artifacts (non-git device updates), use scripts/release_build.py and follow scripts/RELEASE.md.
Console Raster Preview for Print Debugging
When validating printer output (layout, clipping, alignment, density, or black/white dot rendering), run this feedback loop:
./.venv/bin/python testing/render_all_prints.py --module-type astronomy --output testing/artifacts/debug/feedback_full_print.png
./.venv/bin/python testing/console_raster_preview.py --image testing/artifacts/debug/feedback_full_print.png --dots-width 384 --cols 96
./.venv/bin/python testing/render_all_prints.py --channel 3 --output testing/artifacts/debug/feedback_full_print.png
./.venv/bin/python testing/console_raster_preview.py --image testing/artifacts/debug/feedback_full_print.png --dots-width 384 --cols 96
This workflow:
- Renders the full receipt bitmap through the real print pipeline (
testing/render_all_prints.py) - Saves PNG output under
testing/artifacts/debug/ - Prints a console dot-map preview from that exact full receipt image
Use this fallback command only for synthetic calibration patterns:
./.venv/bin/python testing/console_raster_preview.py --pattern targets --dots-width 384 --cols 96
Rules:
- Prefer
./.venv/bin/pythonin this repo (do not assumepythonis onPATH). - Prefer full-print feedback loop previews over synthetic patterns when evaluating actual print changes.
- Use
--dots-width 384by default for the 58mm printer path unless a different width is explicitly provided. - Use built-in patterns (
grid,checker,bars,targets) for deterministic diagnostics. - Use
--image <path>to inspect an actual bitmap that would be printed. - Share/paste generated dot-map output in agent responses when requesting print QA feedback.
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 · 105 lines · 1,055 tokens per session scan A 2e44667f12ba
paper-console AGENTS.md is an instructions file published in the GitHub repository travmiller/paper-console (328 stars, last pushed 8d ago), licensed MIT. It adds 1,055 tokens to every session, about $0.0053 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
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.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.