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 agentmods add skills/nocodework/growth-os/contextnpx skills add nocodework/growth-os --skill contextgit clone --depth 1 https://github.com/nocodework/growth-osWrote 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/nocodework/growth-os/context)<a href="https://agentmods.dev/skills/nocodework/growth-os/context"><img src="https://agentmods.dev/badge/skills/nocodework/growth-os/context.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.00104 | $0.01192 |
| Opus 5 | $0.00052 | $0.00596 |
| Sonnet 5 | $0.00021 | $0.00238 |
| Haiku 4.5 | $0.00010 | $0.00119 |
Grade A, and why
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 5d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
context
Every other Growth OS skill reads one file: .agents/product-marketing.md. context is the skill that creates and maintains it. Get this right and the audit, GEO work, and any delegated marketing task all speak in the business's actual language instead of guessing.
What it does
Turns a URL and a short interview into a durable, structured positioning document:
- USP — what makes this business different, in one sentence.
- UVP — the value promise to the customer (outcome, not features).
- ICP — who it's for: segment, role, company shape, the pain that sends them looking.
- Positioning — category, main alternatives, the wedge.
- Voice & proof — tone, words to use and avoid, credible proof points (numbers, names, guarantees).
It writes this to .agents/product-marketing.md in the project root and keeps it current across sessions.
When to use
- Before any other Growth OS growth work, on a fresh project.
- When positioning shifts — new segment, new pricing, a pivot, a rebrand.
- When the audit or a delegated skill produces a vague result and the root cause is thin context.
Inputs
- A business URL (strongly preferred — it's the pre-fill source).
- Whatever the user already knows about their audience. If they know a lot, the interview is a confirmation. If they know little, it's discovery.
Steps
-
Read the URL. Pull the homepage and one or two key pages (pricing, product, about). Extract a first draft of USP/UVP/ICP and voice from what's actually on the site. This draft is a starting point, not the answer.
-
Present the pre-fill for confirmation. Show the user what you inferred, section by section, in plain language: "Here's what your site says you do and who it's for — is this right?" People correct a draft far faster than they fill a blank form. Never treat the inference as final; it's a prompt for correction.
-
Interview in small batches. Ask 3–5 questions at a time, never a wall of twenty. Group by theme:
- Batch 1 — the customer: who buys, what job they're hiring the product for, what they'd Google at 2am.
- Batch 2 — the difference: why they pick you over the obvious alternative, what you refuse to be.
- Batch 3 — proof and voice: hard numbers, named customers, guarantees; the tone and the words to avoid. Wait for answers before the next batch. Stop early if the picture is already complete — don't pad.
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.
- 5d ago First seen · 99 lines · 104 tokens per session scan A 251ddd121f48
context is a skill published in the GitHub repository nocodework/growth-os (6 stars, last pushed 2mo ago), licensed MIT. It adds 104 tokens to every session and 1,192 once invoked, about $0.0005 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
gtm-reverse-engineer
Reverse-engineer any company's public go-to-market into an evidence-graded, multi-file playbook (copy / adapt / skip). Use whenever the user wants competitor GTM teardown, growth forensics, channel analysis (Instagram, X/Twitter, LinkedIn, ads, Reddit/community, SEO, jobs, pricing), "how did X grow", unicorn/breakout…
cold-outbound-sequencer
Use when the user asks to "build a B2B cold-outbound sequence", "design reply-triage branching", "plan a domain warmup / sending throttle", or "make my outbound CAN-SPAM / opt-in compliant"; produces a multi-step outbound sequence with reply-triage branches (positive / objection / referral / not-now / opt-out), a…
inbox-placement-monitor
Use when the user asks to "track where my emails are actually landing after I send", "read my seed-list inbox vs spam vs promotions results", "trend my Gmail Postmaster / Microsoft SNDS reputation", or "did placement drop after my last send"; produces a per-provider inbox/spam/promotions placement read, a domain/IP…
email-render-builder
Use when the user asks to "build the email HTML", "make this email responsive", "fix dark-mode rendering", or "QA the email across clients"; produces the coded HTML build — a responsive table layout, dark-mode + accessibility pass, a client-render matrix, image-block fallbacks, and a plain-text parity check. Not for…
newsletter-monetization-planner
Use when the user asks to "monetize my newsletter", "build a sponsorship rate card", or "model paid-subscription revenue"; produces a revenue model (paid tiers, ad/sponsorship inventory + CPM/flat rate card, referral/boost loops), a list-growth ↔ revenue projection, and honest-offer / disclosure checks for the SEND-D…
audience-mapper
Use when the user asks to "analyze my target audience", "build an audience profile for influencer targeting", "research a niche community", or "deep-dive a subculture before partnering with creators"; in audience mode produces demographic/psychographic profiles, a platform-priority matrix, named personas, and an…