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 hoavdc/CodexKit --skill codexkit-go-to-market-plannergit clone --depth 1 https://github.com/hoavdc/CodexKitWrote 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/hoavdc/codexkit/codexkit-go-to-market-planner)<a href="https://agentmods.dev/skills/hoavdc/codexkit/codexkit-go-to-market-planner"><img src="https://agentmods.dev/badge/skills/hoavdc/codexkit/codexkit-go-to-market-planner.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.00079 | $0.01005 |
| Opus 5 | $0.00039 | $0.00502 |
| Sonnet 5 | $0.00016 | $0.00201 |
| Haiku 4.5 | $0.00008 | $0.00101 |
Grade A, and why
codexkit-go-to-market-planner 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.
How it starts
The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go-to-Market Planner
Purpose
Create a structured GTM plan that aligns product, marketing, sales, and customer success for a successful launch — from market analysis to day-one execution.
When to use
- launching a new product or service
- entering a new geographic market or customer segment
- repositioning an existing product
- preparing a major feature launch that needs cross-functional coordination
When not to use
- ongoing campaign management (use campaign-brief-writer)
- brand identity or visual design work
- daily marketing operations
Inputs
- product or feature description and key differentiators
- target audience (existing segment or new)
- competitive landscape overview
- launch timeline or constraints
- available budget and resources
- sales model (self-serve, sales-led, product-led, hybrid)
- geographic scope
Procedure
- Market sizing — TAM/SAM/SOM analysis:
- TAM: total market value if 100% penetration
- SAM: segment the company can realistically serve
- SOM: the achievable share in 12–18 months
- Competitive positioning:
- map competitors on a 2×2 matrix (e.g., ease-of-use vs. feature completeness)
- identify your unique positioning angle
- write a positioning statement: "For [target], we are the [category] that [differentiator] unlike [alternative]"
- Messaging framework:
- headline value proposition (one sentence)
- 3 supporting pillars (feature → benefit → evidence)
- objection handling for top 5 buyer concerns
- Channel strategy (prioritize 3–4 channels):
- rank by expected ROI and lead quality
- include content, paid, partnerships, community, product-led
- Pricing approach:
- value-based or competitive pricing rationale
- packaging tiers if applicable
- free trial or freemium consideration
- Launch timeline with milestones:
- T-30: pre-launch (beta, waitlist, press outreach)
- T-0: launch day (announcement, activation campaigns)
- T+30: post-launch (analysis, iteration, feedback loop)
- Success metrics and review cadence:
- leading indicators (sign-ups, trials, pipeline)
- lagging indicators (revenue, retention, NPS)
- review: weekly for first 30 days, then monthly
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 115 lines · 79 tokens per session scan A d18ee686ab1e
codexkit-go-to-market-planner is a skill published in the GitHub repository hoavdc/CodexKit (21 stars, last pushed 3mo ago), licensed MIT. It adds 79 tokens to every session and 1,005 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-30.
Other skills, from other repositories
knowledge_base
Manage the user's personal knowledge base — knowledge graph, documents, and wiki vault.
reducing-aigc-detection
A rewriting workflow for lowering the likelihood that academic writing is labelled as AI-generated by detection services, while keeping formatting and footnotes.
defending-applications
Application security defense knowledge for builders. Covers Web/API/GraphQL hardening (XSS/SQLi/SSRF/IDOR/BOLA/Mass Assignment/deserialization/upload/path traversal), authentication/authorization (OAuth 2.0/OIDC/JWT/Session/Cookie/SAML/SSO), and LLM application security (prompt injection, jailbreak, RAG poisoning…
analyzing-security
Scans code for security vulnerabilities, detects dangerous patterns, and ensures security decisions are documented. Use when running security scans, auditing code, or checking for OWASP issues, injection risks, or sensitive data leaks. Automatically triggered on new modules, security-related changes, or post-refactor.
architecting-security
A security-architecture guide for modeling threats and designing identity, access, privacy, and compliance controls. It covers approaches such as STRIDE, zero trust, single sign-on, multi-factor authentication, and GDPR-related privacy work.
building-agent-systems
AI agent and LLM system engineering reference covering single-agent dev (ReAct, tool calling, plan-execute), multi-agent coordination (swarm, role decomposition, file locking), LLM security (prompt injection, jailbreak defense, output filtering), RAG architecture (chunking, hybrid retrieval, rerank), and prompt…