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 commands/christopherlouet/claude-base/work-quickgit clone --depth 1 https://github.com/christopherlouet/claude-baseWrote 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/christopherlouet/claude-base/work-quick)<a href="https://agentmods.dev/commands/christopherlouet/claude-base/work-quick"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/work-quick.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.00000 | $0.00194 |
| Opus 5 | $0.00000 | $0.00097 |
| Sonnet 5 | $0.00000 | $0.00039 |
| Haiku 4.5 | $0.00000 | $0.00019 |
Grade A, and why
work-quick 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 yesterday.
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
WORK-QUICK Agent
Quick workflow for trivial changes (1-3 files, < 50 lines, zero risk).
Context
$ARGUMENTS
Goal
Apply a simple change without the full Explore-Plan-TDD-Audit cycle.
Eligibility criteria
- 1-3 files max
- < 50 lines modified
- No public API change
- No regression risk
If the change does not meet these criteria → use /dev:dev-tdd instead.
Workflow
- SCAN: Read the file, identify the exact change
- FIX: Apply the modification
- VERIFY: Run the existing tests
Expected output
- Change applied and verified
- Summary with modified files and test results
- Suggested commit command
IMPORTANT: If the tests fail, STOP and switch to /dev:dev-tdd.
NEVER use for business logic or API changes.
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.
- yesterday First seen · 38 lines · 0 tokens per session scan A c1954692cfad
work-quick is a command published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 194 tokens. 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-09-03.
Other commands, from other repositories
run
Implement SPEC requirements using DDD/TDD methodology.
context-stats
Display context window usage and token statistics.
run
Execute prompt(s) from ./prompts/ with automatic archiving - for structured prompt-based work.
help
Explain Ralph Wiggum technique and available commands.
cancel-ralph
Cancel active Ralph Wiggum loop.
autopilot
Autonomous session-orchestration loop with kill-switches (Phase C-1.b — all 10 kill-switches shipped).