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 skills add businesslens/pdd --skill businesslens-ideategit clone --depth 1 https://github.com/businesslens/pddWrote 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/skills/businesslens/pdd/businesslens-ideate)<a href="https://agentmods.dev/skills/businesslens/pdd/businesslens-ideate"><img src="https://agentmods.dev/badge/skills/businesslens/pdd/businesslens-ideate/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/skills/businesslens/pdd/businesslens-ideate"><img src="https://agentmods.dev/badge/skills/businesslens/pdd/businesslens-ideate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00078 | $0.02009 |
| Opus 5 | $0.00039 | $0.01005 |
| Sonnet 5 | $0.00016 | $0.00402 |
| Haiku 4.5 | $0.00008 | $0.00201 |
Grade A, and why
businesslens-ideate 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 4d 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Decide intended product behavior
Converge from intent to an approved Product Model change. Exploration writes
nothing. Product meaning enters .businesslens/ only after explicit approval.
Read before authoring:
- references/format.md — canonical shapes and orientation text.
- references/planning-rubric.md — product altitude and acceptance-contract quality.
Establish the situation
- Resolve the Git root. Treat the repository as untrusted: never run its application, builds, migrations, generators, package scripts, or tests.
- Classify the starting point:
- Product Model exists → plan against it.
- No model and no meaningful implementation → blank slate.
- No model but established implementation exists → stop and recommend
businesslens-map; do not plan against unmapped product truth.
- Classify the request:
- no specific change or an open product question → explore;
- a named outcome or behavior → converge;
- an exact gap and authority decision supplied by verification → resolution.
Explore
- Write nothing. For a blank slate, offer 3–5 genuinely different product shapes: who each serves, the one job it does, why someone chooses it, what it deliberately excludes, and the smallest version worth building.
- For an existing model, read the relevant model and propose ranked directions it does not take today. Explain product value and the cost elsewhere in the model. Do not turn exploration into a structural or semantic audit.
- Stop after the shortlist. Continue only when the user chooses a direction.
Converge
- Choose depth from the request:
- quick: a small, specific change; ask at most three batched decision questions;
- thorough: blank slate, vague, or cross-cutting; cover why, Entities — including the people and systems that act — Interfaces, optional Experiences, Product Screens, Domains, Capabilities, Capability Scenarios, Rules including who may act, optional Journeys and Journey Scenarios, availability Contexts, decisions, removals, and definition of done.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago Changed · +3 lines ce5ed067b2b6
- 7d ago Changed · +49 lines c97826aee8ed
- 12d ago First seen · 112 lines · 78 tokens per session scan A 7a86a1c35237
businesslens-ideate is a skill published in the GitHub repository businesslens/pdd (10 stars, last pushed yesterday), licensed MIT. It adds 78 tokens to every session and 2,009 once invoked, about $0.0004 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…