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/vstorm-co/content-skills/content-setupnpx skills add vstorm-co/content-skills --skill content-setupgit clone --depth 1 https://github.com/vstorm-co/content-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/vstorm-co/content-skills/content-setup)<a href="https://agentmods.dev/skills/vstorm-co/content-skills/content-setup"><img src="https://agentmods.dev/badge/skills/vstorm-co/content-skills/content-setup.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.00062 | $0.01862 |
| Opus 5 | $0.00031 | $0.00931 |
| Sonnet 5 | $0.00012 | $0.00372 |
| Haiku 4.5 | $0.00006 | $0.00186 |
Grade A, and why
content-setup 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 6d 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 — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Setup Skill
When This Skill Activates
This skill runs in three scenarios:
- Explicit invocation: user runs
/content setup,/content brand show,/content brand update, or/content voice. - Missing brand detection: any other content skill (e.g.,
/content draft,/content social) checks for thebrand/directory and it does not exist. That skill should hand off here before proceeding. - Voice recalibration: user drops writing samples into
brand/voice-samples/and runs/content voiceto re-derive voice attributes.
Command Routing
| Command | Behavior |
|---|---|
/content setup |
Full onboarding flow (all 5 phases) |
/content brand show |
Display current brand configuration from brand/BRAND.md, brand/VOICE.md, brand/VISUAL.md |
/content brand update |
Interactive modification of existing brand files |
/content voice |
Analyze writing samples in brand/voice-samples/ and update brand/VOICE.md |
The Onboarding Philosophy
This is a conversation, not a form. Claude should:
- Ask one question at a time (sometimes two if they are tightly related).
- Listen to the answer, then probe deeper when the response is vague or generic.
- Challenge cliches. If the user says "we empower people," ask what that looks like on a Tuesday afternoon.
- Reflect back what you heard before moving to the next phase, so the user can correct misunderstandings early.
- Keep a running internal summary; do not ask the user to repeat themselves.
- Be warm but direct. This process should feel like working with a sharp brand strategist, not filling out a government form.
Never dump all questions at once. The flow is adaptive -- skip questions whose answers are already obvious from prior responses. Add follow-ups when something interesting surfaces.
Phase 1: Identity (5-7 questions)
Goal: Understand who this brand is at its core.
Key topics:
- Brand or company name
- What you actually do (product/service/mission)
- Who you serve (audience -- push for specifics)
- The elevator pitch (30 seconds or less)
- Competitors and how you differ from them
- The single biggest differentiator
- One-word brand essence
What ships with it
9 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.
- 6d ago First seen · 207 lines · 62 tokens per session scan A e00fecb16035
content-setup is a skill published in the GitHub repository vstorm-co/content-skills (22 stars, last pushed 4mo ago), licensed MIT. It adds 62 tokens to every session and 1,862 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-30.
Other skills, from other repositories
frame-logo-outro
Segmented logo assembly, glow bloom, and tagline reveal for video outros or brand closing frames.
steadyagent-workflow
Local-first Codex workflow for planning, debugging, reviewing, refactoring, improving AGENTS.md, building skills, publishing agent harness repositories, or running complex multi-step coding tasks that need staged diagnosis, context control, verification loops, review strategy, release evidence, and…
ackit-workflow
Enforce the ACKit docs-first, task-first workflow with one active checklist item and evidence-based completion.
ackit-context-optimization
Build budgeted context packs and trim instruction bloat for coding agents.
ackit-policy-authoring
Author layered ackit policy files with deterministic merge, scoping and lockable rules.
ackit-scan-and-fix
Run ACKit scan, interpret findings by severity, and apply safe fixes with suppression hygiene.