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.
npx agentmods add instructions/subsy/ralph-tui/agents-mdgit clone --depth 1 https://github.com/subsy/ralph-tuiWhat 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.01090 | $0.01090 |
| Opus 5 | $0.00545 | $0.00545 |
| Sonnet 5 | $0.00218 | $0.00218 |
| Haiku 4.5 | $0.00109 | $0.00109 |
Grade A, and why
ralph-tui 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.
How it starts
The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions
This file provides guidance to AI coding agents when working with code in this repository.
You are an AI assistant. Your role is to assist with software development tasks while adhering to strict coding standards and practices. Here's how you should approach your work:
-
Critical Coding Rules:
- Prioritize simple, clean, and maintainable solutions over clever or complex ones.
- Make the smallest reasonable changes to achieve the desired outcome.
- Never make unrelated code changes; document issues for later instead.
- Preserve code comments unless you can prove they are actively false.
- Start all code files with a file-level JSDoc comment section explaining the file's purpose, prefixed with "ABOUTME: ".
- Avoid temporal context in comments; make them evergreen.
-
Avoiding entropy
- This codebase will outlive you. Every shortcut you take becomes someone else's burden. Every hack compounds into technical debt that slows the whole team down.
- You are not just writing code. You are shaping the future of this project. The patterns you establish will be copied. The corners you cut will be cut again.
- Fight entropy. Leave the codebase better than you found it.
Build Instructions
This project uses bun as its package manager and runtime.
# Install dependencies
bun install
# Build the project
bun run build
# Type check (no emit)
bun run typecheck
# Lint
bun run lint
bun run lint:fix # Auto-fix lint issues
# Run in development mode
bun run dev
# Clean build artifacts
bun run clean
After making code changes, always run:
bun run typecheck && bun run build
Issue Tracking with beads-rust
This project uses br (beads-rust) for issue tracking. Data is stored in .beads/ directory.
Quick Reference
br ready # Find available work (unblocked issues)
br list # List all open issues
br list --all # Include closed issues
br show <id> # View issue details with dependencies
br show <id> --json # JSON output for programmatic use
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.
- 3d ago First seen · 147 lines · 1,090 tokens per session scan A 832b6f3c029f
ralph-tui AGENTS.md is an instructions file published in the GitHub repository subsy/ralph-tui (2,434 stars, last pushed yesterday), licensed MIT. It adds 1,090 tokens to every session, about $0.0054 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.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.