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 yacb2/aidex --skill delegation-detailgit clone --depth 1 https://github.com/yacb2/aidexWrote 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/yacb2/aidex/delegation-detail)<a href="https://agentmods.dev/skills/yacb2/aidex/delegation-detail"><img src="https://agentmods.dev/badge/skills/yacb2/aidex/delegation-detail/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/yacb2/aidex/delegation-detail"><img src="https://agentmods.dev/badge/skills/yacb2/aidex/delegation-detail.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.00063 | $0.02056 |
| Opus 5.5 | $0.00025 | $0.00822 |
| Sonnet 5.5 | $0.00013 | $0.00411 |
| Haiku 4.5 | $0.00006 | $0.00206 |
Grade A, and why
delegation-detail 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Delegation detail
How to brief, size, launch and gate delegates. The routed agents ship with the plugin and
are named aidex:<name> in subagent_type: aidex:artifact-sonnet, aidex:backlog-filer,
aidex:bugfix-opus, aidex:figure-sonnet, aidex:gate-runner, aidex:impl-sonnet,
aidex:lookup-sonnet, aidex:research-sonnet, aidex:review-diff-opus,
aidex:smoke-sonnet, aidex:synthesis-sonnet, aidex:task-general,
aidex:verify-browser-opus, aidex:verify-browser-sonnet.
The brief
A brief names paths, never "the file we discussed": goal, where to work, what to read first, what is forbidden, how to verify, what to return. Use a fresh agent always; a fork only when what the task needs exists nowhere but in this conversation (a fork costs several times a fresh agent). Two parts are load-bearing; keep them as named sections, not sentences in a paragraph:
- "Files to read first", as the brief's own first step. The same sentence buried in a
lead paragraph is not acted on; as a named first step the canon actually gets read.
Name any file over about 25 KB as a Read-tool target: a Bash result over about 30000
characters reaches the agent only as a ~2 KB preview, so
cat,sedorheadof it reads almost nothing (measured on aidex:artifact-sonnet runs). - "what you deliberately left alone", inside what to return: every defect or edge the delegate saw and did not touch, one line each, no fix. A delegate is fresh by construction, and a fresh context is the one that lacks the caution a long session builds up, so this section is what restores it, for a small extra cost. Say it in your own session's work too while the context is still young.
When delegating pays
A delegate costs a brief (about one turn) plus a short reply. Doing the work here costs every call times the current context depth, and that output is re-read on every later turn. So: delegate when re-reading your context costs more than a brief. Early in a session, with a small context, keep a short job here unless the part is itself token-heavy (a transcript sweep, a long command's output). Late in a session, or on a model that charges a lot to re-read context, the balance flips and delegating is cheaper. This skill states the principle, not a per-model depth table: prices change and the numbers behind such a table are the owner's own ledger.
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.
- 4d ago Changed · +6 lines dc1382fde753
- 6d ago Changed · +9 lines 672fbf62d77a
- 11d ago First seen · 122 lines · 63 tokens per session scan A 0126f08e6cd8
delegation-detail is a skill published in the GitHub repository yacb2/aidex (2 stars, last pushed 2d ago), licensed MIT. It adds 63 tokens to every session and 2,056 once invoked, about $0.0003 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-10-13.
Other skills, from other repositories
github-workflow
GitHub best practices for pull requests, code reviews, issues, Actions workflows, and repository management.
pnpm
Best practices for pnpm package manager, workspace management, and monorepo configuration.
lerna
Best practices for Lerna monorepo management, versioning, and publishing.
nx
Best practices for Nx monorepo development, project configuration, and code generation.
monorepo
Best practices for monorepo development with TypeScript, React, Next.js, Expo, Turbo, and related technologies.
monorepo-tamagui
Monorepo development guidelines using Tamagui, Turbo, Next.js, Expo, Supabase, and cross-platform best practices.