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/tslateman/duet/ianpx skills add tslateman/duet --skill iagit clone --depth 1 https://github.com/tslateman/duetWrote 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/tslateman/duet/ia)<a href="https://agentmods.dev/skills/tslateman/duet/ia"><img src="https://agentmods.dev/badge/skills/tslateman/duet/ia.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.00054 | $0.01335 |
| Opus 5 | $0.00027 | $0.00668 |
| Sonnet 5 | $0.00011 | $0.00267 |
| Haiku 4.5 | $0.00005 | $0.00134 |
Grade A, and why
ia 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 3d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Information Architecture
Overview
Information architecture is the structural design of shared information environments. When someone asks "where does this go?" or "I can't find anything", that's an IA problem.
Grounded in Rosenfeld, Morville & Arango's Information Architecture (4th ed.) and the Diataxis documentation framework. See references/rosenfeld-morville.md for the core systems.
The Four Systems
Every information space has four structural systems; evaluate each when reviewing or designing. references/rosenfeld-morville.md carries the full treatment (schemes, structures, label types, navigation modes, search components); this is the working summary.
- Organization: how content is grouped. Choose one primary scheme per level (exact: alphabetical, chronological, geographic; ambiguous: by topic, task, audience). Mixing schemes at one level confuses navigation.
- Labeling: what things are called. Describe content, not container ("Authentication", not "Section 3"); match the words users search for; introduce jargon inside, not at top levels.
- Navigation: how people move. Global (always visible), local (within a section), contextual (inline links), supplemental (index, site map, search). Three clicks to any content, or flatten the hierarchy.
- Search: how people find without browsing. Grep-friendly file names (
signal-contract.md, notdoc-7.md), headings that match search terms, synonym cross-references, consistent metadata.
Taxonomy Construction
When reviewing a project's organization, evaluate whether the taxonomy is sound:
- Can every item be placed in exactly one group? If not, categories overlap. Tighten the scheme.
- Are items at the same level comparable in scope? "utils" alongside "authentication" mixes granularity.
- Does depth exceed three levels? Over-splitting signals the taxonomy is too fine-grained. Flatten by merging related categories.
- Can a newcomer predict where to find something? If not, the grouping reflects how the author thinks, not how readers seek.
- Can a newcomer predict where to put something new? If not, the scheme has gaps or ambiguous boundaries.
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.
- 3d ago First seen · 142 lines · 54 tokens per session scan A 01519e033e09
ia is a skill published in the GitHub repository tslateman/duet (1 stars, last pushed 7d ago), licensed MIT. It adds 54 tokens to every session and 1,335 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
c-design
Takes a 00-overview.md stub from /c-brainstorm and materializes the full design folder (child docs in reading order, plain-English narrative, optional 97/98 sections, OOS shell). Generation modes: all-at-once (parallel generators, the default), one-by-one (write, pause for review, repeat), or inline (main session…
designer
Settle the look before the pixels — name the base and the delta, settle taste by looking, commit one design language to DESIGN.md. A command the user types, for work with an interface someone will see; standalone, no other skill required.
customer-journey-map
Visualize every touchpoint a customer has with a product or service — stages, actions, emotions, pain points, opportunities.
double-diamond
Design problems with two diamond phases: Discover/Define (right problem), Develop/Deliver (right solution).
liquid-glass
Apple Liquid Glass design system. Use when building UI with translucent, depth-aware glass morphism following Apple's design language. Provides CSS tokens, component patterns, dark/light mode, and animation specs.
sxo
Search Experience Optimization (SXO) — the bridge between SEO and UX/CRO. Audits the full journey from the SERP click to the on-page goal: SERP click-through factors (title/meta/rich results that win the click), then post-click experience signals that keep users and drive conversions — above-the-fold relevance and…