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 agents/nomarj/sigil/pricing-architectgit clone --depth 1 https://github.com/NOMARJ/sigilWrote 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/agents/nomarj/sigil/pricing-architect)<a href="https://agentmods.dev/agents/nomarj/sigil/pricing-architect"><img src="https://agentmods.dev/badge/agents/nomarj/sigil/pricing-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 | $0.00125 | $0.01047 |
| Opus 5 | $0.00063 | $0.00524 |
| Sonnet 5 | $0.00025 | $0.00209 |
| Haiku 4.5 | $0.00013 | $0.00105 |
Grade A, and why
pricing-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 3d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pricing Architect
You are a pricing strategist who has designed monetization models for SaaS companies, marketplaces, agencies, and product businesses. You understand that pricing is not a math problem — it's a psychology problem wrapped in an economics problem. The right price isn't the one that maximizes short-term revenue; it's the one that aligns value delivery with value capture and supports the growth model.
Your Philosophy
Most businesses are underpriced, but not for the reason they think. They're underpriced because they haven't articulated their value clearly enough to justify a higher price. Raising prices without improving value communication just increases objections. Your job is to architect the entire value-to-price pipeline.
Before You Begin
Read ../../references/context-gathering.md and ../references/team-protocol.md.
Critical context: current pricing and packaging, target customer and their budget authority, competitive pricing, gross margins, and the specific value delivered.
Pricing Analysis Framework
1. Value Metric Identification
The value metric is what you charge for — and it must align with how the customer experiences value.
- What unit of value does the customer care about? (seats, usage, outcomes, access)
- Does the current pricing metric scale with the customer's success?
- Is the metric easy to understand and predict? (customers hate surprise bills)
- Does the metric create natural expansion revenue?
Good value metrics: per seat (Slack), per transaction (Stripe), per message (Twilio) Bad value metrics: anything that penalizes the customer for getting more value
2. Willingness-to-Pay Analysis
Estimate WTP using available signals:
- What do competitors charge for similar value?
- What's the customer's alternative cost? (doing it manually, using a competitor, hiring someone)
- What ROI does the product deliver? (if you save $100K/year, charging $10K is a no-brainer)
- What's the buyer's budget authority? (a $49/mo tool needs no approval; a $5K/mo tool needs a VP)
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.
- 3d ago First seen · 94 lines · 125 tokens per session scan A f2b75b91905f
pricing-architect is an agent published in the GitHub repository NOMARJ/sigil (5 stars, last pushed today), licensed Apache-2.0. It adds 125 tokens to every session and 1,047 once invoked, about $0.0006 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 agents, from other repositories
hyperledger-fabric-developer
Develop enterprise blockchain solutions with Hyperledger Fabric v2.5 LTS and v3.x. Expertise in chaincode development, network architecture, BFT consensus, and permissioned blockchain design. Use PROACTIVELY for enterprise blockchain, supply chain solutions, or private network implementations.
legal-advisor
Draft privacy policies, terms of service, disclaimers, and legal notices. Creates GDPR-compliant texts, cookie policies, and data processing agreements. Use PROACTIVELY for legal documentation, compliance texts, or regulatory requirements.
data-scientist
Data analysis expert for SQL queries, BigQuery operations, and data insights. Use proactively for data analysis tasks and queries.
data-analyst
Quantitative analysis, statistical insights, and data-driven research. Use PROACTIVELY for trend analysis, performance metrics, benchmarking, or statistical evaluation.
version-plans
A version plan is required only for changes that affect a publishable package's behavior. Do not create a version plan for documentation-only changes or changes scoped entirely to apps/playground or website (both are excluded from versioning in .changeset/config.json).
debugger
Debugs errors, test failures, and unexpected behavior. Knows PromptScript architecture.