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 agentmods add skills/danielmiessler/paiplugin/create-skillnpx skills add danielmiessler/PAIPlugin --skill create-skillgit clone --depth 1 https://github.com/danielmiessler/PAIPluginWhat 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 | $0.00056 | $0.01033 |
| Opus 5 | $0.00028 | $0.00517 |
| Sonnet 5 | $0.00011 | $0.00207 |
| Haiku 4.5 | $0.00006 | $0.00103 |
Grade A, and why
create-skill scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- "Chrome DevTools MCP for web application debugging, visual testing, and browser automation. The ONLY acceptable way to debug web apps - NEVER use curl, fetch, or wget." How it starts
The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Skill - Skill Creation Framework
When to Activate This Skill
- "Create a new skill for X"
- "Build a skill that does Y"
- "Add a skill for Z"
- "Update/improve existing skill"
- "Structure a skill properly"
- User wants to extend Kai's capabilities
Core Skill Creation Workflow
Step 1: Understand the Purpose
Ask these questions:
- What does this skill do? (Clear, specific purpose)
- When should it activate? (Trigger conditions)
- What tools/commands does it use? (Dependencies)
- Is it simple or complex? (Determines structure)
Step 2: Choose Skill Type
Simple Skill (SKILL.md only):
- Single focused capability
- Minimal dependencies
- Quick reference suffices
- Examples: fabric-patterns, youtube-extraction
Complex Skill (SKILL.md + CLAUDE.md + supporting files):
- Multi-step workflows
- Extensive context needed
- Multiple sub-components
- Examples: development, website, consulting
Step 3: Create Directory Structure
# Simple skill
${PAI_DIR}/skills/[skill-name]/
└── SKILL.md
# Complex skill
${PAI_DIR}/skills/[skill-name]/
├── SKILL.md # Quick reference
├── CLAUDE.md # Full context
└── [subdirectories]/ # Supporting resources
Step 4: Write SKILL.md (Required)
Use this structure:
---
name: skill-name
description: Clear description of what skill does and when to use it. Should match activation triggers.
---
# Skill Name
## When to Activate This Skill
- Trigger condition 1
- Trigger condition 2
- User phrase examples
## [Main Content Sections]
- Core workflow
- Key commands
- Examples
- Best practices
## Supplementary Resources
For detailed context: `read ${PAI_DIR}/skills/[skill-name]/CLAUDE.md`
Step 5: Write CLAUDE.md (If Complex)
Include:
- Comprehensive methodology
- Detailed workflows
- Component documentation
- Advanced usage patterns
- Integration instructions
- Troubleshooting guides
Step 6: Add to Global Context
Update ${PAI_DIR}/global/KAI.md available_skills section to include the new skill so it shows up in the system prompt.
What ships with it
6 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.
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 · 138 lines · 56 tokens per session scan A 925784e3e386
create-skill is a skill published in the GitHub repository danielmiessler/PAIPlugin (56 stars, last pushed 9mo ago), licensed MIT. It adds 56 tokens to every session and 1,033 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
weekly-digests
Generate a serial week-by-week narrative digest of a project's full claude-mem timeline. Splits the timeline into per-ISO-week files, then runs one consecutive subagent per week — each receiving the prior week's carry-forward block — to produce one chapter per ISO week of data. Use when asked for "weekly digests"…
agentmail
Use when an agent needs AgentMail CLI email inboxes.
skill-template
Template for creating new Agent Skills for context engineering. Use this template when adding new skills to the collection.
Agent Development
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development…
skill-creator
Scaffold a new yoyo skill when a human or community issue asks for one ("add a skill for X", "create a skill that does Y"). Generates correct frontmatter, validates, writes to disk.
subagent-delegation
Canonical protocol for delegating GSD work to native Antigravity subagents — when to delegate, how to invoke, workspace isolation modes, and the inline fallback for older IDE versions.