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/adologyai/content-intelligence-plugin/creative-toolkitnpx skills add adologyai/content-intelligence-plugin --skill creative-toolkitgit clone --depth 1 https://github.com/adologyai/content-intelligence-pluginWrote 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/adologyai/content-intelligence-plugin/creative-toolkit)<a href="https://agentmods.dev/skills/adologyai/content-intelligence-plugin/creative-toolkit"><img src="https://agentmods.dev/badge/skills/adologyai/content-intelligence-plugin/creative-toolkit.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.00191 | $0.03727 |
| Opus 5 | $0.00096 | $0.01863 |
| Sonnet 5 | $0.00038 | $0.00745 |
| Haiku 4.5 | $0.00019 | $0.00373 |
Grade A, and why
creative-toolkit 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 3d 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 — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creative Toolkit Builder
You produce a creative toolkit — a working library a creative team opens and starts producing from immediately. The toolkit has two files: a CSV (100-150+ rows) and a companion HTML browser.
The Output: 9 Sections Across Two Files
Every toolkit contains exactly these 9 sections. This is the structure of both the CSV and the HTML. Each section serves a different person on the creative team.
Section 1: Voice DNA Card (8-10 items)
The brand's extracted voice profile — archetype, voice attributes with "NOT" contrasts, 8 tone dimension positions, sounds-like / doesn't-sound-like examples. This is the taste reference the team holds everything against.
Section 2: Hook Bank (25-30 hooks)
Verbatim opening lines organized by psychological mechanism: Curiosity Gap, Contrarian Premise, Pain Point Mirror, Social Proof, Urgency/Scarcity, Identity. Each hook is the actual words a creator would say or a caption would start with. "Your morning bar has 14g of sugar. Ours has 2." — that's a hook. "Use a curiosity gap hook" — that's a description, not a hook. Every item in this section is ready to use as-is.
Section 3: Angle Library (10-15 angles)
Strategic content framings with 2-3 sentence briefs. Each tells the creative team: what the framing is, who it targets, and the data that proves it works.
Section 4: Copy Bank (50+ lines)
Ready-to-use copy organized by where it goes: Caption Openers, Text Overlays, CTAs, Comment Replies, One-Liners. Volume matters — 50 minimum, ideally 60-80. Mix of short punchy, medium, and longer narrative lines. Every line contains at least one specific detail (a number, a time, a name, a sensory detail).
Section 5: Tagline Options (10-15 phrases)
Memorable phrases the brand could own, across registers: Bold, Playful, Authoritative, Minimal. Each passes the swap test — if you could put a competitor's name on it, it's not specific enough.
Section 6: Concept Briefs (5-8 concepts)
Full creative concepts a team could brief from. Each includes: concept name, format, hook approach, beat-by-beat structure, platform, production notes, data proof, inspiration source.
What ships with it
6 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.
- 3d ago First seen · 298 lines · 191 tokens per session scan A 855c7c68a025
creative-toolkit is a skill published in the GitHub repository adologyai/content-intelligence-plugin (2 stars, last pushed 29d ago), licensed Apache-2.0. It adds 191 tokens to every session and 3,727 once invoked, about $0.0010 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…