agentmods.dev

pixir CLAUDE.md

A project guide for the Pixir harness, an agent runtime with sessions, providers, tools, and terminal or standard-input/output interfaces.

In plain words
What is it for?
Use it when working on Pixir, especially to inspect its architecture, run checks and tests, format code, compile it, or build the executable.
Why use it?
It points agents to the current source of truth, project vocabulary, architecture notes, and validation commands.

Instructions file

23 4d ago A scan 246 tokens original MIT
View the source file Ranvier-Technologies/pixir
Install

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.

agentmods
npx agentmods add instructions/ranvier-technologies/pixir/claude-md
Clone the repo
git clone --depth 1 https://github.com/Ranvier-Technologies/pixir
Per session 246 This file is loaded in full into every session.
When invoked 246 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00246 $0.00246
Opus 5 $0.00123 $0.00123
Sonnet 5 $0.00049 $0.00049
Haiku 4.5 $0.00025 $0.00025

Measured yesterday against content hash e27989abbc37, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

pixir CLAUDE.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 yesterday.

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.

CLAUDE.md · 36 lines

What it actually says

Pixir Harness - legacy agent guide

AGENTS.md is the canonical instruction file for coding agents in this repo. Start there, then read CONTEXT.md for vocabulary and the relevant ADR in docs/adr/.

This file remains only as a compatibility pointer for harnesses that still look for CLAUDE.md.

Current map

  • Runtime spine: Session -> Turn -> Provider -> Tools.
  • Source of truth: append-only local Log under .pixir/sessions/.
  • Presenters: terminal CLI and ACP over stdio.
  • Provider path: OpenAI Responses, store: false, provider usage as durable evidence, WebSocket-preferred transport with HTTP/SSE fallback.
  • Growth surfaces: Skills, Subagents, Workflows, Session Resources/Image Attachments, Provider-hosted Web Search, and future Skill Context Hydration.

Commands

mix deps.get
mix check
mix test
mix format --check-formatted
mix compile --warnings-as-errors
mix escript.build
./pixir doctor --json

Run Python helpers, if any, with:

uv run python file_name.py
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.

  1. yesterday First seen · 36 lines · 246 tokens per session scan A e27989abbc37

Subscribe to this mod's changes

pixir CLAUDE.md is an instructions file published in the GitHub repository Ranvier-Technologies/pixir (23 stars, last pushed 4d ago), licensed MIT. It adds 246 tokens to every session, about $0.0012 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.

LanguagesPlanningTestingacpagent-harnesscoding-agentsdeveloper-toolselixirotp
Related

Other instructions, from other repositories

raxol CLAUDE.md

Instructions for DROOdotFOO/raxol, covering claude.md, essential commands, initial setup, building & compilation and testing.

DROOdotFOO/raxol · 17,878 tokens

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.

ychamel/RepoResident · 50 tokens

agent-harness-skills AGENTS.md

Instructions for yfge/agent-harness-skills, covering agent harness skills - repository instructions, purpose, rules, validation and commit discipline.

yfge/agent-harness-skills · 450 tokens

agent-harness-skills GEMINI.md

Instructions for yfge/agent-harness-skills: This extension provides reusable skills for repository harness design.

yfge/agent-harness-skills · 111 tokens

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").

abhishekgahlot2/pi-dsh · 1,355 tokens

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.

abhishekgahlot2/pi-dsh · 88 tokens