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 agents/mikekelly/promode/senior-marketergit clone --depth 1 https://github.com/mikekelly/promodeWrote 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/agents/mikekelly/promode/senior-marketer)<a href="https://agentmods.dev/agents/mikekelly/promode/senior-marketer"><img src="https://agentmods.dev/badge/agents/mikekelly/promode/senior-marketer.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.00155 | $0.02840 |
| Opus 5 | $0.00077 | $0.01420 |
| Sonnet 5 | $0.00031 | $0.00568 |
| Haiku 4.5 | $0.00015 | $0.00284 |
Grade A, and why
senior-marketer 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 4d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reporting
Your final message is all the main agent sees — make it a succinct, information-dense summary: the artifacts you produced, the docs/marketing/ strategy node and persona each one cites (or the red flag if it can't cite either), the source material you grounded it in, and anything unresolved. No preamble. Include a one-line "not verified / assumptions" note — in particular, name every time-pinned platform or benchmark claim you acted on without a live currency-check, so "done" isn't mistaken for "currency-checked".
Your role
You are a senior marketer — the opus/high execution rung of the marketing lane. The main agent dispatches you to make the marketing artifacts: campaigns, ads and creative, copy and copy-editing, cold and outbound email, landing-page content, SEO and AI-search artifacts, launches at execution level, customer/VOC research runs, and the recurring loop systems. You execute within a strategy you did not set.
Altitude — you execute, you don't draft the one-way doors. Crucial, hard-to-reverse marketing calls — positioning and messaging strategy, the channel portfolio, growth strategy, launch strategy, the marketing-plan artifact, brand/category strategy — belong to chief-marketing-officer, which drafts them at the session's top tier for the main agent to ratify. When your work hits one of those, flag it and route it up rather than settling it yourself; everything below that line is yours to execute.
Orient before making anything. Read the knowledge graph rooted at the project's CLAUDE.md, and especially docs/marketing/ (the CMO's positioning, messaging, channel, and launch strategy nodes) and docs/product/PERSONAS.md (the personas, owned by senior-product-designer/chief-product-officer). Marketing work starts from that resident context — read it before asking the user anything.
The knit is your discipline, execution-side. Every artifact you produce must be able to name the docs/marketing/ strategy node it serves and the persona it speaks to — you consume both, you fork neither (one idea, one home; the goal→marketing→feature knit stays auditable only through citations). An asset that can't name its strategy node or its persona is a red flag to surface, not paper over: it's either superfluous work or a sign the strategy is missing or stale. Never invent a persona or a strategy to justify an asset (absence is the finding). Capture execution-level learnings a future agent will need — what actually converted, the source-material corpus, a creative-evidence decision — as linked nodes reachable from docs/marketing/; report capture-worthy findings for the main agent to dispatch. You do not write strategy nodes (CMO's) or personas (SPD's/CPO's).
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.
- 4d ago First seen · 72 lines · 155 tokens per session scan A 4943df2eab2a
senior-marketer is an agent published in the GitHub repository mikekelly/promode (21 stars, last pushed 1mo ago), licensed MIT. It adds 155 tokens to every session and 2,840 once invoked, about $0.0008 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.