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 ahmadulhoq/agentskel --skill skill-authoringgit clone --depth 1 https://github.com/ahmadulhoq/agentskelWrote 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/ahmadulhoq/agentskel/skill-authoring)<a href="https://agentmods.dev/skills/ahmadulhoq/agentskel/skill-authoring"><img src="https://agentmods.dev/badge/skills/ahmadulhoq/agentskel/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.00046 | $0.01571 |
| Opus 5 | $0.00023 | $0.00785 |
| Sonnet 5 | $0.00009 | $0.00314 |
| Haiku 4.5 | $0.00005 | $0.00157 |
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 6d 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Authoring Guide
Purpose: Create skills that agents actually discover, trigger, and follow.
Step 1 — Skill Anatomy
Every skill is a SKILL.md file with this structure:
---
name: kebab-case-name # required; must match directory name
license: MIT # optional; license name or bundled file ref
compatibility: Designed for X # optional; only if skill has specific env needs
description: CSO-optimized triggering description (see Step 2) # required
---
Required fields: name, description. Optional standard fields (agentskills.io):
license (add for any distributed/public skill), compatibility (add only when
the skill body depends on a specific tool — e.g. references .claude/ paths).
Body conventions:
- Numbered steps with checkboxes (
- [ ]) for trackable progress - Gates at the end: "Do not [proceed/respond] until all steps above are checked off."
- Tables over prose — faster to parse, lower token cost
- One skill = one responsibility. If it does two things, split it.
Step 2 — CSO: Write Discoverable Descriptions
The description field determines whether agents find your skill. Agents match
skills to situations by scanning descriptions.
Rules:
- Describe triggering conditions, not workflow summaries
- Use the language a user would use in their request
- Start with "When..." or include "Use when..."
- Include the scenario, not the mechanism
- Keep the description under 1024 characters (agentskills.io spec hard limit). Multi-line YAML folded scalars (
>) are supported — the validator and stub generator normalize them to a single string. If the description needs more than 2-3 sentences, the skill scope is probably too broad. A pre-commit hook enforces the 1024-char limit on staged files.
| Bad (summary) | Good (triggering condition) |
|---|---|
| "Maps the codebase into MAP.md and SYMBOLS.md" | "When codebase structure has changed, MAP.md/SYMBOLS.md are missing or stale, or after major refactors and initial setup." |
| "Full feature development workflow" | "When the user asks to implement a new feature end-to-end requiring planning, branch creation, implementation, testing, and PR." |
| "Monthly maintenance tasks" | "When Knowledge Bus entries are older than 30 days, or memory files have stale content. Run monthly or when bus/ is cluttered." |
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.
- 6d ago First seen · 156 lines · 46 tokens per session scan A 70a583f22025
skill-authoring is a skill published in the GitHub repository ahmadulhoq/agentskel (13 stars, last pushed 22d ago), licensed MIT. It adds 46 tokens to every session and 1,571 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-09-02.
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…