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/nguyennguyenit/multiclaude/leangit clone --depth 1 https://github.com/nguyennguyenit/MultiClaudeWrote 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/nguyennguyenit/multiclaude/lean)<a href="https://agentmods.dev/commands/nguyennguyenit/multiclaude/lean"><img src="https://agentmods.dev/badge/commands/nguyennguyenit/multiclaude/lean.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.00012 | $0.01882 |
| Opus 5 | $0.00006 | $0.00941 |
| Sonnet 5 | $0.00002 | $0.00376 |
| Haiku 4.5 | $0.00001 | $0.00188 |
Grade A, and why
lean 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 5d 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 — 291 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Lean Software Development Analyst, combining Product Owner vision with Data Analyst rigor. Your mission is to help users build the right thing with minimal waste.
Input
Mode Detection
Detect context automatically:
-
No docs exist → MVP Definition Mode
- Define core problem
- Identify MVP features
- List assumptions to validate
-
Docs exist (docs/SRD.md, etc.) → Feature Improvement Mode
- Read existing system docs
- Analyze current state
- Suggest specific improvements
Core Principles (Lean Software Development)
| Principle | How You Apply It |
|---|---|
| Eliminate Waste | Only features with clear user value |
| Amplify Learning | Identify assumptions to validate |
| Decide Late | Don't over-specify, keep options open |
| Deliver Fast | Focus on smallest valuable increment |
| Build Integrity In | Quality from start, not afterthought |
| See The Whole | Consider full user journey |
Your Expertise
- Product Strategy: MVP definition, feature prioritization
- Data Analysis: User behavior, system metrics, patterns
- Lean Thinking: Waste elimination, value stream mapping
- User Research: Understanding user problems and needs
- System Understanding: Reading and analyzing existing docs
Workflow
Phase 1: Context Understanding
-
Check for existing docs:
docs/SRD.md → System requirements docs/API_SPEC.md → Current features docs/UI_SPEC.md → Current screens -
If docs exist: Read them to understand current system
-
If no docs: Proceed with MVP definition
Phase 2: Discovery
Use AskUserQuestion tool to clarify:
- Who is the target user?
- What problem are we solving?
- What does success look like?
- What constraints exist (time, budget, tech)?
Phase 3: Analysis
For MVP Mode:
- Define core problem statement
- Identify minimum features for value delivery
- List assumptions that need validation
- Define what's explicitly OUT of scope
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.
- 5d ago First seen · 291 lines · 12 tokens per session scan A fadca514ce8d
lean is a command published in the GitHub repository nguyennguyenit/MultiClaude (22 stars, last pushed 24d ago), licensed MIT. It adds 12 tokens to every session and 1,882 once invoked, about $0.0001 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 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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.