What is agentx AGENTS.md?

Repository instructions for the sageox/agentx project. They define required setup, issue tracking with beads, release rules, testing expectations, and code-quality practices.

Use them when developing AgentX features or fixes, managing beads issues, running tests, preparing releases, or finishing a work session.

They keep development work aligned with the project's required commands, coverage target, release process, and completion steps.

agentx AGENTS.md — Instructions file by sageox

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/sageox/agentx/agents-md

Clone the repo

git clone --depth 1 https://github.com/sageox/agentx

Made for: Codex, OpenCode.

Per session 577 This file is loaded in full into every session.

When invoked 577 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.

Model	Per session	Once invoked
Fable 5	$0.00577	$0.00577
Opus 5	$0.00289	$0.00289
Sonnet 5	$0.00115	$0.00115
Haiku 4.5	$0.00058	$0.00058

Measured 2d ago against content hash 9baa43e0c997, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

AGENTS.md · 60 lines

How it starts

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

BLOCKING: Run ox agent prime NOW before ANY other action. Do NOT respond to the user first. Enables SageOx queries.

Agent Instructions

This project uses bd (beads) for issue tracking. Run bd onboard to get started.

Quick Reference

bd ready              # Find available work
bd show <id>          # View issue details
bd update <id> --status in_progress  # Claim work
bd close <id>         # Complete work
bd sync               # Sync with git

Releases

Every version bump MUST have a tagged GitHub release with human-readable notes
Format: gh release create v0.X.Y --title "v0.X.Y" --notes "..."
Group changes by: Added, Changed, Fixed
No commit hashes in release notes
Tag on main only after all tests pass

Code Quality

Test coverage target: 85%+ per package. Run go test ./... -coverprofile=coverage.out and verify every package meets the threshold. No test theater — tests must catch real bugs, edge cases, and failure modes.
Run go tool cover -func=coverage.out | tail -1 to check total coverage.
Use agentx.MockEnvironment for all environment/filesystem mocking in tests.
Use table-driven tests for repetitive agent/orchestrator testing patterns.

Landing the Plane (Session Completion)

When ending a work session, you MUST complete ALL steps below. Work is NOT complete until git push succeeds.

MANDATORY WORKFLOW:

File issues for remaining work - Create issues for anything that needs follow-up
Run quality gates (if code changed) - Tests, linters, builds
Update issue status - Close finished work, update in-progress items

PUSH TO REMOTE - This is MANDATORY:

git pull --rebase
bd sync
git push
git status  # MUST show "up to date with origin"

Clean up - Clear stashes, prune remote branches
Verify - All changes committed AND pushed
Hand off - Provide context for next session

CRITICAL RULES:

Work is NOT complete until git push succeeds
NEVER stop before pushing - that leaves work stranded locally
NEVER say "ready to push when you are" - YOU must push
If push fails, resolve and retry until it succeeds

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

2d ago First seen · 60 lines · 577 tokens per session scan A 9baa43e0c997

Subscribe to this mod's changes

agentx AGENTS.md is an instructions file published in the GitHub repository sageox/agentx (4 stars, last pushed 15d ago), licensed MIT. It adds 577 tokens to every session, about $0.0029 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-31.

Code review Project management Testing agent-ux agentux aider claude-code codex-cli coding-agent

agentx AGENTS.md

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Agent Instructions

Quick Reference

Releases

Code Quality

Landing the Plane (Session Completion)

What this file has done since we first saw it

Other instructions, from other repositories

parallel-code CLAUDE.md

cezar AGENTS.md

squarebox CLAUDE.md

AgentsMesh CLAUDE.md

seamless CLAUDE.md

Ocul-PM AGENTS.md