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 expertise-exchangegit 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/expertise-exchange)<a href="https://agentmods.dev/skills/itaywol/adeptability/expertise-exchange"><img src="https://agentmods.dev/badge/skills/itaywol/adeptability/expertise-exchange.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.00051 | $0.00910 |
| Opus 5 | $0.00026 | $0.00455 |
| Sonnet 5 | $0.00010 | $0.00182 |
| Haiku 4.5 | $0.00005 | $0.00091 |
Grade A, and why
expertise-exchange 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.
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Team expertise exchange
adept exchange is a shared billboard where developers (and their agents) ask
teammates for expertise and stack responses on each request. The server is
passive storage + auth — it never runs an agent. You drive it with the CLI;
always pass --json so you can parse results.
Entrypoint: check state first
Before anything else, run:
adept exchange status --json
It returns { "server": "...", "registered": <bool>, "dismissed": <bool> }.
Branch on it:
dismissed: true→ the user opted out. Do not prompt. Only act if the user explicitly asks to use the exchange this turn.registered: true→ you're set up. Go straight to the workflow below.registered: falseanddismissed: false→ the exchange could help here but isn't set up. Ask the user which they want (do not pick for them):- Point me at an existing server — they give you the URL + bootstrap
token and you run
adept exchange register --server <url> --bootstrap <tok>. - Host one — explain that a teammate runs
adept exchange serveonce and shares the bootstrap token it prints. Seereferences/setup-and-usage.md. - Dismiss — they don't want this. Run
adept exchange recommendation dismiss(saved per-user; reverse withadept exchange recommendation undismiss). Then stop suggesting it.
- Point me at an existing server — they give you the URL + bootstrap
token and you run
Sample the open board when you start (registered + not dismissed)
The moment you begin interacting with adept in a session, sample the open requests — not just the ones assigned to you:
adept exchange list --status attention-required --json
Skim each open request against the knowledge already available to you and the user this session: the current codebase, the user's domain and prior context, what you've just been working on. For any request that is relevant to what the user likely knows:
- Prompt the user — surface it: "Request #N asks about X; you have context on this. Want me to draft a response?" Do this even if the request is not assigned to the user — open expertise gaps are worth filling.
- If the request is under-specified or the existing responses leave gaps, note exactly what information is missing and ask the user to supply it, so the answer you post actually closes the gap.
- Never auto-post. Draft from the user's knowledge, confirm with them, then
respond. Do not invent expertise; if neither you nor the user knows, skip it.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 85 lines · 51 tokens per session scan A 35d98dccd59a
expertise-exchange is a skill published in the GitHub repository itaywol/adeptability (9 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 910 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
cli-framework-cli-commander
Node.js CLI development with Commander.js and @clack/prompts - command structure, interactive prompts, wizard state machines, config hierarchies, exit codes, cancellation handling.
cli-framework-oclif-ink
Modern CLI development combining oclif's command framework with Ink's React-based terminal rendering.
cli-prompts-clack
Beautiful interactive CLI prompts with @clack/prompts and custom prompts with @clack/core.
saga-orchestration
Implement saga patterns for distributed transactions and cross-aggregate workflows. Use this skill when implementing distributed transactions across microservices where 2PC is unavailable, designing compensating actions for failed order workflows that span inventory, payment, and shipping services, building…
meeting-efficiency
Agenda design, time boxing, decision capture, async alternatives, and productive facilitation.
deep-work-optimization
Focus blocks, distraction management, and flow state triggers for cognitively demanding work.