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/doidor/agentrig/skill-authoringnpx skills add doidor/agentrig --skill skill-authoringgit clone --depth 1 https://github.com/doidor/agentrigWhat 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.00024 | $0.00428 |
| Opus 5 | $0.00012 | $0.00214 |
| Sonnet 5 | $0.00005 | $0.00086 |
| Haiku 4.5 | $0.00002 | $0.00043 |
Grade A, and why
skill-authoring 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 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.
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
skill-authoring (principle 4, 8)
Skills are procedural memory. A bloated skill library is as useless as no library, so new skills must clear an admission bar.
Admission test (all must hold)
- Reusable, not one-off. It encodes how to do one recurring thing well — not a single task.
- Not already covered. Search
.agents/skills/; if an existing skill is close, sharpen it instead of adding a near-duplicate. - A procedure, not a reflex. Passive, always-on constraints belong in
.agents/rules/, not a skill.
Structure
SKILL.mdwith YAML frontmatter:name, adescription< 250 chars,triggers,allowed-tools(scope the blast radius), and an optionalargument-hint.- Body: short, imperative steps. Cap iteration loops and state the fallback.
- Put long reference material in a sibling
references/file and link to it, so the skill itself stays small and the agent loads detail only on demand. - Scope
allowed-toolsto the minimum (e.g.Bash Read Grep Glob).
Keep surfaces in sync
When you add or remove a skill, update the skills inventory in AGENTS.md (the
AGENTRIG:skills-inventory block) so every surface advertises the same set. If the repo mirrors
skills across vendor dirs (.claude/.copilot/.agents/…), they should all point at one canonical
source (AgentRig wires these as symlinks).
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 · 36 lines · 24 tokens per session scan A f8033555e65c
skill-authoring is a skill published in the GitHub repository doidor/agentrig (5 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 428 once invoked, about $0.0001 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-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…