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/WARROOM-CEO/COREWrote 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/warroom-ceo/core/example-command)<a href="https://agentmods.dev/commands/warroom-ceo/core/example-command"><img src="https://agentmods.dev/badge/commands/warroom-ceo/core/example-command/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/warroom-ceo/core/example-command"><img src="https://agentmods.dev/badge/commands/warroom-ceo/core/example-command.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.00032 | $0.00356 |
| Opus 5.5 | $0.00013 | $0.00142 |
| Sonnet 5.5 | $0.00006 | $0.00071 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
example-command 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
Language: All user-facing output — responses, summaries, and any text the user will read — must be written in Thai (ภาษาไทย). Internal logic, file paths, code snippets, and technical values remain in English.
Example Command (Legacy commands/ Format) — Thai Edition
Note: This demonstrates the legacy
commands/*.mdlayout. For new plugins, prefer theskills/<name>/SKILL.mddirectory format (seeskills/example-command/SKILL.mdin this plugin). Both are loaded identically — the only difference is file layout.
This command demonstrates slash command structure and frontmatter options.
Arguments
The user invoked this command with: $ARGUMENTS
Instructions
When this command is invoked:
- Parse the arguments provided by the user
- Perform the requested action using allowed tools
- Report results back to the user
Frontmatter Options Reference
Commands support these frontmatter fields:
- description: Short description shown in /help
- argument-hint: Hints for command arguments shown to user
- allowed-tools: Pre-approved tools for this command (reduces permission prompts)
- model: Override the model (e.g., "haiku", "sonnet", "opus")
Example Usage
/example-command my-argument
/example-command arg1 arg2
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 · 42 lines · 32 tokens per session scan A b155f18b2deb
example-command is a command published in the GitHub repository WARROOM-CEO/CORE (30 stars, last pushed 6mo ago), licensed MIT. It adds 32 tokens to every session and 356 once invoked, about $0.0001 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-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.