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.
git 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/commands/tslateman/duet/lint)<a href="https://agentmods.dev/commands/tslateman/duet/lint"><img src="https://agentmods.dev/badge/commands/tslateman/duet/lint/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/commands/tslateman/duet/lint"><img src="https://agentmods.dev/badge/commands/tslateman/duet/lint.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.00010 | $0.00233 |
| Opus 5.5 | $0.00004 | $0.00093 |
| Sonnet 5.5 | $0.00002 | $0.00047 |
| Haiku 4.5 | $0.00001 | $0.00023 |
Grade A, and why
lint 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 1mo 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.
What it actually says
Lint
Context
- Markdownlint config: !
cat .markdownlint.json
Your Task
Run markdownlint on the target files and report results.
Arguments
${ARGUMENTS:-} — Three usage patterns:
- No arguments — Lint all markdown files in the project
- File path(s) — Lint specific files
- Directory — Lint all
.mdfiles in that directory
Workflow
-
Determine targets:
- If arguments provided, use them
- Otherwise, lint
commands/**/*.mdandskills/**/*.md
-
Run markdownlint:
npx markdownlint-cli [targets] -
Report results:
- If clean, report "No lint issues found"
- If violations found, group by file and list each issue
- For fixable issues, suggest
npx markdownlint-cli --fix [file]
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.
- 1mo ago First seen · 40 lines · 10 tokens per session scan A b964132a4fa4
lint is a command published in the GitHub repository tslateman/duet (1 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 233 once invoked, about $0.0000 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-08-31.
Other commands, from other repositories
quick
Quick execution mode for ad-hoc tasks without full workflow overhead.
audit-release
Diagnose release-readiness against the Starter Series quality bar — matched starter, version-vs-last-tag drift, CHANGELOG drift vs merged PRs, and publish-workflow kind. Read-only.
recap
Time-windowed "where was I?" — git commits, session notes, and files touched in the last N hours or days. Use after stepping away for a few hours or days. Not for cold starts after a long absence (use /tools:brief) or live development checks (use /tools:status).
status
Warm mid-session check — git detail, last session note, and in-progress backlog. Use when you still have mental context loaded and want a quick pulse. Not for cold starts (use /tools:brief) or planning (use /tools:overview).
wrap
You are closing a Claude Code session. Execute all steps below in order.
workday-complete
End-of-day wrap — validate, consolidate, review, changelog.