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 DavidROliverBA/ArchitectKB --skill skill-creatorgit clone --depth 1 https://github.com/DavidROliverBA/ArchitectKBWrote 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/davidroliverba/architectkb/skill-creator)<a href="https://agentmods.dev/skills/davidroliverba/architectkb/skill-creator"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/skill-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/davidroliverba/architectkb/skill-creator"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/skill-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.00009 | $0.01261 |
| Opus 5 | $0.00005 | $0.00630 |
| Sonnet 5 | $0.00002 | $0.00252 |
| Haiku 4.5 | $0.00001 | $0.00126 |
Grade A, and why
skill-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 9d 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/skill-creator
Create a new skill for the vault with guided prompts, following clawdbot's meta-skill pattern.
Usage
/skill-creator <skill-name>
/skill-creator transcribe
/skill-creator vendor-comparison
Instructions
Phase 1: Initial Setup
- Parse the skill name from the command
- Check if a skill with this name already exists in
.claude/skills/ - If exists, warn and ask if they want to overwrite or rename
Phase 2: Gather Skill Metadata (6-Step Process)
Ask the user these questions in sequence:
Step 1: Purpose & Description
Question: "What does this skill do? (One sentence)"
- This becomes the
description:field in frontmatter - Should be concise and action-oriented
- Example: "Convert voice recordings to text using Whisper API"
Step 2: Model Tier
Question: "Which model tier is appropriate?"
| Option | When to Use |
|---|---|
| haiku (default) | Fast, simple tasks - note creation, searches, quick transforms |
| sonnet | Complex analysis, code review, multi-step reasoning |
| opus | Deep research, complex planning, extended reasoning |
Store in model: frontmatter field.
Step 3: Execution Context
Question: "How should this skill execute?"
| Option | When to Use |
|---|---|
| fork (default) | Independent execution, can run in parallel |
| orchestrate | Coordinates multiple dependent sub-agents |
| (no context) | Single-session, simple execution |
Store in context: frontmatter field.
Step 3b: Agent Type (v2.1.0+)
Question: "Should this skill use a specific agent type?"
| Option | When to Use |
|---|---|
| (omit - default) | Use default agent behaviour |
| Explore | Read-only codebase exploration |
| Plan | Design implementation plans |
| general-purpose | Full capabilities needed |
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.
- 9d ago First seen · 217 lines · 9 tokens per session scan A 1d9082cbed03
skill-creator is a skill published in the GitHub repository DavidROliverBA/ArchitectKB (52 stars, last pushed 6mo ago), licensed MIT. It adds 9 tokens to every session and 1,261 once invoked, about $0.0000 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-09-03.
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…