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 using-adeptgit 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/using-adept)<a href="https://agentmods.dev/skills/itaywol/adeptability/using-adept"><img src="https://agentmods.dev/badge/skills/itaywol/adeptability/using-adept/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/using-adept"><img src="https://agentmods.dev/badge/skills/itaywol/adeptability/using-adept.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.00054 | $0.01395 |
| Opus 5.5 | $0.00022 | $0.00558 |
| Sonnet 5.5 | $0.00011 | $0.00279 |
| Haiku 4.5 | $0.00005 | $0.00139 |
Grade A, and why
using-adept 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 1mo 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using the adept CLI
adept makes one AI skill portable across every coding harness. You author once in a
canonical format; adept renders accurately into each harness's native layout and keeps
both sides in sync.
Mental model
canonical skill ──render──▶ .claude/skills/… (per-skill)
(.adeptability/ ──render──▶ .cursor/rules/….mdc (single-file)
skills/<id>/ ──render──▶ AGENTS.md (Codex aggregate)
SKILL.md) ──render──▶ .github/instructions (Copilot aggregate)
◀─sync-from─ (adopt edits made directly in a harness file)
- Identity is
(id, content-hash)— there are no version numbers. The hash decides whether something changed. - A skill is a directory
<root>/skills/<id>/with oneSKILL.md(YAML frontmatter + markdown body) and optional sidecars (scripts/,references/,assets/). - The filesystem is the source of truth.
config.jsononly records which harnesses are enabled, the materialization mode, and library remotes.
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
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
The commands you'll use most
adept init # scaffold .adeptability/ in the current project
adept init --from <git-url> # …and clone a remote skill library to pull skills from
adept harness add claude-code # enable a harness (claude-code | cursor | codex | copilot | opencode)
adept harness list
adept sync # render canonical skills → every enabled harness
adept status # init state, libraries, harnesses, and drift at a glance
adept diff # show exactly what differs between canonical and rendered
adept sync-from # adopt edits made directly in a harness file back to canonical
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.
- 1mo ago First seen · 126 lines · 54 tokens per session scan A 93fb11f7fd46
using-adept is a skill published in the GitHub repository itaywol/adeptability (9 stars, last pushed 2mo ago), licensed MIT. It adds 54 tokens to every session and 1,395 once invoked, about $0.0002 per session on Opus 5.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.