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 viknesh20-20/claude-code-tool-kit --skill business-blueprintgit clone --depth 1 https://github.com/viknesh20-20/claude-code-tool-kitWrote 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/viknesh20-20/claude-code-tool-kit/business-blueprint)<a href="https://agentmods.dev/skills/viknesh20-20/claude-code-tool-kit/business-blueprint"><img src="https://agentmods.dev/badge/skills/viknesh20-20/claude-code-tool-kit/business-blueprint/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/viknesh20-20/claude-code-tool-kit/business-blueprint"><img src="https://agentmods.dev/badge/skills/viknesh20-20/claude-code-tool-kit/business-blueprint.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.00066 | $0.03033 |
| Opus 5 | $0.00033 | $0.01517 |
| Sonnet 5 | $0.00013 | $0.00607 |
| Haiku 4.5 | $0.00007 | $0.00303 |
Grade A, and why
business-blueprint 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 9d 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 — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/business-blueprint
A structured walkthrough of business logic for the project type the user is building. Output is a personalized blueprint — the relevant domains for their app, the edge cases that matter, and a prioritized build plan.
When to use
- Starting a new SaaS / ERP / e-commerce / marketplace / fintech project — before committing to an architecture.
- Auditing an existing project against the full set of real-world concerns.
- Onboarding to a domain you haven't built before and want a checklist of what to think about.
- Preparing for a Series A / SOC 2 / enterprise customer review.
Operating method
1. Lock down the project type and context
Ask, in one round:
- Project type: SaaS / ERP / e-commerce / marketplace / fintech / internal tool / something else.
- Customer: B2C / SMB B2B / mid-market B2B / enterprise B2B / government / regulated industry.
- Sales motion: self-serve / freemium / sales-led / hybrid.
- Monetization: subscription / usage / transaction fee / one-time / hybrid.
- Jurisdictions (where customers and the business are): US / EU / UK / India / etc.
- Stage: pre-launch / early users / scaling / mature.
- Constraints: must-self-host, no-third-party-data, single-region, etc.
Don't blueprint without these. Domain ambiguity makes for irrelevant blueprints.
2. Walk the domain checklist for the project type
Different project types have different "must-have at v1" lists. Pick the matching section below.
SaaS blueprint
Identity & access
- Auth methods: password + magic link minimum; OAuth (Google/GitHub) for self-serve; SAML SSO for enterprise tier.
- MFA: TOTP + WebAuthn. Avoid SMS for high-value accounts.
- Roles: Owner > Admin > Member > Viewer (B2B default). Customize per domain.
- Permission model: role-based at v1. ABAC if resources need fine-grained ownership.
- Session: refresh tokens with rotation; idle timeout per security tier.
- Account merging: design how to handle "user signs up Google and SAML with same email."
- Account recovery: backup admin, recovery codes, support escalation path.
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.
- 9d ago First seen · 298 lines · 66 tokens per session scan A c3d970a048be
business-blueprint is a skill published in the GitHub repository viknesh20-20/claude-code-tool-kit (7 stars, last pushed 4mo ago), licensed MIT. It adds 66 tokens to every session and 3,033 once invoked, about $0.0003 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
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.
interview
Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.
package-installer
Install third-party open-source projects (a GitHub URL or a local git directory the user provides) as external packages. The project is cloned verbatim into the per-user packages directory — never edit, normalize, or reorganize its files.
cog-knowledge-consolidation
Build structured knowledge frameworks from scattered vault notes with source attribution.
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.
composition-design-review
Apply this checklist yourself after a successful composition.snapshot, before the preview is shown. It is advisory: nothing is submitted to the host, no operation records a verdict, and no gate waits on it — the host publishes the contact sheet with the passing snapshot. It is a design QA layer for your own authoring…