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/itaywol/adeptability/managing-librarynpx skills add itaywol/adeptability --skill managing-librarygit 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/managing-library)<a href="https://agentmods.dev/skills/itaywol/adeptability/managing-library"><img src="https://agentmods.dev/badge/skills/itaywol/adeptability/managing-library.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 | $0.00053 | $0.00711 |
| Opus 5 | $0.00026 | $0.00356 |
| Sonnet 5 | $0.00011 | $0.00142 |
| Haiku 4.5 | $0.00005 | $0.00071 |
Grade A, and why
managing-library 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 4d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Managing an adept library
A library is a repo created with adept init --as-library. It exists to publish skills
to other repos. It has two skill locations — keep them straight:
| location | source in adept skill list |
published to consumers? | purpose |
|---|---|---|---|
skills/<id>/ (repo root) |
published |
yes | the library's product |
.adeptability/skills/<id>/ |
private |
no | dev-only helpers, rendered to your harness |
config.json carries "layout": "library". Consumers add the repo with
adept library add <name> --from <git-url> and only ever see the published skills/.
Adding skills
In a library, adept skill add defaults to private (it's the safe default — nothing is
published by accident). Use --publish for skills that ship to consumers:
adept skill add my-helper # → .adeptability/skills/my-helper/ (private, dev-only)
adept skill add pr-review --publish # → skills/pr-review/ (published)
adept skill list # SOURCE column shows published | private | library:<name>
edit and remove take a bare <id> and find it in either location (published wins on a
name clash):
adept skill edit pr-review
adept skill remove my-helper
Rendering dev helpers to your own harness
Private skills render to your enabled harnesses so they assist you while you author the library, without shipping:
adept harness add claude-code # once
adept sync # renders published + private → .claude/skills/, …
echo ".claude/" >> .gitignore # rendered output is not source
adept init --as-library seeds this skill and the authoring helpers (using-adept,
authoring-adept-skills) straight into .adeptability/skills/ for you.
Publishing
Commit and push. Only skills/ (published) reaches consumers; .adeptability/skills/ and the
gitignored .claude/ stay local.
git add skills .adeptability && git commit -m "add <skill>" && git push
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.
- 4d ago First seen · 73 lines · 53 tokens per session scan A 47b7df938401
managing-library is a skill published in the GitHub repository itaywol/adeptability (9 stars, last pushed 1mo ago), licensed MIT. It adds 53 tokens to every session and 711 once invoked, about $0.0003 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
pr-review
AUTHOR SKILL (internal to microsoft/aspire-skills). Reviews pull requests into this repo for problems only — bugs, regressions, missing eval coverage, frontmatter or routing damage, plugin-manifest drift, hook safety, and other concrete issues. Drives a six-step workflow: identify the PR, ensure the branch is…
architecture-cleanup
Use when performing a behavior-preserving architectural cleanup or refactor on a codebase and you need strict guardrails against changing functionality, building a framework, or rewriting tests to fit the new design.
aspire-orchestration
../../../../../skills/aspire-orchestration/SKILL.md.
aspire-deployment
../../../../../skills/aspire-deployment/SKILL.md.
aspire-init
../../../../../skills/aspire-init/SKILL.md.
aspire-monitoring
../../../../../skills/aspire-monitoring/SKILL.md.