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-flow-featuregit 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-flow-feature)<a href="https://agentmods.dev/commands/christopherlouet/claude-base/work-flow-feature"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/work-flow-feature.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.00427 |
| Opus 5 | $0.00000 | $0.00214 |
| Sonnet 5 | $0.00000 | $0.00085 |
| Haiku 4.5 | $0.00000 | $0.00043 |
Grade A, and why
work-flow-feature 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
Agent WORK-FLOW-FEATURE
Complete workflow for developing a new feature, from exploration to merge.
Context
$ARGUMENTS
Goal
Execute the complete development cycle of a feature: branch, exploration, planning, TDD, audit, commit, PR.
Workflow
- BRANCH: Create branch
feature/[name]from up-to-date main - EXPLORE: Analyze existing code, identify patterns and dependencies
- PLAN: Define files to create/modify, tests to write, risks
- TDD: Red-Green-Refactor cycle, tests before code, 80%+ coverage
- AUDIT: Adaptive audit + fix loop until score 90 (critical →
/qa:qa-loop "score 90", standard →/qa:qa-loop "score 90", UI →/qa:qa-design+/qa:wcag-audit) - COMMIT: Format
feat(scope): description, atomic changes - PR: Push +
gh pr createwith description, tests, checklist
Expected output
- Feature: Implemented code with tests
- Quality: 80%+ coverage, lint OK, strict types
- PR: URL with complete description and checklist
Related agents
| Agent | Usage |
|---|---|
/work:work-explore |
Exploration |
/work:work-plan |
Planning |
/dev:dev-tdd |
TDD development |
/qa:qa-loop |
Audit + fix loop (score 90) |
/qa:qa-review |
Auto-review |
/work:work-commit |
Commit |
/work:work-pr |
Pull Request |
IMPORTANT: Each step must be validated before moving to the next.
YOU MUST follow the order of steps — do not skip exploration or planning.
NEVER commit code without tests.
Think hard at each step about the quality of the deliverable.
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 · 50 lines · 0 tokens per session scan A 1a1bcc4e69e2
work-flow-feature 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 427 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
cm
Stage working tree changes and create a Conventional Commit (no push).
cp
Stage, commit, and push the current branch following git governance rules.
run
Implement SPEC requirements using DDD/TDD methodology.
atomic-commits
Analyze staged changes and organize them into intuitive atomic commits following conventional commits.
git-commit
Create a git commit for the current changes using Conventional Commits-style format.
close
End session with verification, commits, and documentation.