What is paper-console AGENTS.md?

A set of project instructions for developing and releasing a software console, including print-output checks. It explains which project files and scripts define the expected workflow.

Use it when working on the paper-console project, especially to read its project context, create production over-the-air update files, or preview printer output as a raster image and dot grid.

It reduces guesswork about architecture, user-interface decisions, production releases, and whether printed output is clipped, misaligned, or rendered incorrectly.

How travmiller/paper-console configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to travmiller/paper-console. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/travmiller/paper-console/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/travmiller/paper-console

Made for: Codex, OpenCode.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/travmiller/paper-console/agents-md/github.svg)](https://agentmods.dev/instructions/travmiller/paper-console/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/travmiller/paper-console/agents-md"><img src="https://agentmods.dev/badge/instructions/travmiller/paper-console/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<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="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,055 This file is loaded in full into every session.

When invoked 1,055 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.1	$0.01055	$0.01055
Opus 5.5	$0.00422	$0.00422
Sonnet 5.5	$0.00211	$0.00211
Haiku 4.5	$0.00105	$0.00105

Measured 2mo ago against content hash 2e44667f12ba, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

AGENTS.md · 105 lines

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.md before making architecture, workflow, or UX assumptions.
If instructions conflict, prefer: explicit user chat instructions, then AGENTS.md, then readme.md.
Do not copy large sections of readme.md into 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/python in this repo (do not assume python is on PATH).
Prefer full-print feedback loop previews over synthetic patterns when evaluating actual print changes.
Use --dots-width 384 by 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.

Read the full file on GitHub · 105 lines

Changes

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.

2mo ago First seen · 105 lines · 1,055 tokens per session scan A 2e44667f12ba

Subscribe to this mod's changes

paper-console AGENTS.md is an instructions file published in the GitHub repository travmiller/paper-console (343 stars, last pushed 1mo ago), licensed MIT. It adds 1,055 tokens to every session, about $0.0042 per session on Opus 5.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.

paper-console AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
paper-console AGENTS.mdtravmiller/paper-console	Instructions file	343	1mo ago	MIT	A	1,055	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

paper-console: Instructions file for Codex