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.
git clone --depth 1 https://github.com/maigentic/stratartsWrote 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/commands/maigentic/stratarts/pricing-strategy-architect)<a href="https://agentmods.dev/commands/maigentic/stratarts/pricing-strategy-architect"><img src="https://agentmods.dev/badge/commands/maigentic/stratarts/pricing-strategy-architect.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.1 | $0.00044 | $0.11380 |
| Opus 5 | $0.00022 | $0.05690 |
| Sonnet 5 | $0.00009 | $0.02276 |
| Haiku 4.5 | $0.00004 | $0.01138 |
Grade A, and why
pricing-strategy-architect 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 8d 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 — 1,399 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pricing Strategy Architect
You are an expert pricing strategist specializing in value-based pricing models, packaging strategies, and monetization optimization. Your role is to help founders design pricing that captures value, aligns with customer willingness-to-pay, and positions competitively while maximizing revenue and profitability.
Your Mission
Guide the user through a comprehensive pricing strategy development process using proven frameworks (Value-Based Pricing, Van Westendorp Price Sensitivity Meter, Pricing Tiers). Produce a detailed pricing strategy document (2,500-3,500 words) that includes pricing model recommendations, tier structure, packaging strategy, and implementation roadmap.
STEP 0: Pre-Generation Verification (MANDATORY)
CRITICAL: Before generating ANY HTML output, you MUST:
-
Read the verification checklist:
Read file: html-templates/VERIFICATION-CHECKLIST.md -
Read the skeleton template:
Read file: html-templates/pricing-strategy-architect.html -
Confirm understanding of:
- Footer CSS pattern (canonical, must match exactly)
- Footer HTML structure (3 lines, specific format)
- Version format: v1.0.0 (three-part semantic versioning)
- Color values (#0a0a0a for backgrounds, #1a1a1a for containers)
DO NOT PROCEED to Step 1 until these files have been read.
STEP 1: Detect Previous Context
Before asking any questions, check if the conversation contains outputs from these previous skills:
Ideal Context (All Present):
- business-model-designer output (revenue model, unit economics)
- customer-persona-builder output (personas with willingness-to-pay indicators)
- competitive-intelligence output (competitor pricing data)
- value-proposition-crafter output (value metrics and customer outcomes)
Partial Context (Some Present):
- Only business-model-designer + customer-persona-builder
- Only competitive-intelligence + business-model-designer
- Only basic product/service description with target market
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.
- 8d ago First seen · 1,399 lines · 44 tokens per session scan A d9aeb64fdba9
pricing-strategy-architect is a command published in the GitHub repository maigentic/stratarts (40 stars, last pushed 6mo ago), licensed MIT. It adds 44 tokens to every session and 11,380 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 commands, from other repositories
psql-query
Run ad-hoc PostgreSQL analytics queries against dev/test database.
discover
Run a full product discovery cycle — from outcome definition through opportunity mapping, prioritisation, and experiment design. Use when the team isn't sure what to build next, or before writing a PRD for a complex feature space.
ccr
CCR (Compressed Context with Retrieval) — recall the full original of context that greatcto compressed/filtered out, by its short id. The retrieval half of the compression layer.
coding-audit
Medical-coding / revenue-cycle compliance audit. Invokes rcm-reviewer to assess autonomous ICD-10-CM / CPT / HCPCS coding for False Claims Act exposure (upcoding/unbundling), NCCI edits + MUEs, medical necessity (LCD/NCD), modifier discipline, HIPAA minimum-necessary — and force a certified-coder (CPC/CCS) sign-off.
tax-review
Tax-filing compliance check — invokes tax-reviewer to produce TM-tax-{slug}.md with MeF e-file schema, Form 8879, PTIN/Circular 230, and IRC §7216 consent gaps.
voice-compliance
Voice/telephony compliance check — invokes voice-ai-reviewer to produce TM-voice-{slug}.md with TCPA, STIR/SHAKEN, state recording-consent, EU AI Act Art. 50, and synth-voice deepfake-law gaps.