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/techwolf-ai/ai-first-toolkit/setup-content-studionpx skills add techwolf-ai/ai-first-toolkit --skill setup-content-studiogit clone --depth 1 https://github.com/techwolf-ai/ai-first-toolkitWrote 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/techwolf-ai/ai-first-toolkit/setup-content-studio)<a href="https://agentmods.dev/skills/techwolf-ai/ai-first-toolkit/setup-content-studio"><img src="https://agentmods.dev/badge/skills/techwolf-ai/ai-first-toolkit/setup-content-studio.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.00049 | $0.01248 |
| Opus 5 | $0.00024 | $0.00624 |
| Sonnet 5 | $0.00010 | $0.00250 |
| Haiku 4.5 | $0.00005 | $0.00125 |
Grade A, and why
setup-content-studio 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Set Up Content Studio for a New Person
You are helping set up a thought leadership content studio for a new person, using the content-studio plugin as the template.
Overview
This is an interactive, multi-step process:
- Gather information about the person
- Research them online
- Ask clarifying questions about content preferences
- Create and configure the new repo
- Populate with their existing content
- Push to remote
Step 1: Gather Basic Information
Ask the user for:
- Person's full name
- Git repo URL for the new content studio (or ask where to create it)
- LinkedIn profile URL (if available)
- Their professional context (role, company, industry)
Step 2: Collect Example Posts
Ask the user to provide example content. This is critical for voice/style analysis:
"Please share 15-30 example posts from this person. You can provide them as:
- A text dump of their LinkedIn posts (with engagement numbers if available)
- URLs to their LinkedIn posts
- A document with collected posts
The more examples, the better I can capture their voice. Include engagement metrics (reactions, comments, reposts) if you have them - this helps identify what resonates with their audience."
Do not proceed until you have at least 10 substantive example posts. Shares/reposts with minimal commentary don't count. Unless the person does not have at least 10 posts.
Step 3: Research the Person Online
Use WebSearch to find:
- Their professional background and bio (company website, conference bios)
- Education and career history
- Speaking engagements, podcasts, publications
- Areas of expertise and thought leadership topics
- Any published articles or blog posts
Combine the online research with what you learn from their example posts.
Step 4: Analyze Their Voice and Style
Read references/voice-analysis.md for the full analysis framework covering writing style, content themes, and engagement patterns.
Step 5: Ask Clarifying Questions
What ships with it
3 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.
- 4d ago First seen · 138 lines · 49 tokens per session scan A 1ed0f0e5106b
setup-content-studio is a skill published in the GitHub repository techwolf-ai/ai-first-toolkit (96 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 1,248 once invoked, about $0.0002 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
media-search
Find and play music/videos via youtubesearch + openurl.
architecture-diagram
Architecture and component diagrams as HTML/SVG (dark-themed).
p5js
Generative visual art and sketches in p5.js (self-contained HTML).
songsee
Visualize audio as mel spectrograms, chromagrams, MFCC (librosa).
stable-diffusion-image-generation
Generate images via Stable Diffusion (HuggingFace Diffusers, local/API).
ascii-art
ASCII text banners and box art (pyfiglet, cowsay, boxes).