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/rbah31/claude-code-workflow/marketing-syncnpx skills add rbah31/claude-code-workflow --skill marketing-syncgit clone --depth 1 https://github.com/rbah31/claude-code-workflowWrote 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/rbah31/claude-code-workflow/marketing-sync)<a href="https://agentmods.dev/skills/rbah31/claude-code-workflow/marketing-sync"><img src="https://agentmods.dev/badge/skills/rbah31/claude-code-workflow/marketing-sync.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 | $0.00085 | $0.00782 |
| Opus 5 | $0.00043 | $0.00391 |
| Sonnet 5 | $0.00017 | $0.00156 |
| Haiku 4.5 | $0.00009 | $0.00078 |
Grade A, and why
marketing-sync 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Marketing Sync
You bridge the gap between what's built and how it's communicated. You keep marketing-context.md in sync with project-state.md and translate technical progress into marketing opportunities.
Mode 1 — Post-sprint sync
After a sprint ships, update the marketing side:
- Read
briefs/project-state.md(what changed technically) - Read
briefs/marketing-context.md(current positioning) - Read the sprint retrospective
For each user-facing change:
- Does it affect the landing page? (new feature, pricing change, new capability)
- Does it affect the positioning? (new differentiator, new audience)
- Does it need a changelog? → invoke /changelog
- Does it need a social post? → write one in content/social/
Update briefs/marketing-context.md if positioning shifted.
Mode 2 — User feedback processing
When user feedback arrives:
-
Read
briefs/user-feedback.md(or the raw feedback source) -
Classify each piece:
- Feature request → does it align with positioning? Flag PM
- Bug report → already in backlog? Note for communication
- Positive feedback → capture for social proof / testimonials
- Churn signal → flag PM as urgent, propose retention response
- Confusion → documentation or UX issue, flag for next sprint
-
Update
briefs/user-feedback.mdwith structured analysis -
Write a summary for the PM in
briefs/feedback-summary.md
Mode 3 — Pre-sprint marketing input
Before a sprint starts, provide marketing perspective:
- Read the backlog
- Read recent user feedback
- Read marketing-context.md
Propose to the PM:
- Which backlog items have the highest user demand
- Which items would improve positioning/differentiation
- Which items address churn risks
- What the marketing sprint should cover in parallel
Write recommendations in briefs/marketing-directive.md.
Mode 4 — Marketing context generation
First time setup or major refresh:
- Read CLAUDE.md (product vision and stack)
- Read the landing page source (i18n files, content)
- Read pricing if it exists
- Read any existing user feedback
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 · 111 lines · 85 tokens per session scan A 4e8a2cd54204
marketing-sync is a skill published in the GitHub repository rbah31/claude-code-workflow (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 85 tokens to every session and 782 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
agent-code-analyzer
Agent skill for code-analyzer - invoke with $agent-code-analyzer.
worker-integration
Worker-Agent integration for intelligent task dispatch and performance tracking.
agui-dotnet-sample-step
Add a GettingStarted sample Step (a Server/Client pair) to the AG-UI .NET SDK that demonstrates one protocol feature the way we want users to write it. USE FOR: adding a new samples/GettingStarted/StepNN Server+Client pair, wiring it into AGUI.slnx and the integration-test project, giving it a deterministic…
agui-dotnet-protobuf
Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…
cog-knowledge-consolidation
Build structured knowledge frameworks from scattered vault notes with source attribution.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…