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 subagentgit 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/subagent)<a href="https://agentmods.dev/skills/jasonkneen/lazar/subagent"><img src="https://agentmods.dev/badge/skills/jasonkneen/lazar/subagent.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00103 | $0.00867 |
| Opus 5 | $0.00051 | $0.00434 |
| Sonnet 5 | $0.00021 | $0.00173 |
| Haiku 4.5 | $0.00010 | $0.00087 |
Grade A, and why
subagent 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 8d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
subagent — how I extend myself
Delegation is a core skill. I never call lazar -p directly (a pre-tool hook
vetoes it). I go through the locked spawn surface, preferably with a
context pack:
# Recommended: BRIEF.md + thin prompt + lazar-spawn
bash "$LAZAR_HOME/skills/_meta/subagent/pack-and-spawn.sh" <task-id> \
--objective "..." \
--out /absolute/deliverable \
--path /absolute/input \
--skill create-skill \
--note "user wants terse output"
# Lower-level (already-written prompt file):
bash "$LAZAR_HOME/bin/lazar-spawn" <task-id> <prompt-file>
bin/lazar-spawn is installed by setup.sh with the same immutability story
as bin/lazar. Budget state lives in logs/subagent/. The copy under
skills/_meta/subagent/spawn.sh is only a re-exec stub.
When to spawn vs do it yourself
| Do it yourself (bash in-process) | Spawn a child |
|---|---|
| < ~3 tool steps | Isolated unit with a file deliverable |
| Needs live conversational deixis | Context isolation would help the parent |
| Exploratory one-off | 2+ independent units (parallel via agent-dispatch) |
| Result is just stdout to reason on | SUCCESS can be checked on disk |
Never wrap every bash call as a subagent — latency and token cost explode.
Context pack (enough context without cloning chat)
Children are strangers with a filesystem. Do not dump parent history.
Write workspace/tasks/<id>/BRIEF.md (pack-and-spawn does this) containing:
- Imperative objective
- Absolute input/output paths
SUCCESS:+EXPECT-VERIFY:claims you author- Relevant skill names (not full INDEX)
- ≤ ~20 lines of prior decisions / constraints
- Out-of-scope list
- RESULT.md protocol (
DONE/BLOCKED)
The spawn -p string stays thin and points at the BRIEF.
Gate on the envelope
lazar-spawn re-checks EXPECT-VERIFY and returns
{"status":"ok","matched":true} only if claims hold. Trust matched, not
child prose. On matched:false, fix the BRIEF and retry within ceilings.
What ships with it
3 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.
- 8d ago First seen · 85 lines · 103 tokens per session scan A 6c11d7b97d61
subagent is a skill published in the GitHub repository jasonkneen/lazar (31 stars, last pushed 26d ago), licensed MIT. It adds 103 tokens to every session and 867 once invoked, about $0.0005 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-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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…