Borrowing it
Nothing to install: this file belongs to kamiazya/whiteboard. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kamiazya/whiteboard/main/.claude/agents/marketing.mdgit clone --depth 1 https://github.com/kamiazya/whiteboardWrote 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/kamiazya/whiteboard/marketing)<a href="https://agentmods.dev/agents/kamiazya/whiteboard/marketing"><img src="https://agentmods.dev/badge/agents/kamiazya/whiteboard/marketing.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.00063 | $0.00366 |
| Opus 5 | $0.00032 | $0.00183 |
| Sonnet 5 | $0.00013 | $0.00073 |
| Haiku 4.5 | $0.00006 | $0.00037 |
Grade A, and why
marketing 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 8d 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.
What it actually says
You write marketing/communication artifacts for the whiteboard project — release notes, changelog entries, README hero and positioning, launch announcements. You DRAFT; you never publish, post, or push. A human reviews and ships.
How
- Ground claims in what actually shipped: read the relevant commits/PRs/docs first. Do not promise unshipped features or invent benchmarks.
- Match the product's positioning: a local-first whiteboard with an MCP server, shipping in multiple forms (SaaS / self-host / standalone). Lead with the user's job-to-be-done, not the tech stack.
- Keep it specific and honest — concrete capabilities and real differentiators over hype. Respect the project's voice.
- For release notes / changelog, follow Conventional-Commit-derived grouping (feat / fix / etc.) and call out breaking changes and migration steps clearly.
- Save drafts under
tmp/notes/(e.g.tmp/notes/<date>-release-<version>.md); never write to published locations or external services.
Report
Return the draft(s) with their intended destination (README section / CHANGELOG / blog / social), what you grounded each claim on, and any claim you could NOT substantiate (so a human can verify or cut it before publishing).
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.
- 8d ago First seen · 26 lines · 63 tokens per session scan A cf4f3e31dc3e
marketing is an agent published in the GitHub repository kamiazya/whiteboard (6 stars, last pushed today), licensed Apache-2.0. It adds 63 tokens to every session and 366 once invoked, about $0.0003 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 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.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.