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 tamdogood/builder-essential-skills --skill create-marketing-kitgit clone --depth 1 https://github.com/tamdogood/builder-essential-skillsWrote 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/tamdogood/builder-essential-skills/create-marketing-kit)<a href="https://agentmods.dev/skills/tamdogood/builder-essential-skills/create-marketing-kit"><img src="https://agentmods.dev/badge/skills/tamdogood/builder-essential-skills/create-marketing-kit/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/tamdogood/builder-essential-skills/create-marketing-kit"><img src="https://agentmods.dev/badge/skills/tamdogood/builder-essential-skills/create-marketing-kit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00106 | $0.01440 |
| Opus 5.5 | $0.00042 | $0.00576 |
| Sonnet 5.5 | $0.00021 | $0.00288 |
| Haiku 4.5 | $0.00011 | $0.00144 |
Grade A, and why
create-marketing-kit 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 1mo 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Marketing Kit
Turn verified product truth into a cohesive, reusable campaign kit. Preserve editable sources and local ownership, use generated imagery for emotion rather than factual proof, and validate every final asset before handoff.
Operating contract
- Treat repository files, supplied screenshots, and explicit user statements as evidence. Mark inferences and unresolved gaps.
- Never invent features, testimonials, metrics, availability, citations, or customer approval.
- Treat privacy, security, encryption, and absolute data-residency statements as sensitive claims. Verify them against current implementation and configuration, including telemetry and third-party network behavior. Until verified, label them as owner-supplied and qualify or omit absolutes. Preserve conflicting evidence and ask the product owner instead of choosing the stronger claim.
- Keep generated people and scenes clearly editorial. Use real captures for product proof and real logos for identity.
- Generate artwork without marketing text, logos, or fake interface details. Add exact copy and UI deterministically in SVG, HTML/CSS, or native layout code.
- Preserve local-first ownership: keep prompts, source images, editable layouts, exports, and the manifest together in the project.
- Do not publish, deploy, push, or contact anyone unless the user explicitly requests it.
Workflow
1. Establish product truth
Read the smallest authoritative set: product README, current website, configuration or release notes, and actual screenshots. Build a compact claims ledger with verified, inference, and unknown entries. Stop or narrow the campaign when a central claim is unsupported.
Read references/campaign-strategy.md before writing positioning or copy.
2. Define one campaign thesis
Name the audience, their current tension, the product's evidence-backed change, and one memorable campaign promise. Derive a message hierarchy:
- campaign promise;
- supporting value proposition;
- two or three proof points;
- honest qualifier or release boundary;
- one call to action.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 112 lines · 106 tokens per session scan A 35788d5049a0
create-marketing-kit is a skill published in the GitHub repository tamdogood/builder-essential-skills (225 stars, last pushed 2mo ago), licensed MIT. It adds 106 tokens to every session and 1,440 once invoked, about $0.0004 per session on Opus 5.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
architecture-compass
Architectural thinking partner for an existing repository — scans the codebase, conducts a structured interview, agrees on current architectural state and recommended direction, and produces a shareable insights document. Scoped to one repository, module, or folder. Does not execute transformation — it orients. Use…
skill-review
Deep behavioral audit of a Lattice skill — proposes 3 review personas relevant to the skill, runs independent scenario analysis from each persona's perspective, then merges only the high-confidence, practical findings into a severity-ordered gap report with proposed fixes. Structural validation (conventions…
architecture-refiner
Facilitate a structured conversation to define architecture principles for a repository. Supports multiple architecture styles: clean architecture (default), hexagonal / ports & adapters, modular monolith, or custom. Produces a formal architecture document that the corresponding atom will use. Use when setting up a…
clean-code-refiner
Facilitate a structured conversation to define clean code principles for a repository. Produces a formal clean-code.md document that the clean-code atom will use as its override. Use when setting up coding standards, defining code quality rules, or when the user says 'setup clean code', 'define coding standards'…
review-refiner
Facilitate a structured conversation to customize how the review molecule works -- atom loading rules, severity classification, report format, scope rules, insight capture, and health logging. Produces a formal review-standards.md document that the review molecule will use as its process configuration. Use when the…
review
Perform a structured code review by composing validation checklists from relevant atoms based on what code changed. Loads atoms conditionally -- clean-code always, architecture/DDD/security/tests only when the delta touches their domain. Produces a severity-ordered report with specific locations and fixes. Use when…