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/adrnpx skills add tslateman/duet --skill adrgit 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/adr)<a href="https://agentmods.dev/skills/tslateman/duet/adr"><img src="https://agentmods.dev/badge/skills/tslateman/duet/adr.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.00045 | $0.00538 |
| Opus 5 | $0.00023 | $0.00269 |
| Sonnet 5 | $0.00009 | $0.00108 |
| Haiku 4.5 | $0.00005 | $0.00054 |
Grade A, and why
adr 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Decision Record Generator
Generate an Architecture Decision Record (ADR) based on the conversation context and any architectural decisions discussed.
ADR Format
Create a markdown file with this structure:
# ADR-[NUMBER]: [TITLE]
**Date:** [YYYY-MM-DD]
**Status:** [Proposed | Accepted | Deprecated | Superseded]
**Deciders:** [Who was involved]
## Context
What is the issue that we're seeing that is motivating this decision or change?
## Decision
What is the change that we're proposing and/or doing?
## Consequences
What becomes easier or more difficult to do because of this change?
### Positive
- [Benefit 1]
- [Benefit 2]
### Negative
- [Trade-off 1]
- [Trade-off 2]
### Risks
- [Risk and mitigation]
## Alternatives Considered
### [Alternative 1]
- **Description:** What was this option?
- **Rejected because:** Why didn't we choose it?
### [Alternative 2]
- **Description:** What was this option?
- **Rejected because:** Why didn't we choose it?
## References
- [Related PR, issue, or document]
- [Relevant discussion or prior art]
Instructions
-
Extract from context: Use the conversation to identify:
- The problem or decision being made
- Options that were discussed
- The chosen approach and rationale
- Trade-offs acknowledged
-
Find the ADR location: Look for existing ADRs:
docs/adr/ordocs/decisions/adr/at project root- If none exist, suggest creating
docs/adr/
-
Number appropriately: Check existing ADRs and use the next number
-
Write concisely: ADRs should be scannable:
- Context: 2-4 sentences
- Decision: 1-2 sentences
- Consequences: Bullet points
- Alternatives: Brief, focused on why rejected
-
Capture the why: The decision itself ages; the reasoning stays valuable
See Also
/research: Research informs the decision; ADR captures it/review: Reviews that surface architectural decisions belong in ADRsskills/FRAMEWORKS.md: Full framework index
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 · 93 lines · 45 tokens per session scan A 82b0b72ee519
adr is a skill published in the GitHub repository tslateman/duet (1 stars, last pushed 7d ago), licensed MIT. It adds 45 tokens to every session and 538 once invoked, about $0.0002 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
to-plan
Capture the chat into .task/task/ .md with ## Description plus ## Plan (Goal/Touches/Logic) — the deepest one-task capture.
roadmap-to-workflow
Fan an approved .task/roadmap/ .md out to a dynamic Workflow — parallel planning, serialized implementation, dependency-ordered waves.
self-improve
Self-improve this skills repo — surface and (safely) apply quality improvements across four parallel read-only lenses (Clarity, Leanness, Coverage, Ergonomics). Sibling of /self-audit — audit fixes rule violations, improve raises quality where no rule is broken. Local meta-skill, independent of the /task: pipeline.
to-roadmap
Capture a multi-task initiative into .task/roadmap/ .md — a phase-grouped backlog of ready-to-pick-up items.
to-task
Capture the chat (or a roadmap item) into .task/task/ .md — ## Description only, no ## Plan.
self-audit
Self-audit this skills repo against CLAUDE.md invariants, the artifact contract, and README/CLAUDE.md/docs sync via three parallel read-only subagents. Local meta-skill — independent of the /task: pipeline.