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.
git clone --depth 1 https://github.com/aegntic/compound-engineeringWrote 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/commands/aegntic/compound-engineering/lfg)<a href="https://agentmods.dev/commands/aegntic/compound-engineering/lfg"><img src="https://agentmods.dev/badge/commands/aegntic/compound-engineering/lfg/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.
<a href="https://agentmods.dev/commands/aegntic/compound-engineering/lfg"><img src="https://agentmods.dev/badge/commands/aegntic/compound-engineering/lfg.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00007 | $0.00174 |
| Opus 5.5 | $0.00003 | $0.00070 |
| Sonnet 5.5 | $0.00001 | $0.00035 |
| Haiku 4.5 | $0.00001 | $0.00017 |
Grade A, and why
lrj 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 1mo 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.
What it actually says
Run these slash commands in order. Do not do anything else.
/workflows:plan $ARGUMENTS/compound-engineering:deepen-plan/workflows:work-- this is the default Ralph-driven execution path and should emit red, green, and post-refactor green evidence unless the plan declares an explicit exception/workflows:review/compound-engineering:resolve_todo_parallel/compound-engineering:test-browser/compound-engineering:feature-video- Output
<promise>DONE</promise>when video is in PR
Start with step 1 now.
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.
- 1mo ago First seen · 22 lines · 7 tokens per session scan A 1a2f4ed53c72
lrj is a command published in the GitHub repository aegntic/compound-engineering (2 stars, last pushed 4mo ago), licensed MIT. It adds 7 tokens to every session and 174 once invoked, about $0.0000 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.
Other commands, from other repositories
cli-anything-web:list
List all available CLI-Anything-Web CLIs (installed and generated).
plan-merge-order
A command that plans the order for merging several pull requests (PRs), which are proposed code changes reviewed before entering a shared branch. It checks their status and file changes, then studies dependencies and overlap to reduce rebasing work.
verify-agent-report
A command for checking whether an agent’s reported branch, pull request, commit, or files actually exist. A pull request is a proposed code change submitted for review.
register-plugin-asset
A project command for adding a distributable command, agent, or agent skill to a plugin manifest, the file that lists what a plugin provides.
preflight
A pre-work check for finding whether a coding task or pull request is already finished, obsolete, or being handled elsewhere. A pull request is a proposed change to a code repository.
challenge
Adversarial review — run pre-mortem, war-game, and logic-torturing analysis on current changes.