agtx is a terminal-based shared workspace where multiple coding agents coordinate through a task board. Developers use it to delegate work, run agents in parallel across git worktrees, and move tasks through different workflow phases.
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 fynnfluegge/agtx --skill oneshotgit clone --depth 1 https://github.com/fynnfluegge/agtxWrote 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/fynnfluegge/agtx/oneshot)<a href="https://agentmods.dev/skills/fynnfluegge/agtx/oneshot"><img src="https://agentmods.dev/badge/skills/fynnfluegge/agtx/oneshot/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/fynnfluegge/agtx/oneshot"><img src="https://agentmods.dev/badge/skills/fynnfluegge/agtx/oneshot.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.00051 | $0.03770 |
| Opus 5.5 | $0.00020 | $0.01508 |
| Sonnet 5.5 | $0.00010 | $0.00754 |
| Haiku 4.5 | $0.00005 | $0.00377 |
Grade A, and why
agtx-oneshot 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 — 289 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agtx — One-Shotting a Project
You are one-shotting a project on an agtx kanban board: a goal too large for one session, run to completion unattended. Ordinarily a person sits at the board and does this. Here, you are that person.
This is not the built-in orchestrator (O), which only advances Planning → Running →
Review and refuses to touch Backlog. You own all five columns: you decompose the
goal into tasks, decide what starts, watch the workers, unblock them, judge Review, and
merge. The workers do the coding; you never write feature code yourself.
Backlog → Planning → Running → Review → Done
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
all of it is yours
Before anything else: verify the board is live
Nothing you do executes unless the agtx TUI is running. move_task writes a row to
a queue; the TUI drains it and performs the real work — worktree creation, agent spawn,
skill deployment. With no TUI, every transition sits pending forever and the board looks
frozen for no visible reason.
- Call
list_projectsand take theproject_idof this project; pass it to every other agtx tool. If the MCP server does not answer, tell the user to register it and stop:
If this project is not listed, it has never been opened in agtx — ask the user to runclaude mcp add --scope user agtx -- agtx mcp-serveagtxin the project root, which is needed anyway (below). Then calllist_tasks. - Check
tui_connectedin that response. If it isfalse, no TUI is draining the queue — ask the user to openagtxin another terminal on this project, and do not queue anything into a dead board.
Also confirm before a long unattended run:
- Call
get_configand checkauto_trust. It must betrue, or agents' trust and bypass-permission dialogs are detected but left unanswered and every task parks as Blocked waiting for a human who is not there. Use the tool — do not read~/.config/agtx/config.tomlyourself:AGTX_CONFIG_DIRrelocates that file, so the path is not authoritative and you will get a stale answer.get_configalso tells you which file to edit.auto_trustis global-only, so a project config cannot turn it on. - Open the coding agent once in the project root and accept its trust prompt before starting. Your own session parks on that dialog in a directory the agent has not seen, and an unattended run has nobody to answer it.
- The project has a base branch and a clean tree.
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 First seen · 289 lines · 51 tokens per session scan A 9244bf979802
agtx-oneshot is a skill published in the GitHub repository fynnfluegge/agtx (1,715 stars, last pushed 14d ago), licensed Apache-2.0. It adds 51 tokens to every session and 3,770 once invoked, about $0.0002 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-09-14.
Other skills, from other repositories
conductor-new-track
Plans a new track (feature or bug fix), generates spec/plan documents, and updates the registry.
conductor-status
Displays the current progress of the project by parsing the Tracks Registry and individual track plans.
Mochi-a-pm
Use this skill when the user or another AI needs project management, task tracking, priority assignment, timeline planning, or progress review. Mochi is a cute but deadly serious project manager AI.
quality
Evaluates whether a GitHub issue is spam, empty, needs more information, or is OK to proceed.
multi-agent
A process for coordinating multiple coding agents by splitting work among scouts, workers, reviewers, and repair agents. Each agent has a defined role and task.
gsd-new-project
Initialize a new project with deep context gathering and PROJECT.md.