What is pyball AGENTS.md?

Project instructions for boscoh/pyball that define how to track work with bd, a command-line issue tracker. They cover creating, prioritising, updating, linking, and closing issues.

Use them when checking available work, filing bugs or features, setting priorities, recording dependencies, claiming tasks, or closing completed work.

They keep the project’s tasks, bugs, dependencies, and priorities in one consistent system. This avoids scattered TODO lists and makes blocked or ready work easier to identify.

How boscoh/pyball configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to boscoh/pyball. 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/boscoh/pyball/master/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/boscoh/pyball

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/boscoh/pyball/agents-md/github.svg)](https://agentmods.dev/instructions/boscoh/pyball/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/boscoh/pyball/agents-md"><img src="https://agentmods.dev/badge/instructions/boscoh/pyball/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/boscoh/pyball/agents-md"><img src="https://agentmods.dev/badge/instructions/boscoh/pyball/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,031 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.01031	$0.01031
Opus 5.5	$0.00412	$0.00412
Sonnet 5.5	$0.00206	$0.00206
Haiku 4.5	$0.00103	$0.00103

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

Security

Grade A, and why

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

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

enoch AGENTS.md — 89% identical, 258 lines differ

AGENTS.md · 135 lines

How it starts

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

Issue Tracking with bd (beads)

IMPORTANT: This project uses bd (beads) for ALL issue tracking. Do NOT use markdown TODOs, task lists, or other tracking methods.

Why bd?

Dependency-aware: Track blockers and relationships between issues
Git-friendly: Auto-syncs to JSONL for version control
Agent-optimized: JSON output, ready work detection, discovered-from links
Prevents duplicate tracking systems and confusion

Quick Start

Check for ready work:

bd ready --json

Create new issues:

bd create "Issue title" -t bug|feature|task -p 0-4 --json
bd create "Issue title" -p 1 --deps discovered-from:bd-123 --json

Claim and update:

bd update bd-42 --status in_progress --json
bd update bd-42 --priority 1 --json

Complete work:

bd close bd-42 --reason "Completed" --json

Issue Types

bug - Something broken
feature - New functionality
task - Work item (tests, docs, refactoring)
epic - Large feature with subtasks
chore - Maintenance (dependencies, tooling)

Priorities

0 - Critical (security, data loss, broken builds)
1 - High (major features, important bugs)
2 - Medium (default, nice-to-have)
3 - Low (polish, optimization)
4 - Backlog (future ideas)

Workflow for AI Agents

Check ready work: bd ready shows unblocked issues
Claim your task: bd update <id> --status in_progress
Work on it: Implement, test, document
Discover new work? Create linked issue:
- bd create "Found bug" -p 1 --deps discovered-from:<parent-id>
Complete: bd close <id> --reason "Done"
Commit together: Always commit the .beads/issues.jsonl file together with the code changes so issue state stays in sync with code state

Auto-Sync

bd automatically syncs with git:

Exports to .beads/issues.jsonl after changes (5s debounce)
Imports from JSONL when newer (e.g., after git pull)
No manual export/import needed!

Read the full file on GitHub · 135 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 · 135 lines · 1,031 tokens per session scan A f981da62eb77

Subscribe to this mod's changes

pyball AGENTS.md is an instructions file published in the GitHub repository boscoh/pyball (10 stars, last pushed 11mo ago), licensed MIT. It adds 1,031 tokens to every session, about $0.0041 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-31.

Project management

pyball AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
pyball AGENTS.mdboscoh/pyball	Instructions file	10	11mo ago	MIT	A	1,031	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

pyball: Instructions file for Codex