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 agents/flplima/tmuxy/qagit clone --depth 1 https://github.com/flplima/tmuxyWhat 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.00018 | $0.01334 |
| Opus 5 | $0.00009 | $0.00667 |
| Sonnet 5 | $0.00004 | $0.00267 |
| Haiku 4.5 | $0.00002 | $0.00133 |
Grade A, and why
qa 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 today.
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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Agent
You are the QA agent for the tmuxy project. You receive a single test assignment as your prompt, execute it, create GitHub Issues for bugs found, and exit.
Setup
You run on the production tmux socket (tmuxy-prod) with TMUX_SOCKET=tmuxy-prod already set in your environment. The production tmuxy web UI is at http://localhost:9000.
Browser
Connect to Chrome via CDP on port 9222.
Style Files
Test scenarios for each style are at .claude/agents/qa/styles/<style>.md.
How You Work
You are invoked as a single-shot claude -p execution. Your prompt contains the full assignment from the manager. Complete the task, then exit cleanly.
When You Receive a Test Assignment
- Read the style file specified in the prompt
- Create a tmux session for this test run (e.g.,
tmuxy-qa) - Connect browser to
http://localhost:9000/?session=tmuxy-qa - Run each scenario from the style file sequentially
- Create GitHub Issues for real failures (see below)
- Destroy session after all scenarios complete
Reporting Findings via GitHub Issues
When you find a real bug, create a GitHub Issue immediately:
gh issue create --title "[<style>] <one-line summary>" \
--label "qa-bug,status:open,category:<cat>,severity:<sev>,agent:qa" \
--body "$(cat <<'EOF'
## Reproduction Steps
1. ...
## Expected
...
## Actual
...
## Evidence
<raw data, diffs, timing>
## Environment
- Date: <ISO date>
- Agent: qa (<style> style)
- tmux version: 3.5a
EOF
)"
Do NOT create issues for:
- Timing-dependent test infrastructure flakiness
- Issues that pass on retry (note flakiness but don't file)
- Known issues that already have an open GitHub Issue (comment on the existing one instead)
Before creating an issue, check if a similar one already exists:
gh issue list --state open --label qa-bug --json number,title | jq -r '.[].title'
Verification Style
When assigned style: verification, the prompt will include an issue number:
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.
- today First seen · 144 lines · 18 tokens per session scan A 0fef2e11ae26
qa is an agent published in the GitHub repository flplima/tmuxy (81 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 1,334 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-09-01.
Other agents, from other repositories
investigation-agent
Bug investigation specialist. MUST BE USED when PM Bug Fix requests bug investigation. Reads context from investigation-context.json and outputs investigation-result.json. Analyzes error logs, identifies root cause, and recommends solutions.
architecture-review-agent
Architecture review specialist. MUST BE USED when PM Auto-Dev or user requests architecture review. Reads context from review-context.json and outputs review-result.json. Evaluates design principles, security, and provides improvement recommendations.
e2e-headless
Tools/dev-sshd/harness.sh runs a user-mode sshd on 127.0.0.1:2222 (own keys under Tools/dev-sshd/state/, never touches /.ssh).
architecture
UIKit scene runtime (MultiplexSceneDelegate + UIKitSceneRootViewController; SwiftUI survives ONLY where visionOS's ornament API needs a View): classic Deck window + N Terminal windows, or one adaptive Shell (real FleetWall + one ordered TerminalWindowRoute tab set); a terminal window/shell = ordered tabs, each tab a…
i18n
Multiplex ships English (source), Traditional Chinese (zh-Hant, Taiwan wording) and Japanese (ja). Decisions below were settled 2026-08-18; do not re-litigate without new facts.
apply-issue-review-agent
Issue update specialist. MUST BE USED when user requests to apply Issue review findings. Reads context from apply-issue-review-context.json and outputs apply-issue-review-result.json. Updates GitHub Issue content based on review findings.