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 skills add vincentkoc/dotskills --skill tmux-agent-lane-orchestratorgit clone --depth 1 https://github.com/vincentkoc/dotskillsWrote 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/vincentkoc/dotskills/tmux-agent-lane-orchestrator)<a href="https://agentmods.dev/skills/vincentkoc/dotskills/tmux-agent-lane-orchestrator"><img src="https://agentmods.dev/badge/skills/vincentkoc/dotskills/tmux-agent-lane-orchestrator/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/skills/vincentkoc/dotskills/tmux-agent-lane-orchestrator"><img src="https://agentmods.dev/badge/skills/vincentkoc/dotskills/tmux-agent-lane-orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Memory Poisoning · line 13 Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
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.00063 | $0.00692 |
| Opus 5 | $0.00032 | $0.00346 |
| Sonnet 5 | $0.00013 | $0.00138 |
| Haiku 4.5 | $0.00006 | $0.00069 |
Grade A, and why
tmux-agent-lane-orchestrator 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.
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tmux Agent Lane Orchestrator
Purpose
Turn a tmux window of coding-agent workers into a visible, auditable lane with clear state and next actions.
When to use
- Monitor or summarize a tmux worker lane.
- Reconstruct worker state after a manager cold start.
- Detect duplicated, idle, waiting, blocked, or risky work.
- Coordinate several coding-agent panes without mutating them blindly.
Workflow
- Establish lane scope.
- Prefer an explicit lane number.
- Otherwise infer it from a current tmux window named
L<number>. - Do not inspect other lanes unless the operator expands scope.
- Capture lane state.
python3 scripts/lane_snapshot.py --lane <number>- Add
--session <name>outside the active tmux session. - If a descendant command does not contain its resumed thread ID, repeat
--thread L<number>.<pane>=<thread-id>from separately verified evidence. - Add
--jsonfor machine-readable output. - Add
--cursor-file <path>only when bounded incremental state is wanted; the helper writes no persistent state by default.
- Cross-check panes and logs.
- Pane titles alone are weak evidence.
- Resolve pane ID to shell PID, descendant Codex PID, exact thread ID, the state-database rollout path, and the newest turn.
- Shared cwd and generic terms such as
CI,failed, orrunningnever establish ownership. - Missing or conflicting identity is
unknown, never a restore target.
- Classify each pane.
- Use the newest exact turn and changing event/tool/token counters.
- A completed turn after an earlier error is
completed, not blocked. - Report bounded bytes read and truncation with the state.
- Include the evidence and next action, not only the label.
- Intervene conservatively.
- Inspect before steering.
- Avoid duplicate heavy checks.
- Do not kill or mutate another pane without explicit scope.
- Prefer reversible actions and targeted commands.
- Summarize in manager style.
- One line per pane: mission, state, evidence, blocker, next action.
- Add one short manager judgment about where attention belongs.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed · +12 lines ca2a159d5e35
- 12d ago First seen · 61 lines · 63 tokens per session scan A c2619fda0a0e
tmux-agent-lane-orchestrator is a skill published in the GitHub repository vincentkoc/dotskills (102 stars, last pushed 2d ago), licensed MIT. It adds 63 tokens to every session and 692 once invoked, about $0.0003 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-30.
Other skills, from other repositories
taiyi-plan
A TaiyiForge planning step that turns a README, product requirements document, or technical plan into a list of separate project changes. Each change includes a suggested work profile, dependencies, and priority.
taiyi-integration
A project workflow skill for closing a TaiyiForge change and recording it in a CHANGELOG.md file. It checks review results, tests, and the state of the working tree before archiving the change.
taiyi-requirement
A requirements-analysis process that turns a proposed change into a REQUIREMENT.md document. It records user needs, acceptance checks, terminology, triggers, and dependencies, with different levels of detail for different project sizes.
security-compliance
Guides security professionals in implementing defense-in-depth security architectures, achieving compliance with industry frameworks (SOC2, ISO27001, GDPR, HIPAA), conducting threat modeling and risk assessments, managing security operations and incident response, and embedding security throughout the SDLC.
taiyi-change
A TaiyiForge workflow stage for writing a change proposal in CHANGE.md, with checks for scope, risks, success criteria, and related project documents.
taiyi-test
A project workflow skill for verifying an implementation and producing a TEST.md record. TDD means writing a failing test, implementing the change, and then making the test pass; this skill checks that process and other regression cases.