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 commands/tslateman/duet/lintgit clone --depth 1 https://github.com/tslateman/duetWhat 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.00010 | $0.00233 |
| Opus 5 | $0.00005 | $0.00117 |
| Sonnet 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 2d 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.
- 2d 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 5d ago), licensed MIT. It adds 10 tokens to every session and 233 once invoked, about $0.0001 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 commands, from other repositories
prd-task-doc
Generate development task documentation from PRD files with optional AI model collaboration for optimization and review.
impl-task
Implementation task executor using unified artisan-impl approach - processes each top-level task with high-quality code generation and automatic progress tracking.
git-commit
Git workflow specialist for commit management, branch operations, and repository analysis. Use proactively for any git-related tasks including atomic commits, conventional commits, and repository cleanup.
pr-address
Address PR review comments on current branch.
plan-save
Save the current session's plan to GitHub as an issue.
enforce_standards
CRITICAL: Before running the code standards enforcer, we must prepare the stack properly and abort if there are merge conflicts.