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 byheaven/byheaven-skills --skill content-creatorgit clone --depth 1 https://github.com/byheaven/byheaven-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/byheaven/byheaven-skills/content-creator)<a href="https://agentmods.dev/skills/byheaven/byheaven-skills/content-creator"><img src="https://agentmods.dev/badge/skills/byheaven/byheaven-skills/content-creator/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/byheaven/byheaven-skills/content-creator"><img src="https://agentmods.dev/badge/skills/byheaven/byheaven-skills/content-creator.svg" alt="Reviewed on agentmods" width="80" 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.00083 | $0.01140 |
| Opus 5.5 | $0.00033 | $0.00456 |
| Sonnet 5.5 | $0.00017 | $0.00228 |
| Haiku 4.5 | $0.00008 | $0.00114 |
Grade A, and why
content-creator 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 today.
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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Creator
Every writing task starts with a writing brief that the user approves, and the draft follows that brief. Style is chosen for each piece from its reader and purpose.
A writing task is text whose value lies in how a human reader receives it: product and interface copy, posts, articles, introductions, documents written to be read such as a Vision, principles, or a PRD, and messages sent on the user's behalf. Conversation replies, status updates, code, commit and PR text, instructions for agents (skills, rules, charters, directives), and documents that record facts for reference (decision records, product behavior documents, architecture, runbooks, reviews) are not writing tasks. The user's global instructions carry the same definition.
1. Writing brief
Show the user the brief before drafting or revising, and draft only after the user approves it. For Yu Bai's own posts, articles, and books, follow the next section instead of drafting. A Vision, other project documents, and product copy go through this brief and an agent draft even when he signs them.
- Author: who is speaking, as a specific person or voice (the AMIO team; the AMIO companion; Yu Bai as AMIO's founder in a Vision).
- Reader: one specific person in a specific moment, described by what they already know, what they care about, and what would convince them. A platform or a category ("players", "investors") is too broad.
- Purpose: what the piece should achieve, and what the reader takes away: the value (what they now know, can do, or can decide) and the feeling (how they feel about the subject and the author).
- Style: the style that best serves this reader and purpose (tone, register, rhythm, length, structure, how vivid or plain), with two or three concrete references that model it well: published works, writers, products, or pieces the user already approved, each with what to take from it.
Reuse what the project has settled, such as a product's brand voice, a document's agreed structure, or an approved brief for the same series, and name it in the brief. Done when the user approves the brief as written or as changed. One approved brief covers the task's drafts and revisions until its author, reader, or purpose changes.
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.
- today Changed · +10 lines 1aa987c07ff1
- 10d ago First seen · 43 lines · 83 tokens per session scan A c1a9b5d49f5c
content-creator is a skill published in the GitHub repository byheaven/byheaven-skills (2 stars, last pushed today), licensed MIT. It adds 83 tokens to every session and 1,140 once invoked, about $0.0003 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-10-08.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.