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 jasonkneen/lazar --skill create-skillgit clone --depth 1 https://github.com/jasonkneen/lazarWrote 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/jasonkneen/lazar/create-skill)<a href="https://agentmods.dev/skills/jasonkneen/lazar/create-skill"><img src="https://agentmods.dev/badge/skills/jasonkneen/lazar/create-skill.svg" alt="Measured on agentmods" 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.00000 | $0.00390 |
| Opus 5 | $0.00000 | $0.00195 |
| Sonnet 5 | $0.00000 | $0.00078 |
| Haiku 4.5 | $0.00000 | $0.00039 |
Grade A, and why
create-skill 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 7d 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-skill
When you need a capability that isn't in INDEX.md, author a new skill.
When to use
- INDEX.md has nothing relevant.
- An existing skill could be adapted but doesn't fit the current need cleanly.
- You found yourself doing the same multi-step bash dance twice; capture it.
How to use
-
Confirm the gap:
cat $LAZAR_HOME/skills/INDEX.md -
Pick a short, descriptive kebab-case name (e.g.
web-search,file-watch,git-status). -
Create the skill folder and SKILL.md:
mkdir -p $LAZAR_HOME/skills/<name> cat > $LAZAR_HOME/skills/<name>/SKILL.md <<'EOF' # <name> <one-line purpose> ## When to use <triggers — what situation calls for this skill> ## How to use <ordered steps the next invocation will follow> ## Recipe <copy-pasteable bash; assume the agent runs it verbatim> EOF -
Register it in the index:
echo "- <name> — <one-line purpose>" >> $LAZAR_HOME/skills/INDEX.md -
Verify:
cat $LAZAR_HOME/skills/INDEX.md cat $LAZAR_HOME/skills/<name>/SKILL.md
Principles
- Skills should be small. If a skill does two things, split it.
- Prefer composition: existing skills + bash +
lazar -precursion. - Bash-first. If the recipe can't be expressed in bash, the skill is too big.
- Document the failure modes you hit while designing it. Future-you will thank you.
- Skills go in
$LAZAR_HOME/skills/. Never write outside that tree to extend your capabilities.
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.
- 7d ago First seen · 53 lines · 0 tokens per session scan A 7a5e1f3ae857
create-skill is a skill published in the GitHub repository jasonkneen/lazar (31 stars, last pushed 25d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 390 tokens. 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…