runx AGENTS.md

Instructions for using scafld, a command-line tool that manages software work through planned, checked, reviewed, and completed stages. It keeps a written contract and evidence of the work as it progresses.

In plain words
What is it for?
Use it to initialize a project, plan and harden tasks, validate changes, build them, request a review, track status, create reports, and prepare handoffs.
Why use it?
It gives coding work a defined lifecycle and requires review before a task can be marked complete. This helps prevent unfinished or insufficiently checked work from being closed.

Instructions file for CodexOpenCode

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/runxhq/runx/agents-md
Clone the repo
git clone --depth 1 https://github.com/runxhq/runx

Made for: Codex, OpenCode.

Per session 3,209 This file is loaded in full into every session.
When invoked 3,209 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.03209 $0.03209
Opus 5 $0.01605 $0.01605
Sonnet 5 $0.00642 $0.00642
Haiku 4.5 $0.00321 $0.00321

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

Security

Grade A, and why

runx 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 3d 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 · 359 lines

How it starts

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

scafld Agent Contract

Contract

  • spec is the living contract.
  • session is the durable evidence ledger.
  • handoff is transport, not source of truth.
  • review is the adversarial completion gate.

You execute autonomously inside the contract. You do not close the task unchallenged.

Commands

scafld init
scafld plan <task-id> --title "Title" --size small --risk low
scafld harden <task-id>
scafld harden <task-id> --mark-passed
scafld validate <task-id>
scafld approve <task-id>
scafld build <task-id>
scafld review <task-id>
scafld complete <task-id>
scafld status <task-id>
scafld list
scafld report
scafld handoff <task-id>
scafld update

For real review: scafld review <task-id> --provider {codex|claude|command}. --provider local is smoke-test only and cannot satisfy complete. Only an operator may use scafld review <task-id> --human-reviewed --reason ....

Source Checkout

Inside the scafld repo, use ./bin/scafld or go run ./cmd/scafld. Do not use a copied compiled binary; stale binaries can report old lifecycle state.

Lifecycle

plan -> harden -> approve -> build -> review -> complete

Hardening attacks the draft. Review attacks the result. Build opens one phase at a time. After implementing the opened phase, run scafld build <task-id> again to record evidence and advance.

Do Not

  • Edit outside declared scope, objectives, or invariants.
  • Reconstruct lifecycle state by scraping Markdown. Use status --json.
  • Mutate .scafld/core/ by hand. Use scafld update.
  • Run --provider local for real review.
  • Cite files, commands, or review findings you have not verified.

Prompts

.scafld/prompts/* overrides .scafld/core/prompts/* overrides built-ins.

runx OSS Agent Guide

Canonical reference for AI coding agents working in the runx OSS workspace. This repo uses scafld for non-trivial work, but the architecture rules are the runx rules in CONVENTIONS.md, docs/rust-kernel-architecture.md, and docs/trusted-kernel-package-truth.md.

Read the full file on GitHub · 359 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. 3d ago First seen · 359 lines · 3,209 tokens per session scan A ce4667d2890c

Subscribe to this mod's changes

runx AGENTS.md is an instructions file published in the GitHub repository runxhq/runx (84 stars, last pushed 3d ago), licensed Apache-2.0. It adds 3,209 tokens to every session, about $0.0160 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.