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 digital-stoic-org/agent-skills --skill creategit clone --depth 1 https://github.com/digital-stoic-org/agent-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/digital-stoic-org/agent-skills/create)<a href="https://agentmods.dev/skills/digital-stoic-org/agent-skills/create"><img src="https://agentmods.dev/badge/skills/digital-stoic-org/agent-skills/create/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/digital-stoic-org/agent-skills/create"><img src="https://agentmods.dev/badge/skills/digital-stoic-org/agent-skills/create.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.00036 | $0.00521 |
| Opus 5.5 | $0.00014 | $0.00208 |
| Sonnet 5.5 | $0.00007 | $0.00104 |
| Haiku 4.5 | $0.00004 | $0.00052 |
Grade A, and why
create 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 1mo 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.
What it actually says
Create — Philosopher Persona Generator
Meta-skill that generates a new philosopher persona following the established plugin patterns. Creates SKILL.md + reference.md for any historical thinker with sufficient written corpus in LLM training data.
Arguments
| Arg | Required | Description | Example |
|---|---|---|---|
<name> |
✅ | Thinker's common name → becomes skill name + directory | montaigne |
--lang |
❌ | Primary language for key concepts (auto-detected from origin) | --lang el |
--focus |
❌ | Emphasis area if thinker is multi-domain | --focus ethics |
Procedure
Step 1 — Corpus Assessment
Evaluate LLM training data coverage for the requested thinker. Use embedded knowledge — do NOT web search.
Produce a coverage table (🟢 deep / 🟡 partial / 🔴 thin): Published works, Key concepts, Biography, Letters, Unpublished/notebooks, Reception history, Writing style & voice, Native-language vocabulary.
Gate: >2 🔴 → warn user, suggest alternative. Wait for confirmation.
Step 2 — Generate Persona
Load templates, then generate both files. See reference.md for full section checklist and quality criteria.
- Read
../../framework.md+../nietzsche/reference.md+../nietzsche/SKILL.mdas structural templates - Generate
philosopher/skills/<name>/reference.md— all 8 required sections adapted to the thinker - Generate
philosopher/skills/<name>/SKILL.md— following nietzsche SKILL.md pattern with thinker-specific voice and cutoff date
Step 3 — Review Gate
Present both files to user. Ask: voice authentic? periods correct? concepts complete? opening lines land? challenges sharp? Iterate if needed.
Step 4 — Write Files
Create directory with mkdir -p, then write both files. Remind user to test with /<name> and run /edit-plugin for version bump.
What ships with it
1 file 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.
- 1mo ago First seen · 49 lines · 36 tokens per session scan A d5aef78449c9
create is a skill published in the GitHub repository digital-stoic-org/agent-skills (20 stars, last pushed 12d ago), licensed MIT. It adds 36 tokens to every session and 521 once invoked, about $0.0001 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-09-04.
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…