Borrowing it
Nothing to install: this file belongs to ttttmr/pi-tmux-task. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ttttmr/pi-tmux-task/main/AGENTS.mdgit clone --depth 1 https://github.com/ttttmr/pi-tmux-taskWrote 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/instructions/ttttmr/pi-tmux-task/agents-md)<a href="https://agentmods.dev/instructions/ttttmr/pi-tmux-task/agents-md"><img src="https://agentmods.dev/badge/instructions/ttttmr/pi-tmux-task/agents-md/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/instructions/ttttmr/pi-tmux-task/agents-md"><img src="https://agentmods.dev/badge/instructions/ttttmr/pi-tmux-task/agents-md.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.03041 | $0.03041 |
| Opus 5.5 | $0.01216 | $0.01216 |
| Sonnet 5.5 | $0.00608 | $0.00608 |
| Haiku 4.5 | $0.00304 | $0.00304 |
Grade A, and why
pi-tmux-task AGENTS.md 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 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.
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 — 267 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PROJECT KNOWLEDGE BASE
Generated: 2026-05-20
Updated: 2026-05-22
OVERVIEW
Project: pi-tmux-task
This repository is a Pi extension package for Pi-session-scoped background task management. It does not implement its own scheduler. Instead, it defines an agent-facing background-task convention and backs that convention with tmux plus extension-side observability.
Core product idea
-
Skill guidance for background task management
- Bundle a skill that teaches the agent when to treat work as a long-running background task instead of a foreground command.
- Standardize on one Pi session = one task tmux session and one logical task = one tmux window / task slot.
- Encourage meaningful task naming, reuse of the same task slot on rerun when possible, and follow-up by
window_idwhen precise low-level targeting is useful.
-
Code-level runtime support
- Compute a stable Pi-session-scoped tmux session name and inject it into bash calls as
PI_TMUX_SESSION. - Provide UI surfaces to inspect and manage tmux task windows.
- Poll tmux state, diff snapshots into semantic task events, and push plain-text notifications back into the active Pi conversation.
- Compute a stable Pi-session-scoped tmux session name and inject it into bash calls as
Current stack
- Language: TypeScript + ESM
- Runtime: Node.js
- Host framework:
@earendil-works/pi-coding-agent - UI:
@earendil-works/pi-tui - Shell integration: tmux + bash helper scripts
- Tests: lightweight Node/bash scripts under
test/
STRUCTURE
.
├── AGENTS.md
├── docs/
│ ├── architecture.md
│ └── tmux-task-event-flow.md
├── package.json
├── skills/
│ └── tmux-task-manager/
│ ├── SKILL.md
│ └── tmux-task-run.sh
├── src/
│ ├── context.ts
│ ├── index.ts
│ ├── types.ts
│ ├── tmux/
│ │ ├── commands.ts
│ │ ├── events.ts
│ │ ├── parse.ts
│ │ ├── poller.ts
│ │ └── snapshot.ts
│ └── ui/
│ └── tasks-panel.ts
└── test/
├── context.mjs
├── events.mjs
└── tmux-integration.sh
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 Changed · +2 lines · +166 tokens per session ceb068db6c1f
- 1mo ago First seen · 265 lines · 2,875 tokens per session scan A 893c08c13d51
pi-tmux-task AGENTS.md is an instructions file published in the GitHub repository ttttmr/pi-tmux-task (6 stars, last pushed 11d ago), licensed MIT. It adds 3,041 tokens to every session, about $0.0122 per session on Opus 5.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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.