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 skills/event4u-app/agent-config/command-routingnpx skills add event4u-app/agent-config --skill command-routinggit clone --depth 1 https://github.com/event4u-app/agent-configWrote 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/skills/event4u-app/agent-config/command-routing)<a href="https://agentmods.dev/skills/event4u-app/agent-config/command-routing"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/command-routing.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.00044 | $0.01430 |
| Opus 5 | $0.00022 | $0.00715 |
| Sonnet 5 | $0.00009 | $0.00286 |
| Haiku 4.5 | $0.00004 | $0.00143 |
Grade A, and why
command-routing 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
commands
When to use
Triggered when user invokes a slash command. The slash-command-routing-policy rule (always loaded) handles core behavior — this skill adds context inference and GitHub API patterns.
Procedure: Execute a command
- Match command — Find the command file in
.augment/commands/oragents/overrides/commands/. - Infer inputs — Before asking the user, try to infer values (see table below).
2b. List a matching playbook in the preamble. If a playbook's
taskmatches the command's name, name it before the steps run — it is this repository's own procedure and outranks a shipped one (playbook-precedence). - Execute steps — Follow the command steps in exact order.
- Verify output — Confirm expected result was produced (commit, PR, file change, etc.).
Before asking the user for input, try to infer it:
| Input needed | How to infer |
|---|---|
| Jira ticket | Extract from branch name (fix/DEV-1234-... → DEV-1234) |
| Default branch | git symbolic-ref refs/remotes/origin/HEAD or assume main |
| Project type | Check for artisan (Laravel) or composer.json (Composer) |
| Module name | Extract from current working directory or file path |
| Current branch | git branch --show-current |
Only ask the user if inference fails and the command cannot proceed without the value.
Command locations
| Location | Scope |
|---|---|
.augment/commands/ |
Shared commands (work across projects) |
agents/overrides/commands/ |
Project-specific overrides (used instead of original) |
Commands that dispatch to the work engine
Most commands are pure markdown procedures — the agent reads the steps
and executes them. Two commands delegate to the work_engine engine
(TypeScript, run via tsx) via the ./agent-config dispatcher; both share the same
Option-A loop (read state → run engine → handle exit code → repeat),
they only differ in the input envelope they build:
| Command | Subcommand | Envelope | Use when |
|---|---|---|---|
/implement-ticket |
./agent-config implement-ticket |
input.kind="ticket" |
User points at a Jira/Linear ticket or supplies a structured ticket payload |
/work |
./agent-config work |
input.kind="prompt" |
User supplies a free-form prompt — no ticket id, no acceptance criteria yet |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 142 lines · 44 tokens per session scan A 13209c3deb97
command-routing is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 1,430 once invoked, about $0.0002 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-31.
Other skills, from other repositories
openbot-data-access
Governs how the OpenBot browser app reads and writes server data — every request goes through client in app/src/lib/client.ts, every read is a queryOptions factory in app/src/lib/ /queries.ts, every write is a mutationOptions factory in app/src/lib/ /mutations.ts, and components consume them through…
openbot-screen-layout
The default layout for every OpenBot configuration screen — PageShell and its prose/wide widths, PageSection and PageRows, Item row composition, the settings-row pattern where a summary and a chevron open a dialog, and the size and variant vocabulary. This is what a new screen looks like unless an instruction says…
muapi-media-editing
Edit and enhance images and videos with AI via muapi.ai — prompt-based editing, upscaling, background removal, face swap, lipsync, video effects, and more.
vox-director
Turn ONE topic into a finished Vox-style paper-collage explainer / ad video, end to end on the Atlas Cloud API + local ffmpeg — script, collage keyframes, motion, voice-over, music, captions, all automated. Use this whenever the user wants a "Vox style" video, a paper/torn-paper collage animation, a "motion collage"…
muapi-storyboard-to-cooking-video
Turn a single photo of a person into a 15-second cinematic pasta-making (or other cuisine) tutorial video. First builds a composite reference sheet (character + kitchen + 9-step action board), then animates the full cooking sequence with audio in a single continuous shot.
stage-edit
Intelligent editing of real user-supplied footage—understand it with transcript/OCR/scene/silence/quality/vision evidence, then choose deterministic timeline operations or a constrained semantic AI edit. Trigger for repurpose, montage, cleanup, localization, narration, or local content changes.