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-quotation)<a href="https://agentmods.dev/commands/nasrulhazim/claude/sales-get-quotation"><img src="https://agentmods.dev/badge/commands/nasrulhazim/claude/sales-get-quotation/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-quotation"><img src="https://agentmods.dev/badge/commands/nasrulhazim/claude/sales-get-quotation.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.00015 | $0.02254 |
| Opus 5 | $0.00008 | $0.01127 |
| Sonnet 5 | $0.00003 | $0.00451 |
| Haiku 4.5 | $0.00002 | $0.00225 |
Grade A, and why
sales-get-quotation 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 10d 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 — 341 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sales-get-quotation Command
Generate quotation templates and breakdowns.
Usage
/sales-get-quotation [customer-type]
/sales-get-quotation for [custom requirements]
Output Destination
- Create directory
docs/sales-kit/if it doesn't exist. - Write the full formatted output to
docs/sales-kit/quotation.md. - Display a brief confirmation:
Quotation saved to docs/sales-kit/quotation.md
Customer Types
| Type | Description |
|---|---|
sme / basic |
Small/medium enterprise, basic package |
sme-plus |
SME with monitoring/add-ons |
enterprise |
Enterprise package |
government / gov |
Government standard |
government-full |
Government full scope |
custom |
Custom based on requirements |
Output Format
## QUOTATION: [Package Name]
| | |
|---|---|
| **Customer** | [Customer type/name] |
| **Date** | [Current date] |
| **Valid** | 30 days |
| No | Description | Amount |
|----|-------------|--------|
| 1 | [Line item 1] | [amount] |
| 2 | [Line item 2] | [amount] |
| 3 | [Line item 3] | [amount] |
| | **TOTAL** | **[total]** |
**Optional Add-ons:**
| Add-on | Price |
|--------|-------|
| [Add-on 1] | [amount] |
| [Add-on 2] | [amount] |
**Terms:**
- [Term 1]
- [Term 2]
**Notes:**
- [Note 1]
- [Note 2]
Configuration Reference
The command reads from product-config.md:
# Quotation Templates
quotation_templates:
- name: "SME Basic"
customer_type: "sme"
line_items:
- description: "Product License"
price: 25000
total: 25000
notes:
- "Deployment included"
- "1 year support included"
- name: "Enterprise Full"
customer_type: "enterprise"
line_items:
- description: "Product License"
price: 25000
- description: "Monitoring Integration"
price: 25000
- description: "Customization"
price_min: 10000
price_max: 25000
- description: "Training (3 days)"
price: 15000
total_min: 75000
total_max: 90000
# Default terms
quotation_terms:
- "Prices quoted in MYR"
- "Valid for 30 days"
- "50% upon confirmation, 50% upon completion"
- "Warranty: 3 months from deployment"
# Default notes
quotation_notes:
- "Deployment included"
- "1 year updates & support included"
- "Maintenance Year 2+: 20% of license fee"
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.
- 10d ago First seen · 341 lines · 15 tokens per session scan A b7d940a8e4b6
sales-get-quotation is a command published in the GitHub repository nasrulhazim/claude (22 stars, last pushed 7d ago), licensed MIT. It adds 15 tokens to every session and 2,254 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
dev
Runs Vendure in development mode. By default it starts three processes: the GraphQL server (ts-node ./src/index.ts), the worker (ts-node ./src/index-worker.ts), and the dashboard (a Vite dev server).
start
Runs a project that has already been compiled with vendure build.
validate-idea
Validate Shopify app idea against market demand, category saturation, App Store discovery patterns, and monetization viability.
ebay-orders
Check recent eBay orders and fulfillment status.
intake
You are running the intake for this purchase. The goal is to populate spec.md at the repo root with the per-purchase brief.
price-strategy
You are a senior E-commerce & Retail specialist. The user needs help with price strategy in the context of product catalogue optimisation, conversion rate, customer journey and retail analytics.