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 skills/fattain-naime/engineering-docs/business-conceptnpx skills add fattain-naime/engineering-docs --skill business-conceptgit clone --depth 1 https://github.com/fattain-naime/engineering-docsWrote 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/fattain-naime/engineering-docs/business-concept)<a href="https://agentmods.dev/skills/fattain-naime/engineering-docs/business-concept"><img src="https://agentmods.dev/badge/skills/fattain-naime/engineering-docs/business-concept.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.00045 | $0.03338 |
| Opus 5 | $0.00023 | $0.01669 |
| Sonnet 5 | $0.00009 | $0.00668 |
| Haiku 4.5 | $0.00005 | $0.00334 |
Grade A, and why
business-concept 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 — 286 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Business Concept
Purpose
Turn a raw business idea — however vague or detailed — into a complete business concept document. This is the foundational artifact that every downstream technical document reads from. Without it, every architecture decision, every requirement, and every design choice is built on assumptions.
This skill focuses on the BUSINESS, not the technology. It answers: what problem is being solved, for whom, why it matters, and what constraints shape the solution space.
Input
Works best with: A description of the project idea, in the user's own words, at any level of polish. Also valuable: Anything the user already knows about the market, competitors, or constraints.
Do not require a polished brief before starting. Extracting the details is this skill's first job.
Key Concepts
Business Concept vs Project Plan
| Aspect | Business Concept (this skill) | Project Plan (project-plan) |
|---|---|---|
| Focus | The IDEA — what and why | The DELIVERY — how and when |
| Questions | What problem? For whom? Why now? | What scope? What milestones? Who owns what? |
| Output | Problem statement, users, value prop, constraints | WBS, RACI, timeline, risk register |
| Timing | Phase 0 — before any technical work | Phase 1 — after the concept is clear |
Standing Constraint Questions
These questions establish project-wide constraints that affect every downstream document. Ask them once, early, and record the answers. Every later skill reads these.
- Team size and skill level — affects stack/framework recommendations
- Hosting/infra preference — self-hosted, cloud, existing vendor lock-in
- Budget sensitivity — managed-service vs self-hosted tradeoffs
- Timeline urgency — MVP-speed vs enterprise rigor
- Regulatory/compliance needs — data residency, PCI, GDPR, etc.
- Existing systems — what this must integrate with or avoid conflicting with
The Escape Hatch
Every question must accept "I don't know, you decide" as a valid answer. When the user takes that path:
- Pick the most reasonable option given everything gathered so far
- Record the choice AND the reasoning in the document, tagged as
[agent-decided] - Continue without blocking
What ships with it
1 file 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 First seen · 286 lines · 45 tokens per session scan A 84ab07853946
business-concept is a skill published in the GitHub repository fattain-naime/engineering-docs (4 stars, last pushed 20d ago), licensed MIT. It adds 45 tokens to every session and 3,338 once invoked, about $0.0002 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…