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 stefanoskarakasis/Product-Marketing-Skills --skill market-contextgit clone --depth 1 https://github.com/stefanoskarakasis/Product-Marketing-SkillsWrote 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/stefanoskarakasis/product-marketing-skills/market-context)<a href="https://agentmods.dev/skills/stefanoskarakasis/product-marketing-skills/market-context"><img src="https://agentmods.dev/badge/skills/stefanoskarakasis/product-marketing-skills/market-context/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/stefanoskarakasis/product-marketing-skills/market-context"><img src="https://agentmods.dev/badge/skills/stefanoskarakasis/product-marketing-skills/market-context.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.00088 | $0.02540 |
| Opus 5.5 | $0.00035 | $0.01016 |
| Sonnet 5.5 | $0.00018 | $0.00508 |
| Haiku 4.5 | $0.00009 | $0.00254 |
Grade A, and why
market-context 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 11d 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 — 282 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Market Context
How This Works
Positioning says what you are. Alternatives say what you beat. Market context says why the world needed you right now — the layer that makes a narrative land as inevitable instead of opportunistic. This skill builds that narrative from macro forces and buying triggers, then deepens your brain's existing Section 5 in place rather than creating a second market file — one source of truth stays intact for every downstream skill.
Step 0 — Load brain Section 5 (current market context, however thin),
Section 3 (alternatives, for narrative grounding), and any guardrails from
/context/meta-patterns.md.
Step 1 — Establish category and maturity: what category the product competes in (existing, emerging, or being created), and where that category sits on the adoption curve.
Step 2 — Surface macro forces and buying triggers: what external
shifts (regulatory, technological, economic, cultural) create demand for
this category right now, and what specific event moves a buyer from
passive awareness to active evaluation. Every force and trigger tagged
[CONFIRMED] / [INFERRED] / [HYPOTHESIS].
Step 3 — Build and stress-test the narrative arc: the single sentence connecting macro force → buyer consequence → why the old approach breaks → why now. Run the specificity and buyer-connection checks before it ships.
Step 4 — Deepen brain Section 5 with the narrative (on user confirmation).
Step 5 — Learning Close: log the session to /context/skill-sessions.md.
Trigger
-
When: Defining or sharpening the market narrative — why this category, why this moment, what forces make the solution feel inevitable rather than opportunistic.
-
Not for: Positioning statement or messaging hierarchy itself → use
positioning-messaging. Competitive alternatives mapping → that's brain Section 3, handled withinproduct-marketing-contextor this skill's own Step 0 load, not rebuilt here. Full ICP or buying-committee work →ideal-customer-profileorbuyer-personas.
What ships with it
1 file 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.
- 11d ago Changed · -1 lines · -3 tokens per session 4fab278b4e2f
- 19d ago Changed c3ea0deb17c8
- 20d ago Changed 51f6a8d7e1c6
- 24d ago Changed 2e030f422675
- 26d ago Changed · +13 lines bbbbbba8317a
- 1mo ago Changed · +2 lines 8feba0a677a9
- 1mo ago First seen · 268 lines · 91 tokens per session scan A 496dfd76f7d3
market-context is a skill published in the GitHub repository stefanoskarakasis/Product-Marketing-Skills (8 stars, last pushed 3d ago), licensed MIT. It adds 88 tokens to every session and 2,540 once invoked, about $0.0004 per session on Opus 5.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-09-04.
Other skills, from other repositories
report
A way to export a chat card or reply as a standalone HTML report, meaning a file that can open in a browser without the chat application. It preserves the card template, including right-to-left Persian or left-to-right English layouts.
k8s-rightsize
Right-size Kubernetes CPU and memory requests from Prometheus usage (p95 CPU, p98 memory over 7 days), size the node count, tune KEDA autoscaling. Use when asked to rightsize workloads, cut node cost, or "how many nodes do we need".
owasp-security
Deep OWASP reference: Top 10 2025, ASVS 5.0, secure patterns, per-language quirks, LLM Top 10 and agentic AI security. Use for an in-depth security review, auth work, or hardening an LLM or agent app. For the everyday baseline use secure-coding.
fig
One self-contained HTML file holding a looping animated SVG, for ideas that move: flows, loops, retries, queues, fan-outs. Use when the user says "fig" or a diagram would be better animated.
brand
A project-specific visual identity for chat cards and saved reports, using the project's colors, logo, and fonts. It finds these details in the repository or asks the user for them, then stores the result in a committable `.readable/` folder.
workspace-rules
A set of guidelines for deciding which rules belong in a repository's workspace instructions and which should be enforced by its build or checks.