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/feature-video)<a href="https://agentmods.dev/commands/aegntic/compound-engineering/feature-video"><img src="https://agentmods.dev/badge/commands/aegntic/compound-engineering/feature-video/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/feature-video"><img src="https://agentmods.dev/badge/commands/aegntic/compound-engineering/feature-video.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.00017 | $0.02025 |
| Opus 5.5 | $0.00007 | $0.00810 |
| Sonnet 5.5 | $0.00003 | $0.00405 |
| Haiku 4.5 | $0.00002 | $0.00202 |
Grade C, and why
feature-video scanned grade C 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 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf tmp/screenshots How it starts
The opening of the file, as written. The whole thing — 328 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Video Walkthrough
<command_purpose>Record a video walkthrough demonstrating a feature, upload it, and add it to the PR description.</command_purpose>
Introduction
Developer Relations Engineer creating feature demo videos
This command creates professional video walkthroughs of features for PR documentation:
- Records browser interactions using agent-browser CLI
- Demonstrates the complete user flow
- Uploads the video for easy sharing
- Updates the PR description with an embedded video
Prerequisites
Setup
Check installation:
command -v agent-browser >/dev/null 2>&1 && echo "Installed" || echo "NOT INSTALLED"
Install if needed:
npm install -g agent-browser && agent-browser install
See the agent-browser skill for detailed usage.
Main Tasks
1. Parse Arguments
<parse_args>
Arguments: $ARGUMENTS
Parse the input:
- First argument: PR number or "current" (defaults to current branch's PR)
- Second argument: Base URL (defaults to
http://localhost:3000)
# Get current branch name
git branch --show-current
</parse_args>
2. Gather Feature Context
<gather_context>
Get branch context:
git log --oneline main..HEAD
Get changed files:
git diff --name-only main...HEAD
Map files to testable routes (same as playwright-test):
| File Pattern | Route(s) |
|---|---|
app/Http/Controllers/*Controller.php |
Corresponding API routes (check routes/components/) |
app/Services/*Service.php |
API routes using those services |
src/nuxt/*/pages/* |
Nuxt page routes (filesystem-based) |
src/nuxt/*/components/* |
Pages using those components |
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 · 328 lines · 17 tokens per session scan C d57112f6c4ac
feature-video is a command published in the GitHub repository aegntic/compound-engineering (1 stars, last pushed 4mo ago), licensed MIT. It adds 17 tokens to every session and 2,025 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
merge-check
A pre-merge checklist command for a GitHub pull request. A pull request is a proposed code change, and the command checks whether it meets the project’s documented requirements before merging.
release-kick
A release command for the River Review project that checks release instructions and pull-request state, updates an out-of-date branch, and verifies the release after merging.
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.
pr
A command that drafts a pull request (PR) description, the summary attached to a code change for review, using a set template. It checks that the description matches the actual changes before finalizing it.
brief
Brief a PR, MR or the current branch with Punchcard — the reviewer's orientation before the review, never a review.