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 skills add Brainrot-Creations/claude-plugins --skill product-promotiongit clone --depth 1 https://github.com/Brainrot-Creations/claude-pluginsWrote 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/skills/brainrot-creations/claude-plugins/product-promotion)<a href="https://agentmods.dev/skills/brainrot-creations/claude-plugins/product-promotion"><img src="https://agentmods.dev/badge/skills/brainrot-creations/claude-plugins/product-promotion/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/skills/brainrot-creations/claude-plugins/product-promotion"><img src="https://agentmods.dev/badge/skills/brainrot-creations/claude-plugins/product-promotion.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.00045 | $0.01051 |
| Opus 5 | $0.00023 | $0.00526 |
| Sonnet 5 | $0.00009 | $0.00210 |
| Haiku 4.5 | $0.00005 | $0.00105 |
Grade A, and why
product-promotion 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- product-promotion — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Promotion Guide
Help users promote their products authentically without coming across as spam.
The golden rule
Add value first, mention product second.
Every promotional post or reply must stand on its own merit. If you removed the product mention entirely, the content should still be worth posting.
When product promotion works
Good opportunities
- Someone asks for tool/product recommendations in your category
- A discussion about a problem your product solves
- Sharing genuine results or lessons learned from building
- Responding to direct questions about solutions
- Show-and-tell threads (X) or dedicated promo threads (Reddit)
Bad opportunities
- Random unrelated posts (looks like spam)
- Emotional/personal posts (insensitive)
- Threads already saturated with self-promo
- Controversial topics (brand risk)
- When you have nothing valuable to add beyond "use my product"
Platform-specific rules
X (Twitter)
- Replies can mention products if genuinely relevant
- Don't spam the same reply to multiple people
- Quote tweets with added insight work well
- Building in public threads are accepted promo
- Avoid replying to big accounts just for visibility (transparent and cringe)
- Comments should add professional value first
- Soft mentions work better than hard pitches
- Share case studies and learnings, not just features
- Connection request + immediate pitch = blocked
- Posts about your journey/building are accepted
- Most strict about self-promotion
- Many subs ban it entirely or require specific threads
- Ratio matters: 90% helpful content, 10% promo max
- Always disclose if it's your product ("I built X...")
- Never create fake accounts to promote
- Add genuine value in comments consistently before ever mentioning your product
How to structure a promotional reply
Pattern 1: Help first, mention after
[Directly address their question/problem with useful insight]
[Optional: share relevant experience]
[Brief mention: "I actually built [Product] for this exact reason" or "We solve this with [Product]"]
[Back to helping: additional tip or offer to answer questions]
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 · 139 lines · 45 tokens per session scan A 33a10ca06cc3
product-promotion is a skill published in the GitHub repository Brainrot-Creations/claude-plugins (22 stars, last pushed 2mo ago), licensed MIT. It adds 45 tokens to every session and 1,051 once invoked, about $0.0002 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 skills, from other repositories
cco-tools
Show what tools actually cost in tokens — learned per-tool averages from observed results, replacing the hardcoded MCP/Agent guesses.
github-pr-creation
Creates GitHub Pull Requests with automated validation and task tracking. Use when user wants to create PR, open pull request, submit for review, or check if ready for PR. Analyzes commits, validates task completion, generates Conventional Commits title and description, suggests labels. NOTE - for merging existing…
test-run
Run plugin test suites in this monorepo and report a concise pass/fail summary. Optional plugin slug arg; without arg, runs all plugins under plugins/.
design-system-reference
Style guides and implementation rules for frontend design. Works with design-discovery agent which handles context gathering and VS-based style recommendations. Contains detailed style guides, anti-patterns, and implementation checklists.
pipeline-report
A procedure for reporting the state of an amoCRM sales funnel, a set of stages that deals move through before they are won or lost. It groups deals by stage and value and checks how long they have been inactive.
refund-payment
A payment procedure for refunding a completed T-Kassa payment or cancelling a payment that is still on hold. T-Kassa is a payment service, and the procedure can also send the required closing receipt.