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/wkusnierczyk/aigent/aigent-buildernpx skills add wkusnierczyk/aigent --skill aigent-buildergit clone --depth 1 https://github.com/wkusnierczyk/aigentWhat 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.00058 | $0.00553 |
| Opus 5 | $0.00029 | $0.00277 |
| Sonnet 5 | $0.00012 | $0.00111 |
| Haiku 4.5 | $0.00006 | $0.00055 |
Grade B, and why
aigent-builder scanned grade B 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.
Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
aigent new "<purpose>" --dir .claude/skills/<name>/ What it actually says
Skill Builder
Setup
Check if aigent is available:
command -v aigent
With aigent CLI
If aigent is on $PATH, use the CLI for authoritative skill generation:
-
Build the skill:
aigent new "<purpose>" --dir .claude/skills/<name>/ -
Validate the result:
aigent validate .claude/skills/<name>/ -
If validation reports errors, fix the SKILL.md and re-validate.
Use --no-llm to force deterministic mode (no API keys needed).
Use --name <name> to override the derived skill name.
The CLI defaults to outputting in ./<name>/ in the current directory. The
--dir flag above overrides this to place skills in .claude/skills/, which
is the standard Claude Code skill location.
Without aigent CLI
If aigent is not available, generate the SKILL.md directly.
Name rules
- Lowercase letters, numbers, and hyphens only
- Maximum 64 characters
- Prefer gerund form: "processing-pdfs", "analyzing-data"
- No reserved words: "anthropic", "claude"
- No XML tags
- Must match directory name
Description rules
- Non-empty, maximum 1024 characters
- Third person: "Processes PDFs..." not "I process PDFs..."
- Include what the skill does AND when to use it
- No XML tags
Body guidelines
- Keep under 500 lines
- Be concise — only add context Claude doesn't already have
- Use ## headings for sections
- Link to additional files for large content
Output
Write the SKILL.md to .claude/skills/<name>/SKILL.md with:
---
name: <kebab-case-name>
description: <what-it-does-and-when-to-use-it>
---
# <Title>
## Quick start
[Concise instructions]
## Usage
[Detailed usage]
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 · 94 lines · 58 tokens per session scan B 3e2d1d67f685
aigent-builder is a skill published in the GitHub repository wkusnierczyk/aigent (4 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 58 tokens to every session and 553 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…