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 jakesterns/agent-skills --skill skill-authoringgit clone --depth 1 https://github.com/jakesterns/agent-skillsWrote 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/jakesterns/agent-skills/skill-authoring)<a href="https://agentmods.dev/skills/jakesterns/agent-skills/skill-authoring"><img src="https://agentmods.dev/badge/skills/jakesterns/agent-skills/skill-authoring.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.00030 | $0.00287 |
| Opus 5 | $0.00015 | $0.00143 |
| Sonnet 5 | $0.00006 | $0.00057 |
| Haiku 4.5 | $0.00003 | $0.00029 |
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 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.
What it actually says
Skill Authoring
Use this skill when creating or improving an AI agent skill, prompt package, or reusable markdown workflow.
Inputs
- Skill goal, target users, expected trigger phrases, examples, draft markdown, or existing skill folder
- Target providers or compatibility requirements
Steps
- Clarify the task the skill should handle and when an agent should use it.
- Write a description that includes the action, domain, and trigger conditions.
- Keep the body concise: inputs, steps, outputs, and guidelines.
- Add tags that improve search and filtering.
- Add provider metadata when the skill is compatible across agents.
- Move detailed examples or long reference material into reference files when needed.
- Validate frontmatter, file naming, category placement, and discoverability.
- Review whether the skill gives useful procedural knowledge rather than generic advice.
Output
Return:
- Improved skill markdown or review notes
- Metadata recommendations
- Trigger and searchability improvements
- Validation issues
- Suggested tests or example prompts
Guidelines
- Prefer concrete workflows over broad principles.
- Avoid bloated skills that consume context without improving execution.
- Make the skill useful to an autonomous agent, not just a human reader.
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 · 41 lines · 30 tokens per session scan A 85252054cc58
skill-authoring is a skill published in the GitHub repository jakesterns/agent-skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 30 tokens to every session and 287 once invoked, about $0.0002 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.
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…