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 agtx-executegit 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/agtx-execute)<a href="https://agentmods.dev/skills/fynnfluegge/agtx/agtx-execute"><img src="https://agentmods.dev/badge/skills/fynnfluegge/agtx/agtx-execute/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/agtx-execute"><img src="https://agentmods.dev/badge/skills/fynnfluegge/agtx/agtx-execute.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00029 | $0.00426 |
| Opus 5.5 | $0.00012 | $0.00170 |
| Sonnet 5.5 | $0.00006 | $0.00085 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
agtx-execute 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.
What it actually says
Execution Phase
You are in the execution phase of an agtx-managed task.
Input
The argument to this command is a task ID.
If .agtx/plan.md exists in the current working directory, read it — it already contains the approved plan and all needed context. Do NOT call get_task.
If .agtx/plan.md does not exist, fetch the task description:
mcp__agtx__get_task(task_id: "<the id passed to this command>")
Instructions
- Read
.agtx/plan.mdif it exists (skipget_task), otherwise fetch viaget_task - Implement the changes
- Run relevant tests to verify your changes
- Fix any issues found during testing
- Commit.
git add -A, commit with a short imperative message, verifygit status --shortclean. Your worktree is deleted at task completion — uncommitted work is destroyed and the merge is blocked. agtx's own files are already git-excluded, soadd -Atakes only your work.
Output
When implementation is complete, write a summary to .agtx/execute.md in the current working directory with these sections:
Changes
What files were modified/created and what was changed in each.
Testing
How you verified the changes — tests run, results, manual checks.
CRITICAL: Stop After Writing
After writing .agtx/execute.md (in the current working directory):
- Do NOT start new work beyond the plan
- Say: "Implementation complete. Summary written to
.agtx/execute.md." - Wait for further instructions
Output Style
Terse. No pleasantries. Fragments OK. Short synonyms. Code exact. Status updates: one line. Pattern: [what] [why]. Done.
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 · +1 lines 8434041bfc9e
- 1mo ago First seen · 49 lines · 29 tokens per session scan A 6d87e6e3b346
agtx-execute is a skill published in the GitHub repository fynnfluegge/agtx (1,723 stars, last pushed 5d ago), licensed Apache-2.0. It adds 29 tokens to every session and 426 once invoked, about $0.0001 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-30.
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-setup
Scaffolds the project and sets up the Conductor environment. Use this whenever a project needs to be initialized or if the Conductor configuration is missing.
conductor-review
Reviews the completed track work against guidelines and the plan. Acts as a Principal Software Engineer to ensure quality and compliance.
delegation-core
Delegates execution to eight CLIs (Gemini, Qwen, MiniMax, GLM, Muse, Codex, OpenCode, Glimmer). Use for execution tasks. Do not use for secrets.
cmux-architecture
Skill "cmux-architecture" from manaflow-ai/cmux, covering cmux architecture, package architecture, layers, file organization and documentation.
cmux-cua
Use only after the user explicitly asks for cmux Computer Use through the cmux-cua skill: drive real macOS apps from a cmux agent session via the bundled engine (accessibility tree + screenshots, click/type/scroll/drag, branded cursor), or explain its user-directed permission setup. Reading or discovering this skill…