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 skills/wavyrai/tmux-ide/skillnpx skills add wavyrai/tmux-ide --skill skillgit clone --depth 1 https://github.com/wavyrai/tmux-ideWrote 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/wavyrai/tmux-ide/skill)<a href="https://agentmods.dev/skills/wavyrai/tmux-ide/skill"><img src="https://agentmods.dev/badge/skills/wavyrai/tmux-ide/skill.svg" alt="Measured on agentmods" 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.00000 | $0.04471 |
| Opus 5 | $0.00000 | $0.02235 |
| Sonnet 5 | $0.00000 | $0.00894 |
| Haiku 4.5 | $0.00000 | $0.00447 |
Grade B, and why
skill 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 6d 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.
writes a POSIX hook into `~/.claude/settings.json` that stamps `@agent_state` on How it starts
The opening of the file, as written. The whole thing — 364 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tmux-ide — Claude Code Skill
tmux-ide is a dock around tmux: one command adds a native chrome to any tmux
session — a fleet of tabs with live agent-status glyphs, ground-truth
working/blocked/done detection, notifications when an agent needs a human, and a
crash-proof restore. It's built around tmux (adopt is additive tmux config, no
wrapper process), and the whole UI is one keystroke away — one interaction
grammar, one theme file. .tmux-ide/workspace.yml is optional; adopt works on any session.
When to use
- User mentions tmux, a dock/status bar over sessions, an agent fleet, or session status
- User wants live working/blocked/done status across multiple agents or panes
- You are an agent and want to report your own status so the dock/fleet reflects it (the agent contract, below)
- Post-crash recovery — a tmux server died and the user wants their fleet + Claude conversations back
- User wants a git worktree (plus an adopted session) per branch
- User wants to set up a multi-pane dev workspace with
.tmux-ide/workspace.yml
The agent contract
This is the core of tmux-ide. Detection is two-layer, and an agent that reports its own state is the authoritative layer — the dock trusts it over any screen-scraping. If you are an agent running in a tmux pane, self-report by setting a pane-local tmux option:
tmux set-option -p @agent_state "<state>:$(date +%s)" # state = working | blocked | done | idle
The value is <state>:<unix-epoch>. A working/blocked report older than ~10
minutes is treated as stale (the detector falls back to Layer 2), so long-running
agents should re-stamp periodically. Two optional companions:
tmux set-option -p @agent_session_id "<id>" # your own session id — powers restore --resume-agents
tmux set-option -p @agent_hint claude # force which agent manifest Layer 2 uses for this pane
Display metadata — say WHAT you're doing and WHO you are, right in the fleet UI. Two more optional pane-local options:
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.
- 6d ago First seen · 364 lines · 0 tokens per session scan B a71804feda09
skill is a skill published in the GitHub repository wavyrai/tmux-ide (543 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,471 tokens. 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-30.
Other skills, from other repositories
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.