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-create-config)<a href="https://agentmods.dev/commands/nasrulhazim/claude/sales-create-config"><img src="https://agentmods.dev/badge/commands/nasrulhazim/claude/sales-create-config/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-create-config"><img src="https://agentmods.dev/badge/commands/nasrulhazim/claude/sales-create-config.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.00017 | $0.00858 |
| Opus 5 | $0.00009 | $0.00429 |
| Sonnet 5 | $0.00003 | $0.00172 |
| Haiku 4.5 | $0.00002 | $0.00086 |
Grade A, and why
sales-create-config 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sales-create-config Command
Interactively create a product-config.md file in the current project directory.
Usage
/sales-create-config
/sales-create-config [product name]
Behavior
-
Check for existing config: Look for
product-config.mdin the current project directory. If it exists, ask the user whether to overwrite or abort. -
Read the template: Load
~/.claude/product-config-template.mdas the structural reference for all sections. -
Gather information interactively: Ask the user for their product details in the following order. Group related questions together to minimize back-and-forth. If a product name was provided as an argument, skip asking for it.
Round 1 — Core Identity
- Product name
- Company name
- Tagline
- Website
- Currency (default: MYR)
- Business model: on-premise, saas, hybrid, or service
Round 2 — Product Details
- Short description (one paragraph, under 50 words)
- Target market (primary and secondary segments)
- Ideal customer characteristics
- Core features (name + brief description for each)
Round 3 — Pricing
- Base price and unit (one-time, monthly, yearly, per-user)
- What's included in the base price
- Add-ons (name, price or price range, description)
- Maintenance/support pricing (yearly fee, percentage, when it starts)
- Minimum Advertised Price (MAP) if applicable
Round 4 — Partner Channels
- Ask if they use partner channels
- If yes, confirm or customize default margins: referrer (10%), affiliate (20%), reseller (30%), fronting (15%)
- Customize roles and responsibilities per channel if needed
Round 5 — Packages / Bundles
- Ask if they offer predefined packages
- If yes, for each package: name, target customer, components with prices, total, optional add-ons
Round 6 — Marketing Content
- Primary tagline and alternatives
- Elevator pitch (30-second, ~50-75 words)
- Social media posts (offer to generate based on product details if user prefers)
- Value proposition and ROI calculation inputs
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 · 87 lines · 17 tokens per session scan A 1a48832b3b13
sales-create-config is a command published in the GitHub repository nasrulhazim/claude (22 stars, last pushed 7d ago), licensed MIT. It adds 17 tokens to every session and 858 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.