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 phuongduyphan/cc-tmux-agents --skill cursorgit clone --depth 1 https://github.com/phuongduyphan/cc-tmux-agentsWrote 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/phuongduyphan/cc-tmux-agents/cursor)<a href="https://agentmods.dev/skills/phuongduyphan/cc-tmux-agents/cursor"><img src="https://agentmods.dev/badge/skills/phuongduyphan/cc-tmux-agents/cursor/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/phuongduyphan/cc-tmux-agents/cursor"><img src="https://agentmods.dev/badge/skills/phuongduyphan/cc-tmux-agents/cursor.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.00037 | $0.01502 |
| Opus 5 | $0.00018 | $0.00751 |
| Sonnet 5 | $0.00007 | $0.00300 |
| Haiku 4.5 | $0.00004 | $0.00150 |
Grade A, and why
cursor 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 9d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
$cursor — delegate to Cursor Agent CLI
Spawns Cursor Agent's TUI in a detached tmux session so Codex can offload work to it. The user stays in the loop: they ask Codex when to check progress, what guidance to send, and when to stop.
Primitive
All operations go through a single dispatcher:
~/.agents/skills/cursor/bin/cursor-agent [--session <name>] <verb> [args]
Verbs:
start [task...]— create session (defaultcodex-cursor), launchagent --force, type the task and press Enter. Returns immediately (non-blocking).send <message>— type message + Enter. For follow-up guidance. Does not interrupt current generation; Cursor Agent queues the input.keys <name>— send a raw tmux key (Escape,C-c,Enter, etc.). Used for interrupts.capture [lines]— print last N ANSI-stripped rendered lines (default 500). Read-only, non-destructive.wait [stable] [timeout]— block until the agent goes idle, then exit. Run it in the foreground to block until the sub-agent finishes (the mode for Codex and other CLI orchestrators; see "Wait for completion" below).stable= secs the working indicator must stay gone before declaring idle (default 6);timeout= overall cap in secs (default 1800).stop— kill-session. Destroys the tmux session.list— list activecodex-cursor*sessions.
How to respond to the user
| User says | Do |
|---|---|
$cursor <task> / "delegate to cursor" |
start <task>, then run wait in the foreground (blocks this turn until cursor is idle); on return, capture + report. |
$cursor <task> + "tell me when it's done" / "notify me" |
Same as $cursor <task>; foreground wait is already the default. |
| "check cursor" / "progress" / "what's cursor doing" / "ask cursor for progress" | capture. Show the relevant tail, add a one-line diagnosis (running / idle / error / prompt). Do not send ESC. |
| "interrupt cursor" / "esc cursor" | keys Escape → capture. |
| "tell cursor: X" / "send cursor: X" | send X. |
| "kill cursor" / "stop cursor" | stop. |
What ships with it
1 file 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.
- 9d ago First seen · 84 lines · 37 tokens per session scan A a2d397e021d5
cursor is a skill published in the GitHub repository phuongduyphan/cc-tmux-agents (8 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 1,502 once invoked, about $0.0002 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 skills, from other repositories
repo-hygiene
Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.
find-simplifications
Use for a periodic repo-wide sweep of qwen-code for accumulated excess surface — dead components and files, orphaned locale keys, exports nothing consumes, added-then-removed scaffolding — filing candidates on a tracking issue and landing only what a maintainer has said yes to. Repo-wide and evidence-first; every…
autoprompt
Explicit-only useful-first orchestration. Invoke only when the user names autoprompt - typed as /autoprompt or in plain language such as "act in autoprompt mode" - to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Do not infer invocation from…
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.
ap-execharness-resolver
L3 executor - EXECHARNESS RESOLVE. Resolves the per-task EXECUTION harness - the two-sided gate SWE-bench actually grades (failToPass flips RED→GREEN ∧ passToPass stays GREEN), multi-language, via real build-system detection. Ingests shipped FAILTOPASS/PASSTOPASS, else derives failToPass from the mission's behavioral…