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 andrewcigan/vibe-dev-plugin --skill marketing-launchgit clone --depth 1 https://github.com/andrewcigan/vibe-dev-pluginWrote 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/andrewcigan/vibe-dev-plugin/marketing-launch)<a href="https://agentmods.dev/skills/andrewcigan/vibe-dev-plugin/marketing-launch"><img src="https://agentmods.dev/badge/skills/andrewcigan/vibe-dev-plugin/marketing-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.00081 | $0.00405 |
| Opus 5 | $0.00041 | $0.00202 |
| Sonnet 5 | $0.00016 | $0.00081 |
| Haiku 4.5 | $0.00008 | $0.00040 |
Grade A, and why
marketing-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 7d 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.
What it actually says
/marketing-launch
Маркетинг-пакет через marketing-launch-preparer agent.
Что происходит
- Subagent
marketing-launch-preparer(Sonnet) читает PRODUCT, validation, research/market, cost_policy - Строит 14 артефактов в
docs/marketing-launch/:- product-marketing-context, positioning, messaging
- icp-profile, pricing-strategy
- landing-page-brief (→ передаётся в Claude Design)
- landing-content, email-sequences/
- launch-plan, social-media-content, product-hunt-prep (если applicable)
- analytics-setup, support-readiness, metrics-targets
- Confirm с пользователем на pricing + ICP (бизнес-решения)
Output
docs/marketing-launch/ (14 файлов)
Confirm-points для пользователя
ТОЛЬКО эти 2 (Quality Gate — это бизнес-решения, не technical):
- Pricing structure: tiers + цены + обоснование
- ICP profile: кто целевой клиент
Остальные 12 артефактов — система делает сама.
Skip когда
- mode = FAST (это финал FULL только)
- Internal tool без рынка (личное использование)
Cost cap
$3. WebSearch до 10.
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.
- 7d ago First seen · 44 lines · 81 tokens per session scan A 7ef5a099b2fc
marketing-launch is a skill published in the GitHub repository andrewcigan/vibe-dev-plugin (5 stars, last pushed 1mo ago), licensed MIT. It adds 81 tokens to every session and 405 once invoked, about $0.0004 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-31.
Other skills, from other repositories
harness
A meta-skill for designing and maintaining a project harness: a coordinated set of specialist agents, skills, and project instructions. It defines their roles, connects them to the project, and updates the setup as the work changes.
dhpk-deploy-list
A command-line tool that builds a list of files to include in a software deployment from Git history. A deployment is the process of shipping a change to a running environment.
change-verdict
Read-only verdicts for code changes, pull requests, security, tests, documents, or change risk. Use when judging an existing change or evidence set. Not for implementing fixes, generating tests, editing documents, clearing gates, or architecture-only design. Output: evidence-backed findings, degradation state, and…
dhpk-agent-architecture-audit
Full-stack diagnostic for agent and LLM applications — audits the 12-layer agent stack for wrapper regression, memory pollution, tool-discipline failures, hidden repair loops, and rendering corruption. Use when: shipping an agent/LLM feature, an agent degrades after adding wrapper/memory/tool layers, the same model…
dhpk-js-static-check-strategy
Progressive // @ts-check per-leaf rollout playbook for legacy JS bundles. Covers the three-list legacy-globals sync (ESLint globals / TypeScript ambient .d.ts / JSDoc typedef), tsconfig exclude strategy for type-check-resistant files, leaf classification (typedef-widening-fixable vs permanent-exclude), line-anchored…
dhpk-matrix-cell-onboard
Checklist + procedure for adding a new PHP / Laravel / PHPUnit / Monolog cell to a multi-major library's CI matrix. Use when extending support to a new runtime version (e.g. "add PHP 8.3 + Laravel 12"), bumping a dep major (e.g. "Monolog 4 came out, plan the cell"), or restoring a dropped cell. Not for patch-only…