PM Skills is a collection of plain-Markdown instructions that teach AI assistants structured methods for handling professional, personal, and life-admin tasks. People use it with Claude, ChatGPT, Gemini, Cursor, Codex, and other supported agents for work such as writing product requirements, reviewing documents, or planning difficult situations.
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 mohitagw15856/pm-claude-skills --skill creator-brand-kitgit clone --depth 1 https://github.com/mohitagw15856/pm-claude-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/mohitagw15856/pm-claude-skills/creator-brand-kit)<a href="https://agentmods.dev/skills/mohitagw15856/pm-claude-skills/creator-brand-kit"><img src="https://agentmods.dev/badge/skills/mohitagw15856/pm-claude-skills/creator-brand-kit/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/mohitagw15856/pm-claude-skills/creator-brand-kit"><img src="https://agentmods.dev/badge/skills/mohitagw15856/pm-claude-skills/creator-brand-kit.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.00097 | $0.01325 |
| Opus 5.5 | $0.00039 | $0.00530 |
| Sonnet 5.5 | $0.00019 | $0.00265 |
| Haiku 4.5 | $0.00010 | $0.00133 |
Grade A, and why
creator-brand-kit 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 2d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creator Brand Kit Skill
The difference between a creator who compounds and one who churns content is consistency — same niche, same voice, recognizable pillars. This skill builds the foundation other content skills read from: your niche, who you serve, how you sound, and what you talk about. It's the "reads-first" of the creator stack.
Working from a brief
Given a rough description (handle, what they post, vibe), build the full kit anyway — propose a sharp niche and pillars, and label choices as (draft — confirm). Push for specificity: "fitness" is not a niche; "strength training for desk workers over 40" is.
Required Inputs
Ask for (if not already provided):
- What they create and where (platforms/handles)
- Who it's for (the specific audience) and what they want
- The creator's personality / how they want to sound
- Goal (grow, monetize, build authority, drive a product)
Output Format
A one-page, reusable brand kit:
1. Niche & positioning
- Niche (specific): [audience] + [topic] + [angle]
- Positioning line: "I help [who] [achieve what] through [how]."
- What makes you different: the angle no one else in the niche owns.
2. Audience
Who they are, what they struggle with, what they aspire to, where they hang out.
3. Content pillars
3–5 pillars (the recurring themes you post about), each with: what it covers, why it serves the audience, and 2–3 example post ideas. Aim for a mix of grow (reach), nurture (trust), and convert (sell).
4. Voice & tone
- 3 voice attributes (e.g. "direct, warm, a little contrarian") with a do/don't example each.
- Words you use / avoid.
- A 2-sentence sample written in-voice as a reference.
5. Bio & handles
- A profile bio (≤150 chars) and a longer about-line.
- Consistent handle/name guidance across platforms.
6. Reuse note
How to paste this into other skills (or the Playground "🧠 Your context" box / a CONTEXT.md) so [[content-repurposer]], [[hook-writer]], [[short-form-script]], and [[newsletter-writer]] all sound like you.
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.
- 2d ago First seen · 90 lines · 97 tokens per session scan A b8c6c4315a10
creator-brand-kit is a skill published in the GitHub repository mohitagw15856/pm-claude-skills (1,449 stars, last pushed today), licensed MIT. It adds 97 tokens to every session and 1,325 once invoked, about $0.0004 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-12.
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…