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 itaywol/adeptability --skill authoring-adept-skillsgit clone --depth 1 https://github.com/itaywol/adeptabilityWrote 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/itaywol/adeptability/authoring-adept-skills)<a href="https://agentmods.dev/skills/itaywol/adeptability/authoring-adept-skills"><img src="https://agentmods.dev/badge/skills/itaywol/adeptability/authoring-adept-skills/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/itaywol/adeptability/authoring-adept-skills"><img src="https://agentmods.dev/badge/skills/itaywol/adeptability/authoring-adept-skills.svg" alt="Reviewed on agentmods" width="80" 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.00045 | $0.00914 |
| Opus 5 | $0.00023 | $0.00457 |
| Sonnet 5 | $0.00009 | $0.00183 |
| Haiku 4.5 | $0.00005 | $0.00091 |
Grade A, and why
authoring-adept-skills 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 10d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Authoring a good adept skill
A skill is a directory <root>/skills/<id>/ with one SKILL.md (YAML frontmatter +
markdown body) and optional sidecars. adept renders it into every enabled harness, so
write it once, well, and harness-neutral.
Canonical SKILL.md format
---
id: pr-review # ^[a-z0-9](?:[a-z0-9-]{0,48}[a-z0-9])?$ — matches the directory name
description: Use before opening a PR. Tests, security, performance. # <= 280 chars
activation: agent # always | globs | agent | manual
globs: [] # REQUIRED when activation: globs (e.g. ["**/*.go"])
allowed-tools: [Read, Grep] # carried into Claude Code
targets: [] # empty = all enabled harnesses
tags: [review, quality]
---
# PR Review Checklist
- [ ] Tests added or updated
- [ ] No secrets in the diff
Validated against pkg/adeptschema/skill.schema.json on every load — adept sync fails
loudly on a malformed skill, so let it catch your mistakes.
Pick activation deliberately — this is the whole game
| activation | Fires when | Use for |
|---|---|---|
agent |
The model decides from the description | Most skills. Procedures, checklists, how-tos. |
globs |
A matching file is in context | Language/path-specific rules (**/*.go, **/*.tsx). |
always |
Every request | Rare. Project-wide invariants only — costs budget on every turn. |
manual |
Only when explicitly invoked | Heavy or destructive procedures you don't want auto-firing. |
The description is the trigger — write it like one
For activation: agent, the description is the only thing the model sees when deciding
whether to load the skill. Make it earn the load:
- Lead with when to apply, not what it is: "Use before opening a PR…" beats "A PR helper."
- Name concrete nouns the user will say (file types, commands, tools, error strings).
- One line, ≤ 280 chars. If you can't say when it applies in one line, the skill is too broad — split it.
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.
- 10d ago First seen · 80 lines · 45 tokens per session scan A cb7300188f38
authoring-adept-skills is a skill published in the GitHub repository itaywol/adeptability (9 stars, last pushed 1mo ago), licensed MIT. It adds 45 tokens to every session and 914 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
ai-infrastructure-ollama
Local LLM inference with the Ollama JavaScript client -- chat, streaming, tool calling, vision, embeddings, structured output, model management, and OpenAI-compatible endpoint.
ai-orchestration-langchain
LangChain.js patterns for building LLM applications — chat models, LCEL chains, prompt templates, structured output, agents, tools, RAG, streaming, and LangSmith tracing.
ai-provider-cohere-sdk
Official Cohere TypeScript SDK patterns -- CohereClientV2, chat, embeddings, rerank, RAG with citations, tool use, streaming, and model selection.
api-baas-appwrite
Appwrite backend-as-a-service — Auth, TablesDB, Storage, Functions, Realtime, permissions model, typed client.
api-database-mongodb
Native MongoDB driver (the mongodb npm package) - MongoClient lifecycle, typed collections, CRUD result shapes, cursors, aggregation pipelines, index design, transactions.
api-database-redis
Redis in-memory data store patterns with ioredis and node-redis -- caching, sessions, rate limiting, pub/sub, streams, queues, transactions, cluster.