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/install-statusline)<a href="https://agentmods.dev/commands/tslateman/duet/install-statusline"><img src="https://agentmods.dev/badge/commands/tslateman/duet/install-statusline/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/install-statusline"><img src="https://agentmods.dev/badge/commands/tslateman/duet/install-statusline.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.00015 | $0.00497 |
| Opus 5.5 | $0.00006 | $0.00199 |
| Sonnet 5.5 | $0.00003 | $0.00099 |
| Haiku 4.5 | $0.00002 | $0.00050 |
Grade B, and why
install-statusline scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- Current user statusline script: !`cat ~/.claude/statusline-command.sh 2>/dev/null || echo "(none)"` What it actually says
Install Statusline
Context
- Duet statusline script: !
cat statusline/statusline-command.sh - Current user statusline config: !
jq -r '.statusLine // empty' ~/.claude/settings.json 2>/dev/null || echo "(none)" - Current user statusline script: !
cat ~/.claude/statusline-command.sh 2>/dev/null || echo "(none)"
Your Task
Install the duet statusline script to ~/.claude/ and configure it in ~/.claude/settings.json.
-
Check current state:
- Does
~/.claude/settings.jsonalready have astatusLinefield? - Does
~/.claude/statusline-command.shalready exist? - Categorize: no existing statusline, identical, or different
- Does
-
If identical: Report "Statusline already up to date" and stop.
-
If different or new:
- If a statusline script already exists, show the diff between duet's version and the existing one
- Ask the user whether to install (replace) or skip
- Make clear this will overwrite their current statusline
-
Install:
- Copy
statusline/statusline-command.shto~/.claude/statusline-command.sh - Make it executable:
chmod +x ~/.claude/statusline-command.sh - If
~/.claude/settings.jsonlacks astatusLinefield, add it:"statusLine": { "type": "command", "command": "bash ~/.claude/statusline-command.sh" } - Use
jqto merge the statusLine field without disturbing other settings
- Copy
-
Verify:
- Confirm the script exists and is executable
- Confirm
settings.jsonhas thestatusLinefield - Report success — note that the statusline will appear on next Claude Code session start
Note
To disable the statusline, delete the statusLine key from settings.json entirely. Setting it to null causes a settings validation error.
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 · 50 lines · 15 tokens per session scan B 3d9530893539
install-statusline is a command published in the GitHub repository tslateman/duet (1 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 497 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). 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.
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).
release
Execute the full release workflow for ekstend plugins.
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).
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.
workday-complete
End-of-day wrap — validate, consolidate, review, changelog.