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 whawkinsiv/solo-founder-skills --skill about-megit clone --depth 1 https://github.com/whawkinsiv/solo-founder-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/whawkinsiv/solo-founder-skills/about-me)<a href="https://agentmods.dev/skills/whawkinsiv/solo-founder-skills/about-me"><img src="https://agentmods.dev/badge/skills/whawkinsiv/solo-founder-skills/about-me/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/whawkinsiv/solo-founder-skills/about-me"><img src="https://agentmods.dev/badge/skills/whawkinsiv/solo-founder-skills/about-me.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00147 | $0.03042 |
| Opus 5 | $0.00073 | $0.01521 |
| Sonnet 5 | $0.00029 | $0.00608 |
| Haiku 4.5 | $0.00015 | $0.00304 |
Grade A, and why
about-me 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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
About Me: Founder Profile
Create ABOUT-ME.md — a reference file that captures who you are so every other skill can personalize its output.
Without this file, skills produce generic output. With it, they produce output that sounds like a specific human with specific experience, opinions, and a communication style.
The brain dump IS a voice sample. How you describe yourself reveals your communication style — sentence length, formality, humor, vocabulary. This skill analyzes your writing patterns, not just what you say.
Workflow
If ABOUT-ME.md already exists
Ask the founder what changed. Update the relevant sections. Don't start over.
If creating from scratch
Step 1 — Collect the brain dump:
Tell me about yourself. Write naturally — like you're explaining to a smart friend who needs to understand who you are in order to write as you and give you advice that fits your actual situation.
Cover whatever feels important, but here are areas that help the most:
- What you do and how you got here
- What you know deeply — your unfair expertise
- Strong opinions you have about your industry
- A few stories that shaped you — wins, failures, lessons
- How you communicate (or just write naturally and I'll pick it up)
- Where you have an existing presence or audience
- What you're great at vs. what you'd rather not do yourself
Let them write. Don't interrupt.
Step 1.5 — Voice signal check:
The question is NOT "did they write enough words." The question is: can you identify at least 4 concrete, testable writing patterns from what they gave you?
A pattern is testable if you could check a paragraph against it and say yes or no. "Uses short sentences" — testable. "Authentic voice" — not testable. "Starts with the point, never buries the lede" — testable. "Relatable and down-to-earth" — not testable.
Try to list 4 patterns right now from their brain dump. If you can't:
"I can see what you're saying, but I can't hear how you say it yet — there's not enough of your actual writing voice here for me to build real style rules. I need more signal. Either of these would help:"
- Tell a story in full. Pick one of the stories or opinions you mentioned above and write it out — a couple paragraphs, stream of consciousness, don't edit yourself.
- Paste things you've already written. Copy-paste 2-3 social media posts, emails, Slack rants, blog drafts, tweets — anything where you were writing as yourself. Raw and unedited is better than polished.
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 · 220 lines · 147 tokens per session scan A 4aee9979f5a6
about-me is a skill published in the GitHub repository whawkinsiv/solo-founder-skills (243 stars, last pushed 16d ago), licensed MIT. It adds 147 tokens to every session and 3,042 once invoked, about $0.0007 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
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…