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 whawkinsiv/solo-founder-skills --skill pricinggit clone --depth 1 https://github.com/whawkinsiv/solo-founder-skillsWrote 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/whawkinsiv/solo-founder-skills/pricing)<a href="https://agentmods.dev/skills/whawkinsiv/solo-founder-skills/pricing"><img src="https://agentmods.dev/badge/skills/whawkinsiv/solo-founder-skills/pricing/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/whawkinsiv/solo-founder-skills/pricing"><img src="https://agentmods.dev/badge/skills/whawkinsiv/solo-founder-skills/pricing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
SkillSpector: 1 finding, up to low
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- low Privilege Escalation · line 129 Skill requests more permissions than appear necessary for its stated functionality. Review if elevated access is justified.Fix: Request only the minimum permissions required. Document why each permission is needed. Remove broad permissions like '*' or 'all'.
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.00084 | $0.02052 |
| Opus 5 | $0.00042 | $0.01026 |
| Sonnet 5 | $0.00017 | $0.00410 |
| Haiku 4.5 | $0.00008 | $0.00205 |
Grade A, and why
pricing 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 12d 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 — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pricing & Monetization
Price is a signal. Too low says "toy." Too high says "enterprise." Your price tells customers who this product is for. This skill helps you choose what to charge, how to structure tiers, and how to build a pricing page that converts.
Core Principles
- Pricing is a psychology problem, not a math problem.
- Align price with the value metric — the unit of value your customer receives.
- Three tiers is the default for a reason: anchoring, self-selection, and upgrade paths.
- The best pricing is simple to understand and hard to outgrow.
- Most SaaS companies underprice by 2-3x. Revisit pricing every 6 months.
Workflow
Pricing Setup:
- [ ] Choose your value metric
- [ ] Design tier structure (Free → Pro → Business)
- [ ] Set price points
- [ ] Build the pricing page
- [ ] Plan expansion revenue mechanics
Step 1: Choose Your Value Metric
The value metric is what you charge for. It should be:
- Easy to understand: The customer can predict their bill.
- Aligned with value: As they get more value, they pay more.
- Scalable: It grows with their usage naturally.
| SaaS Type | Good Value Metric |
|---|---|
| Collaboration tools | Per seat/user |
| Developer tools | API calls, compute time, builds |
| Marketing tools | Contacts, emails sent, campaigns |
| Analytics | Events tracked, data points, queries |
| Storage/infra | GB stored, bandwidth |
Bad value metrics: Features-only gating (bloated top tiers), flat pricing (no expansion revenue), complex formulas nobody can predict.
Tell AI:
Help me choose a value metric for my SaaS:
- Product: [what it does]
- Users: [who uses it and how]
- Core value: [what outcome users get]
- Current model: [if any — flat rate, per user, etc.]
Recommend a value metric that's easy for users to understand, scales with the value
they receive, and creates natural expansion revenue. Show 2-3 options with tradeoffs.
Step 2: Design Tier Structure
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.
- 12d ago First seen · 226 lines · 84 tokens per session scan A fa9d8ad2abfc
pricing is a skill published in the GitHub repository whawkinsiv/solo-founder-skills (243 stars, last pushed 16d ago), licensed MIT. It adds 84 tokens to every session and 2,052 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-30.
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…