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/ranvier-technologies/pixir/agents-mdgit clone --depth 1 https://github.com/Ranvier-Technologies/pixirWhat 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.02790 | $0.02790 |
| Opus 5 | $0.01395 | $0.01395 |
| Sonnet 5 | $0.00558 | $0.00558 |
| Haiku 4.5 | $0.00279 | $0.00279 |
Grade A, and why
pixir 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 2d 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 — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md - Pixir Harness
Pixir is an OTP-native, local-first coding-agent harness. The runtime spine is:
Session -> Turn -> Provider -> Tools
The append-only Log is truth, the terminal CLI is the default presenter, and ACP over stdio is the main client transport.
Progressive Discovery
Do not read the whole repo up front. Load context in this order and stop once the task is grounded enough:
- Start here: this file gives the architecture map, invariants, commands, and beta stance.
- Human quickstart:
README.mdanddocs/open-beta-quickstart.mdexplain the source-install developer-preview path. - Vocabulary:
CONTEXT.mddefines Harness, Session, Agent, Skill, Workflow, Subagent, Event, Log, History, Workspace, Tool, Host Boundary Crossing, Provider, Credential, and PATCHMD. Use those meanings exactly. - Architecture decisions: read only the ADRs relevant to your change:
0001Session is the process; Agent is role/configuration.0002ChatGPT subscription OAuth + OpenAI Responses API.0003stateless Turns; local Log is source of truth.0004unified Event envelope and canonical vs ephemeral events.0005agent ergonomics: dry-run, help, structured errors, I/O discipline.0006permission model.0007encrypted reasoning item persistence/replay.0008UI-agnostic Conversation driver.0009ACP transport over stdio.0010Agent Skills with progressive disclosure.0011BEAM-native Subagents.0012structural Workflows over Subagents.0013Skill-backed Workflow Templates.0014Workflow Checkpoint Bundles and honest partial outcomes.0015PATCHMD customization maintenance.0016open beta scope as source-install developer preview.0017minimal Harness core and Presenter boundary.0018durable History compaction and replay repair.0019Provider usage, prompt-cache observability, and WebSocket continuation.0020versioned Prompt Contract, cache-key family, and compaction triggers.0021Session Resources and Image Attachments.0022Provider-hosted Web Search evidence, not local Tool execution.0023Skill Context Hydration as explicit, canonical, late-bound context.0024Session Fork and Branch Summaries.0025Hex package scope.0026Runtime terminal-state and replay contract.0027external command execution as a bounded host boundary.0028Workspace Strategies and future virtual overlays.0029Virtual Overlay changes exportvirtual_diffartifacts.0030explicit apply and merge-back semantics forvirtual_diff.0031Git worktrees as lease-owned strategy for intended repo changes.0032minimal Workflow Events for durable run decisions.0033typed checkpoint outputs as harness-owned projections.0034Delegate service runtime residency before async start.0035Write-capable Sessions require an external evidence mirror.0036Idle-timeout recovery does not auto-resume ambiguous work.0037Anthropic provider registry routing, pa1 prompt contract, explicit cache control, and seam-parity transport.0038Pixir Monitor is an experimental sibling source-checkout SPA using authoritative snapshots and bounded SSE invalidation hints.0039Provider-output truncation is neutral, durable success evidence.0040Native OpenAI compaction is a replay window onhistory_compaction. Overlay amendment (2026-08-16): default-on after OpenAI Responses resolve; recovery stays local. Implementation plan for #522-B/C/D:docs/design/0004-native-openai-compaction-implementation.md.
- Nearest local instructions: read the closest subtree
AGENTS.mdbefore editing code, docs, tests, benchmarks, or ADRs.
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.
- 2d ago First seen · 234 lines · 2,790 tokens per session scan A c8df2a8844bf
pixir AGENTS.md is an instructions file published in the GitHub repository Ranvier-Technologies/pixir (23 stars, last pushed 5d ago), licensed MIT. It adds 2,790 tokens to every session, about $0.0140 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
raxol CLAUDE.md
Instructions for DROOdotFOO/raxol, covering claude.md, essential commands, initial setup, building & compilation and testing.
RepoResident AGENTS.md
Instructions for ychamel/RepoResident: Agent entry point: read CLAUDE.md in full — it is the operating manual — then follow its Session protocol. Everything else (state, workflows, project knowledge) is routed from there via the .agent/ directory.
agent-harness-skills AGENTS.md
Instructions for yfge/agent-harness-skills, covering agent harness skills - repository instructions, purpose, rules, validation and commit discipline.
agent-harness-skills GEMINI.md
Instructions for yfge/agent-harness-skills: This extension provides reusable skills for repository harness design.
pi-dsh AGENTS.md
AGENTS.md instructions for abhishekgahlot2/pi-dsh, covering pi-dsh, the contract (read before changing anything), layout, commands and vendoring policy ("maintain both forks").
pi-dsh CLAUDE.md
Claude Code instructions for abhishekgahlot2/pi-dsh: All project instructions live in AGENTS.md — read it first and follow it exactly.