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/fatihkan/badiWrote 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/fatihkan/badi/launch)<a href="https://agentmods.dev/commands/fatihkan/badi/launch"><img src="https://agentmods.dev/badge/commands/fatihkan/badi/launch.svg" alt="Measured on agentmods" 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.00000 | $0.00878 |
| Opus 5 | $0.00000 | $0.00439 |
| Sonnet 5 | $0.00000 | $0.00176 |
| Haiku 4.5 | $0.00000 | $0.00088 |
Grade A, and why
launch 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 today.
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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product launch plan command. Creates a comprehensive plan for a new product or feature launch.
Required Tools
- Read (project data)
- Grep (market research data)
- Write (plan file)
- Bash (current project analysis)
- Glob (resource scan)
Procedure (7 Steps)
Step 1: Product Summary
Get from the user:
- Product/feature name
- One-sentence value proposition
- Target audience definition
- Launch date or time window
- Success metrics (KPIs)
Build the summary:
- Problem statement (what problem does it solve?)
- Solution statement (how does it solve it?)
- Unique value proposition (why this solution?)
- Target market size estimate
Step 2: Competitive Research
Analyze the competitive landscape:
- Direct competitors (solving the same problem, 3-5)
- Indirect competitors (alternative solutions)
- For each competitor: strengths, weaknesses, pricing
- Market gap analysis
- Differentiation opportunities
- Competitor positioning matrix
Step 3: Positioning
- Target audience segmentation (primary, secondary personas)
- Unique selling proposition (USP) definition
- Messaging framework:
- Headline
- Subheadline
- 3 core benefit bullets
- Social proof strategy (testimonials, statistics, logos)
- Tone and voice (brand-aligned)
- Keywords and SEO strategy
Step 4: Pricing Analysis
- Cost-base calculation
- Competitor pricing comparison
- Value-based pricing suggestion
- Price tiers (if applicable):
- Free / Freemium
- Starter
- Professional
- Enterprise
- Intro pricing strategy
- Revenue projection (3-6-12 months)
Step 5: Landing Page Draft
Design a conversion-driven page structure:
- Hero Section: Headline + value proposition + primary CTA + visual placeholder
- Problem/Solution: Name the user's pain, show the solution
- Features: 3-6 core features, with benefits
- How It Works: A 3-4 step visual flow
- Social Proof: Testimonials, customer logos, statistics
- Pricing: Comparison table
- FAQ: 5-8 frequent questions
- Final CTA: Strong closing message + action button
- Technical: SEO meta tags, OG image, structured data
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.
- today First seen · 124 lines · 0 tokens per session scan A a661343b9f0b
launch is a command published in the GitHub repository fatihkan/badi (7 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 878 tokens. 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-09-06.
Other commands, from other repositories
audit-agents-skills
Audit quality of agents, skills, and commands in a Claude Code project.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary — the complete landing pipeline.
qa
Systematic QA testing of a web application — diff-aware, tiered, with fix-and-verify loop.
review-pr
Perform a comprehensive code review of a pull request.
security-audit
Comprehensive security audit with scored posture assessment.
git-worktree-clean
Clean up stale git worktrees with merged branch detection and disk usage report.