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/racecraft-lab/paddock/agents-mdgit clone --depth 1 https://github.com/racecraft-lab/PaddockWrote 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.
[](https://agentmods.dev/instructions/racecraft-lab/paddock/agents-md)<a href="https://agentmods.dev/instructions/racecraft-lab/paddock/agents-md"><img src="https://agentmods.dev/badge/instructions/racecraft-lab/paddock/agents-md.svg" alt="Measured on agentmods" height="20"></a>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.07040 | $0.07040 |
| Opus 5 | $0.03520 | $0.03520 |
| Sonnet 5 | $0.01408 | $0.01408 |
| Haiku 4.5 | $0.00704 | $0.00704 |
Grade A, and why
Paddock AGENTS.md scanned grade A with 1 finding 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 today.
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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- TypeScript 5.7 strict on Node >=22 + Next.js 16 App Router, React 19, `better-sqlite3`, existing feature-flag/auth/workspace/task-stage helpers, Node `child_process`/stream/timer/crypto/fs APIs, Vitest, Playwright; no How it starts
The opening of the file, as written. The whole thing — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Paddock
Open-source dashboard for AI agent orchestration. Manage agent fleets, track tasks, monitor costs, and orchestrate workflows.
Stack: Next.js 16, React 19, TypeScript 5, SQLite (better-sqlite3), Tailwind CSS 3, Zustand, pnpm
OpenClaw Node Deployment Notes
- These notes apply to operator-managed Paddock worktrees:
<live-worktree>(livemain) and<dev-worktree>(dev branch). - Paddock should run from
racecraft-lab/Paddockmain. - Active systemd unit:
paddock.service - Active startup wrapper:
~/.local/bin/mc-start.sh - The wrapper resolves runtime secrets from the operator's configured secret manager at startup.
- Active service worktree:
<live-worktree>onmain;<dev-worktree>is the development worktree on the active feature branch. - OpenClaw is a separate deploy surface on the operator node. The gateway should run from
<openclaw-release-symlink>, which should point at the clean tagged release tree, not from a Homebrew global package path. - If you change startup assumptions, verify both:
systemctl --user status --no-pager paddock.servicesystemctl --user status --no-pager openclaw-gateway.service
Prerequisites
- Node.js >= 22 (LTS recommended; 24.x also supported)
- pnpm (
corepack enableto auto-install)
Setup
pnpm install
pnpm build
Secrets (AUTH_SECRET, API_KEY) auto-generate on first run if not set.
Visit http://localhost:3000/setup to create an admin account, or set AUTH_USER/AUTH_PASS in .env for headless/CI seeding.
Run
pnpm dev # development (localhost:3000)
pnpm start # production
pnpm start:standalone # standalone mode (after build)
Docker
docker compose up # zero-config
bash install.sh --docker # full guided setup
Production hardening: docker compose -f docker-compose.yml -f docker-compose.hardened.yml up -d
Tests
pnpm test # unit tests (vitest)
pnpm test:e2e # end-to-end (playwright)
pnpm typecheck # tsc --noEmit
pnpm lint # eslint
pnpm test:all # lint + typecheck + test + build + e2e
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.
- today First seen · 232 lines · 7,040 tokens per session scan A fb49906c3539
Paddock AGENTS.md is an instructions file published in the GitHub repository racecraft-lab/Paddock (11 stars, last pushed 2mo ago), licensed MIT. It adds 7,040 tokens to every session, about $0.0352 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other instructions, from other repositories
mission-control CLAUDE.md
Claude Code instructions for builderz-labs/mission-control, covering mission control, prerequisites, setup, run and docker.
kraken AGENTS.md
Instructions for rafael-adcp/kraken, covering agents.md — running as a kraken tentacle, your operating contract — read these, then follow them, why there are no deltas any more and driving it non-interactively.
helmo AGENTS.md
AGENTS.md instructions for arthurcoulston/helmo, covering agents — session routing for helmo, what kind of session is this? and universal expectations.
codex-router AGENTS.md
AGENTS.md instructions for rixzkiye/codex-router, covering codex router repository contract, product invariants and verification.
helmo CLAUDE.md
Claude Code instructions for arthurcoulston/helmo: The canonical apparatus for this repository is AGENTS.md — read it first; it routes every session (summoned roles load only their role file; dev sessions load DEV.md). This file exists only because Claude Code looks for CLAUDE.md. Substance never lives here.
superspec-ai-workflow AGENTS.md
AGENTS.md instructions for itokun99/superspec-ai-workflow, covering project name — ai agent guidelines, projects, opencode + omo agent directives, 1. firewall protocol (critical boundaries) and 2. sub-agent delegation (omni-routing).