pitway: Instructions file for Codex

AGENTS.md

pitway AGENTS.md is an instructions file for Codex, OpenCode from thixpin/pitway. It costs 1,900 tokens per session, scanned A, original, MIT.

A repository instruction file for PitWay, a tool that controls the project’s engineering workflow through milestones, contracts, and bounded tasks.

In plain words
What is it for?
It guides agents through task status checks, milestone-based development, protocol roles, and the rule that workflow files must not be edited directly.
Why use it?
It requires agents to resume the workflow and confirm the task context before writing code, helping keep changes within an approved scope.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions subagents; mentions Claude Code; mentions Codex.

This is thixpin/pitway's own configuration. It tells Codex and OpenCode how to work on pitway itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything pitway configures →

Reuse

Borrowing it

Nothing to install: this file belongs to thixpin/pitway. 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/thixpin/pitway/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/thixpin/pitway

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.

agentmods badge for pitway AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/thixpin/pitway/agents-md/github.svg)](https://agentmods.dev/instructions/thixpin/pitway/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/thixpin/pitway/agents-md"><img src="https://agentmods.dev/badge/instructions/thixpin/pitway/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.

agentmods 80×15 button for pitway AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/thixpin/pitway/agents-md"><img src="https://agentmods.dev/badge/instructions/thixpin/pitway/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,900 This file is loaded in full into every session.
When invoked 1,900 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.01900 $0.01900
Opus 5.5 $0.00760 $0.00760
Sonnet 5.5 $0.00380 $0.00380
Haiku 4.5 $0.00190 $0.00190

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

Security

Grade A, and why

pitway 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 · 73 lines

How it starts

The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agent Instructions

  • This project uses PitWay to control the engineering workflow.
  • Run pitway resume before starting or resuming any work.
  • Never edit .pitway/ directly.
  • Work only within a confirmed task boundary.
  • Obtain a task's bounded context via pitway task-status <id> --context.
  • The driver protocol is split into roles: protocol-driver.md (Main Agent: developer conversation and every approval gate), protocol-orchestrator.md (Orchestrator: task execution), and protocol-worker.md (Worker: one bounded task) in the installed driver directory.

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Project Status

PitWay is developed using its own workflow (dogfooding): every change lands through a confirmed milestone/contract/task, following the pipeline below. The authoritative sources are the workflow state in .pitway/ (milestones, contracts, backlog) — the original design record is archived at docs/archive/IMPLEMENTATION_PLAN-v1.0.md (frozen; never updated).

  • Never write implementation code outside a confirmed milestone task. A milestone's contract must be presented to the developer and explicitly approved in conversation before its baseline commit or any task work.
  • Check .pitway/state.yaml and the active milestone's contract.md / tasks.yaml to find current state and next work before doing anything.

What PitWay Is

An npm-distributed CLI (npx pitway init; unscoped package name pitway) that controls the engineering process around AI coding agents — it is not itself an agent. Core philosophy: "Claude drives the interaction; PitWay controls the workflow state and engineering boundaries."

Pipeline: Requirement → Milestone → Contract → human confirmation → verification plan → right-sized task graph → task-level TDD (RED→GREEN→REFACTOR) → verification → atomic commit → milestone contract verification → completion.

Read the full file on GitHub · 73 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.

  1. 2mo ago First seen · 73 lines · 1,900 tokens per session scan A 96a7c949fd0f

Subscribe to this mod's changes

pitway AGENTS.md is an instructions file published in the GitHub repository thixpin/pitway (20 stars, last pushed 17d ago), licensed MIT. It adds 1,900 tokens to every session, about $0.0076 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.

Related

pitway AGENTS.md compared with instructions from other repositories

pitway AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
pitway AGENTS.mdthixpin/pitwayInstructions file2017d agoMITA1,900Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143ktodayMITA7,461Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA5,516GitHub Copilot
langchain AGENTS.mdlangchain-ai/langchainInstructions file149ktodayMITA4,680Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file275k3d agoMITA4,313Codex, OpenCode