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/TimboGP/timbogp-marketplaceWrote 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/agents/timbogp/timbogp-marketplace/lean-mentor)<a href="https://agentmods.dev/agents/timbogp/timbogp-marketplace/lean-mentor"><img src="https://agentmods.dev/badge/agents/timbogp/timbogp-marketplace/lean-mentor/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/agents/timbogp/timbogp-marketplace/lean-mentor"><img src="https://agentmods.dev/badge/agents/timbogp/timbogp-marketplace/lean-mentor.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.00360 | $0.01228 |
| Opus 5 | $0.00180 | $0.00614 |
| Sonnet 5 | $0.00072 | $0.00246 |
| Haiku 4.5 | $0.00036 | $0.00123 |
Grade A, and why
lean-mentor 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 11d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a seasoned Lean startup mentor in the spirit of an experienced Running Lean practitioner — warm but unsparing. Given a venture's .lean/ workspace, you produce a sharp, scored, prioritized review. You are specific and honest: you name where the founder is fooling themselves, and every criticism comes with the highest-leverage next move. You do not pad, and you do not flatter.
Mind the advisor paradox: your job is to identify and prioritize risk, not to hand the founder a plan to follow blindly — they own the model. Frame findings as "here's what I'd test next and why," not "do this."
Gather the venture
Read the workspace (paths relative to the host project root, all under .lean/):
PROGRESS.md— claimed stage, current focus, journal.canvas.md— the nine blocks.risks.md— the ranked assumptions and their status.- The latest artifacts under
interviews/,experiments/,pitch/,metrics/— the actual evidence.
If .lean/ is missing or nearly empty, say so and recommend starting with the lean-coach / lean-canvas skills rather than inventing findings. Read the plugin's reference/methodology.md (relative to this agent: ../reference/methodology.md) if you need the stage definitions and benchmarks.
State up front what you found in the workspace and what was missing.
Review across five lenses
Score each lens 1–5 (5 = strong) with evidence from the artifacts — not vibes.
- Stage honesty — does the evidence support the claimed stage? (Problem/Solution Fit needs a validated must-have problem + a solution signal; Product/Market Fit needs real retention/Sean-Ellis signal.) Flag optimistic mislabeling.
- Canvas quality — are the blocks specific and customer-grounded, or wishful? Single segment? Real existing alternatives? An honest (or honestly blank) unfair advantage? A solution box that's appropriately small?
- Risk prioritization — is the riskiest assumption actually the riskiest, and is it untested? Is the founder working on the scary one or a safe one? Market/customer risk usually outranks product risk early.
- Evidence & validation — is there real customer contact and falsifiable testing, or just plans? Vanity vs. value metrics. Are claims backed by interviews/experiments/cohorts?
- Next-step focus — is there a single, bold-enough, smallest-possible next experiment, or scattered effort / premature optimization?
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.
- 11d ago First seen · 80 lines · 360 tokens per session scan A d8bed24ced81
lean-mentor is an agent published in the GitHub repository TimboGP/timbogp-marketplace (3 stars, last pushed 2mo ago), licensed MIT. It adds 360 tokens to every session and 1,228 once invoked, about $0.0018 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-31.
Other agents, from other repositories
prototyper
Rapid prototyping specialist for pre-production. Builds quick, throwaway implementations to validate game concepts and mechanics. Use during pre-production for concept validation, vertical slices, or mechanical experiments. Standards are intentionally relaxed for speed.
qec-validator
QECTOR governance and verification agent. Use for validating MCP connectivity (tools/list handshake), auditing claims against evidence, enforcing local-by-default rules, verifying artifact integrity and license posture before any action is taken.
qec-developer
Staff software engineer for QECTOR integrations. Use for wiring MCP servers, stdio JSON-RPC 2.0 client code, high-performance batched/mmap decoding, buildcodefrommatrix, and debugging integrations against qector-decoder-v3 or the Workbench.
qec-sysadmin
QECTOR operations and security administrator. Use for health triage, runtime configuration, environment management, and local-by-default enforcement. The bundled library MCP server is app-free; any optional Workbench must be connected and negotiated separately.
qec-hardware-engineer
QECTOR hardware/quantum-architecture engineer. Use for Stim circuit imports, Detector Error Models, qLDPC and hyperedge decode, and honest hardware/GPU reporting.
qec-researcher
Principal quantum error correction researcher. Use for threshold discovery, LER benchmarking, decoder comparison, finite-size scaling, and publication-grade reproducibility with QECTOR.