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-marketing)<a href="https://agentmods.dev/commands/nasrulhazim/claude/sales-get-marketing"><img src="https://agentmods.dev/badge/commands/nasrulhazim/claude/sales-get-marketing/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-marketing"><img src="https://agentmods.dev/badge/commands/nasrulhazim/claude/sales-get-marketing.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.01676 |
| Opus 5 | $0.00009 | $0.00838 |
| Sonnet 5 | $0.00003 | $0.00335 |
| Haiku 4.5 | $0.00002 | $0.00168 |
Grade A, and why
sales-get-marketing 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 12d 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 — 320 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sales-get-marketing Command
Generate marketing content for products/services.
Usage
/sales-get-marketing [type] [style]
Output Destination
- Create directory
docs/sales-kit/if it doesn't exist. - Write the full formatted output to
docs/sales-kit/marketing.md. - Display a brief confirmation:
Marketing content saved to docs/sales-kit/marketing.md
Types
| Type | Description |
|---|---|
tagline / taglines |
Product taglines |
elevator / pitch |
30-second elevator pitch |
social |
Social media posts |
value / roi |
Value proposition & ROI |
features |
Feature highlights |
comparison |
Competitive positioning |
Styles (for social media)
| Style | Description |
|---|---|
casual |
Relaxed, conversational tone |
professional |
Business/LinkedIn tone |
problem-solution |
Lead with pain point |
behind-the-scene |
Founder story style |
short / punchy |
Quick, impactful |
Output Formats
Taglines
## TAGLINES
**Primary:**
> "[Main tagline]"
**Alternatives:**
- "[Alternative 1]"
- "[Alternative 2]"
- "[Alternative 3]"
**Usage:**
| Placement | Tagline |
|-----------|---------|
| Website hero | Primary tagline |
| Social media bio | Alternative 1 |
| Email signature | Alternative 2 |
Elevator Pitch
## ELEVATOR PITCH (30 seconds)
> "[Your pitch here - approximately 50-75 words that
> explain what the product does, who it's for, and
> why they should care. End with price point or CTA.]"
**Key Points:**
1. [Problem statement]
2. [Solution]
3. [Key differentiator]
4. [Price/CTA]
Social Media
## SOCIAL MEDIA POST: [Style]
[Post content here]
---
**Hashtags:** #hashtag1 #hashtag2 #hashtag3
**Best for:**
- [Platform 1]
- [Platform 2]
**Post time:** [time recommendation]
Value Proposition / ROI
## VALUE PROPOSITION
**Problem:**
[What pain point does this solve?]
**Solution:**
[How does the product solve it?]
**ROI Calculation:**
| Current State (Without Product) | |
|---|---|
| Hours spent on [task]/month | [X] hours |
| Hourly rate | [currency] [X] |
| Monthly cost | [currency] [X] |
| Annual cost | [currency] [X] |
| With Product | |
|---|---|
| Investment | [currency] [X] |
| Payback period | [X months] |
**Additional Benefits:**
- [Benefit 1]
- [Benefit 2]
- [Benefit 3]
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.
- 12d ago First seen · 320 lines · 17 tokens per session scan A 04e3ed71521f
sales-get-marketing is a command published in the GitHub repository nasrulhazim/claude (22 stars, last pushed 9d ago), licensed MIT. It adds 17 tokens to every session and 1,676 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.