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/nasrulhazim/claudeWrote 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/nasrulhazim/claude/sales-get-pricing)<a href="https://agentmods.dev/commands/nasrulhazim/claude/sales-get-pricing"><img src="https://agentmods.dev/badge/commands/nasrulhazim/claude/sales-get-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/commands/nasrulhazim/claude/sales-get-pricing"><img src="https://agentmods.dev/badge/commands/nasrulhazim/claude/sales-get-pricing.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.00014 | $0.01589 |
| Opus 5 | $0.00007 | $0.00794 |
| Sonnet 5 | $0.00003 | $0.00318 |
| Haiku 4.5 | $0.00001 | $0.00159 |
Grade A, and why
sales-get-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 11d 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 — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sales-get-pricing Command
Get comprehensive pricing information based on the scenario specified.
Usage
/sales-get-pricing [scenario]
Behavior
-
Find product config: Look for
product-config.mdin the current project, or use defaults from~/.claude/sales-reference.md -
Parse scenario: Understand what pricing the user needs:
license/base/standard→ Base product pricingwith [addon]→ Base + specific add-onvia [channel]→ Partner channel pricingpartner comparison→ All partner channels side by side[customer-type]→ Package pricing (sme, enterprise, government)full project→ Complete project breakdown
-
Calculate and format: Apply margins, calculate totals, format output
Output Destination
- Create directory
docs/sales-kit/if it doesn't exist. - Write the full formatted output to
docs/sales-kit/pricing.md. - Display a brief confirmation:
Pricing saved to docs/sales-kit/pricing.md
Scenario Patterns
Direct Sales
/sales-get-pricing license→ Base license price/sales-get-pricing base→ Same as license/sales-get-pricing with monitoring→ License + monitoring add-on/sales-get-pricing with ELK and training→ Multiple add-ons
Partner Channels
/sales-get-pricing via referrer→ 10% margin calculation/sales-get-pricing via affiliate→ 20% margin calculation/sales-get-pricing via reseller→ 30% margin calculation/sales-get-pricing via fronting→ 15% fee calculation/sales-get-pricing partner comparison→ All channels side by side
Project-Based
/sales-get-pricing sme→ SME package/sales-get-pricing enterprise→ Enterprise package/sales-get-pricing government→ Government package/sales-get-pricing government full project→ Full scope breakdown
Custom
/sales-get-pricing for 10 users with SSO→ Custom calculation/sales-get-pricing project worth RM 200k via fronting→ Partner split
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.
- 11d ago First seen · 262 lines · 14 tokens per session scan A 9ac57638928b
sales-get-pricing is a command published in the GitHub repository nasrulhazim/claude (22 stars, last pushed 8d ago), licensed MIT. It adds 14 tokens to every session and 1,589 once invoked, about $0.0001 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.