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 ognjengt/founder-skills --skill pricing-strategistgit clone --depth 1 https://github.com/ognjengt/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/ognjengt/founder-skills/pricing-strategist)<a href="https://agentmods.dev/skills/ognjengt/founder-skills/pricing-strategist"><img src="https://agentmods.dev/badge/skills/ognjengt/founder-skills/pricing-strategist/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/ognjengt/founder-skills/pricing-strategist"><img src="https://agentmods.dev/badge/skills/ognjengt/founder-skills/pricing-strategist.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
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 →
- medium Excessive Agency · line 61 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00049 | $0.02178 |
| Opus 5 | $0.00024 | $0.01089 |
| Sonnet 5 | $0.00010 | $0.00436 |
| Haiku 4.5 | $0.00005 | $0.00218 |
Grade A, and why
pricing-strategist 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pricing Strategist
Purpose
Build a comprehensive, justified pricing strategy — tier structures, price points, positioning, and revenue optimization — tailored to the business through context and conversation.
Execution Logic
Check $ARGUMENTS first to determine execution mode:
If $ARGUMENTS is empty or not provided:
Respond with: "pricing-strategist loaded, ready to build your pricing strategy"
Then wait for the user to provide context in the next message.
If $ARGUMENTS contains content:
Proceed immediately to Task Execution (skip the "loaded" message).
Task Execution
1. MANDATORY: Read FOUNDER_CONTEXT.md
BLOCKING REQUIREMENT — DO NOT SKIP THIS STEP
Before doing ANYTHING else, read FOUNDER_CONTEXT.md from the project root. Extract everything relevant to pricing:
- Company name, industry, product/service type
- Target audience (demographics, pain points, budget signals)
- Existing pricing model (if any)
- Competitors and their pricing (if mentioned)
- Value proposition and key features/benefits
- Business stage and revenue goals
DO NOT PROCEED to Step 2 until this file has been read.
2. Determine Which Questions to Ask
Cross-reference what FOUNDER_CONTEXT.md already provides against the Question Bank below. Only ask questions where the answer is genuinely missing or unclear. Never ask something the context already answers.
Question Bank (priority order):
| # | Question | Why it matters | Skip if... |
|---|---|---|---|
| 1 | B2B or B2C? | Changes deal size, tier logic, sales cycle, everything | Target audience section makes it obvious |
| 2 | What pricing model do you prefer or want to avoid? (subscription, one-time, usage-based, freemium, hybrid) | Determines the entire structure | Pricing model already stated in context |
| 3 | What's the primary value metric that scales with usage? (seats, API calls, storage, projects, transactions, etc.) | Drives tier differentiation and upgrade logic | Product type + features make it obvious |
| 4 | Target gross margin range? (60-70%, 70-80%, 80%+, not sure) | Sets the floor for every price point | A number or range is already given |
| 5 | How price-sensitive is your target customer? (very sensitive, moderate, willing to pay premium) | Calibrates price positioning and tier gaps | Audience detail + industry norms make it clear |
| 6 | Who are your closest competitors and how do they price? | Market anchoring — prevents under or over pricing | Competitors section is filled |
| 7 | What's your current stage or revenue target? (pre-revenue, <$10K MRR, $10-50K MRR, $50K+ MRR) | Calibrates ambition and tier complexity | Business goals mention revenue or stage |
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 · 198 lines · 49 tokens per session scan A f517838c3bfa
pricing-strategist is a skill published in the GitHub repository ognjengt/founder-skills (302 stars, last pushed 3mo ago), licensed MIT. It adds 49 tokens to every session and 2,178 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-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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…