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 danielpaulai/Purely-Personal-Run-a-business-by-itself --skill content-strategygit clone --depth 1 https://github.com/danielpaulai/Purely-Personal-Run-a-business-by-itselfWrote 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/danielpaulai/purely-personal-run-a-business-by-itself/content-strategy)<a href="https://agentmods.dev/skills/danielpaulai/purely-personal-run-a-business-by-itself/content-strategy"><img src="https://agentmods.dev/badge/skills/danielpaulai/purely-personal-run-a-business-by-itself/content-strategy/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/danielpaulai/purely-personal-run-a-business-by-itself/content-strategy"><img src="https://agentmods.dev/badge/skills/danielpaulai/purely-personal-run-a-business-by-itself/content-strategy.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.00158 | $0.05744 |
| Opus 5 | $0.00079 | $0.02872 |
| Sonnet 5 | $0.00032 | $0.01149 |
| Haiku 4.5 | $0.00016 | $0.00574 |
Grade A, and why
content-strategy 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 12d 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 — 454 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Strategy — Purely Personal
by Daniel Paul · Purely Personal
Read ALL reference files before running research or writing:
/references/voice-dna.md— Daniel's ICP snapshot, what good positioning looks like/references/human-writing-standards.md— what world-class content looks like/references/copywriting-frameworks.md— how to think about content intent and structure/references/design-system.md— brand tokens for the strategy header and the Step 9 visual/references/creator-systems.md— the five content systems behind the biggest solo creators: the topic-by-format grid, the four content angles, the pillar-to-micro cascade, the depth-niche test, and 2026 cadence data. Steps 5 and 7 depend on it./references/visual-standards.md· environment detection, the HTML+GSAP stack, motion and design rules, the Strategy document shape, and the visual quality gate. Step 9 depends on it.
WHERE THIS SKILL SITS
Reads from: BUSINESS-BRAIN.md · the client's intake answers and live research Hands off to: the weekly operating rhythm (Step 7): newsletter-writer for the weekly pillar piece · linkedin-carousel-builder and linkedin-cheatsheet-builder for the visual cuts · linkedin-caption-writer for the daily topics, one at a time Tell the user the next step in one line after delivering.
One job: a strategy so specific and grounded in the client's real niche that they read the pillars and think "this is exactly what I've been trying to say — just clearer than I could say it."
The standard for every pillar: Generic pillar names are noise. "Thought leadership" is not a content pillar. "LinkedIn tips" is not a content pillar. "Personal brand growth" is not a content pillar.
A content pillar is a specific claim, audience problem, or angle that only this client can own in this niche right now. It should make competitors uncomfortable.
STEP 0 — CONTEXT CHECK (always first, never skipped)
Look for the participant's context, in this priority order:
- BUSINESS-BRAIN.md in Project Knowledge or attached to the chat — the single source of truth. If present, its Voice DNA, ICP, offer, proof, sign-off, and design tokens OVERRIDE every default in this skill's references folder.
- If no brain: individual foundation documents (Voice DNA, ICP, Brand Positioning, Messaging House, Rule of 1, Business in a Box) — use them the same way.
- If neither: use the bundled references (Daniel Paul's defaults) and label the output header:
DEFAULT VOICE — personalize by adding your BUSINESS-BRAIN.md to this project.
What ships with it
12 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.
- references/about-frameworks.md 6.0 KB
- references/ai-pattern-blacklist.md 7.0 KB
- references/copywriting-frameworks.md 12 KB
- references/creator-systems.md 11 KB
- references/design-system.md 3.8 KB
- references/execution-playbooks.md 18 KB
- references/headline-frameworks.md 4.6 KB
- references/html-output-templates.md 65 KB
- references/human-writing-standards.md 3.6 KB
- references/post-writing-variations.md 10 KB
- references/visual-standards.md 7.7 KB
- references/voice-dna.md 4.8 KB
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.
- 12d ago First seen · 454 lines · 158 tokens per session scan A 72bfb31bdf26
content-strategy is a skill published in the GitHub repository danielpaulai/Purely-Personal-Run-a-business-by-itself (2 stars, last pushed 29d ago), licensed MIT. It adds 158 tokens to every session and 5,744 once invoked, about $0.0008 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.
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…