Borrowing it
Nothing to install: this file belongs to yusifeng/formax. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/yusifeng/formax/main/.codex/skills/formax-slash-command-workflow/SKILL.mdgit clone --depth 1 https://github.com/yusifeng/formaxWrote 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/yusifeng/formax/formax-slash-command-workflow)<a href="https://agentmods.dev/skills/yusifeng/formax/formax-slash-command-workflow"><img src="https://agentmods.dev/badge/skills/yusifeng/formax/formax-slash-command-workflow.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.1 | $0.00051 | $0.00927 |
| Opus 5 | $0.00026 | $0.00464 |
| Sonnet 5 | $0.00010 | $0.00185 |
| Haiku 4.5 | $0.00005 | $0.00093 |
Grade A, and why
formax-slash-command-workflow 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 7d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Formax slash command workflow
Goal
Use this skill when changing slash command discovery, dispatch, overlay dismissal output, or next-turn injection behavior.
Read First
docs/contracts/slash-command-contract.mddocs/contracts/semantics-contract.mdwhen command behavior crosses canonical UI messages or routingdocs/contracts/config-settings-contract.mdwhen the change touches/config
These docs are canonical. If stable behavior changes, update them before or with code.
Code Map
1) Command discovery + dispatch
packages/core/src/features/commands/registry.ts: command list/suggest/dispatch wiringpackages/core/src/features/commands/CommandStore.ts: disk scanning + precedence (project overrides user)packages/core/src/features/semantics/core/commandRouting.ts: exact/clear//compactand command-dispatch routing boundary
2) Command result contract (UI vs model)
packages/core/src/features/commands/contracts.ts:UiEffect/UiMessage/ModelEffectshapespackages/core/src/features/commands/adapter.ts: maps command execution output →CommandResultpackages/core/src/features/repl/controller/send/send.ts: consumed slash handling,local_async, and injected-block plumbing
3) Overlay dismissal “subline output”
packages/core/src/features/repl/controller/ui/overlays.ts: overlay open/close + append “dismissed” sublines
4) REPL message plumbing + rendering
packages/core/src/features/repl/controller/send/send.ts: appliesUiEffect.appendMessagestoMsgpackages/core/src/screens/REPL.tsx: rendermsg.ui.kind === 'command_subline'as⎿ ...(no⏺)packages/core/src/screens/REPL.slashSuggestions.test.tsx: duplicate command selection /preferredSlashSpecId
High-Signal Patterns
- Pattern A: one-line overlay dismissal
- append a single assistant
Msgwithui.kind='command_subline' - keep copy stable unless the user explicitly requests copy changes
- append a single assistant
- Pattern B: multi-line local output
- split output into multiple
command_sublinerows - this is UI only; model injection remains separately controlled
- split output into multiple
- Pattern C: inject-but-don't-spam
- when a command needs to inform the model, keep UI output minimal and preserve
recordForNextTurn/ injected-block behavior separately
- when a command needs to inform the model, keep UI output minimal and preserve
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.
- 7d ago First seen · 73 lines · 51 tokens per session scan A e86dddd43858
formax-slash-command-workflow is a skill published in the GitHub repository yusifeng/formax (192 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 927 once invoked, about $0.0003 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 skills, from other repositories
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
work
Execute an approved wish plan — orchestrate subagents per task group with fix loops, validation, and review handoff.
trace
Dispatch trace subagent to investigate unknown issues — reproduces, traces, and reports root cause for fix handoff.
preview-design
Render a real artifact through this branch's local MERIDIAN design code (not the published npm package) so the team can test the new Design Convention on the document / handoff / platform surfaces before it ships. Use for /preview-design, "preview the design convention", "render this with the new design", or Design…
sw-do
Implement a SpecWeave increment task by task through the ledger, with evidence per task and a verified close. Use for "implement this", "start working", "continue the increment", "keep going".
done
Close an increment: ledger check, specweave verify, optional review, then specweave complete. Use when all tasks are done and saying "close increment", "we are done", or "finish up".