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 etrebels/claude-code-growth-os --skill marketing-feedbackgit clone --depth 1 https://github.com/etrebels/claude-code-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/etrebels/claude-code-growth-os/marketing-feedback)<a href="https://agentmods.dev/skills/etrebels/claude-code-growth-os/marketing-feedback"><img src="https://agentmods.dev/badge/skills/etrebels/claude-code-growth-os/marketing-feedback/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/etrebels/claude-code-growth-os/marketing-feedback"><img src="https://agentmods.dev/badge/skills/etrebels/claude-code-growth-os/marketing-feedback.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.00071 | $0.00594 |
| Opus 5 | $0.00036 | $0.00297 |
| Sonnet 5 | $0.00014 | $0.00119 |
| Haiku 4.5 | $0.00007 | $0.00059 |
Grade A, and why
marketing-feedback 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 9d 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 — 33 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Marketing Feedback
The loop that keeps sales and marketing as one system: field intelligence flows from sales back to marketing on a cadence, instead of dying inside a meeting note. This is mechanism #5 from docs/why-align.md — made concrete as a tagged line in a shared log.
From a source — a note in ops/daily-log.md, a file in demo/meetings/, a call recap, a deal update:
Tagged lines live in one place:
ops/feedback-log.md. That's the single home the SessionStart hook surfaces and/weekly-reviewclears — writeMARKETING-ACTIONlines there, not in the daily log, so they don't go invisible.
- Scan for the five signal types:
- Recurring objection — the same pushback in 3+ conversations.
- Competitor mention — who showed up, and how the buyer described them.
- Buyer language — the words they actually used (use them in content; don't translate them into your own).
- Missing proof — evidence they asked for that doesn't exist yet.
- Win/loss reason — the real one, not the polite one.
- Log each as a tagged line in
ops/feedback-log.md, so marketing can act on it without a meeting:MARKETING-ACTION: [signal] — [the content or proof that would answer it]MARKETING-ACTION-URGENT:when a live deal was affected.MARKETING-STRATEGIC:when it signals a positioning or new-segment shift.
- Don't invent signals. One offhand comment isn't a pattern — tag it only when it recurs across deals or clearly cost one. A log full of false patterns is worse than an empty one.
The tag is the hand-off. One file, both functions read it — that's the loop, version-controlled, with a diff and a history. Marketing's job is to clear the MARKETING-ACTION lines; sales' job is to keep them honest and current.
Depth
- quick: scan one note, emit any
MARKETING-ACTIONlines. - standard: the full five-signal scan across recent notes, tagged and ranked by urgency.
- deep: + a one-line content brief for the top signal (who it's for, the claim to make, the proof to find).
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.
- 9d ago First seen · 33 lines · 71 tokens per session scan A e7df4f44af32
marketing-feedback is a skill published in the GitHub repository etrebels/claude-code-growth-os (20 stars, last pushed 3d ago), licensed MIT. It adds 71 tokens to every session and 594 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
startup-launch-playbook
A step-by-step playbook for early-stage startups going from pre-seed to their first 1000 users. Covers MVP validation, initial traction channels, and founder-led growth tactics. By @WeiYipei — follow on X for more startup growth insights.
a-b-testing
Design statistically sound GTM experiments for copy, channels, landing pages, sequencing, pricing, and funnel conversion. Produces hypothesis, sample-size logic, success metrics, test plan, analysis method, and scale/stop/kill recommendation. Use when planning A/B tests, split tests, or experiment roadmaps.
attribution
Build practical B2B attribution models across first touch, lead creation, opportunity creation, multi-touch, account-based influence, and sales-sourced revenue. Produces model comparison, UTM governance, source-of-truth rules, and channel ROI view. Use when marketing and sales disagree on source or ROI.
campaign-analytics
Analyze campaign performance from deliverability through revenue: delivery, engagement, replies, meetings, SQOs, pipeline, CAC, and payback. Produces diagnostic scorecard, root-cause analysis, benchmark comparison, and next-action plan. Use when deciding whether to scale, fix, or kill campaigns.
deliverability-monitoring
Monitor outbound deliverability health across domains, inboxes, DNS, bounces, spam placement, reply rates, and reputation signals. Produces alert thresholds, dashboard spec, weekly QA checklist, and remediation playbook. Use when inboxing drops, bounce rates rise, campaigns underperform, or new infrastructure launches.
gtm-metrics
Build a GTM metrics system for SaaS: funnel conversion, pipeline velocity, win rates, CAC, payback, NRR, sales efficiency, growth accounting, and executive dashboards. Use when creating metrics dashboards, board reports, revenue reviews, operating cadence, or diagnosing growth constraints.