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-researchgit 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-research)<a href="https://agentmods.dev/skills/fynnfluegge/agtx/agtx-research"><img src="https://agentmods.dev/badge/skills/fynnfluegge/agtx/agtx-research/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-research"><img src="https://agentmods.dev/badge/skills/fynnfluegge/agtx/agtx-research.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.00041 | $0.00365 |
| Opus 5 | $0.00020 | $0.00182 |
| Sonnet 5 | $0.00008 | $0.00073 |
| Haiku 4.5 | $0.00004 | $0.00036 |
Grade A, and why
agtx-research 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 11d 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
Research Phase
You are in the research phase of an agtx-managed task. This is a read-only exploration.
Input
The argument to this command is a task ID. Fetch the task description using the agtx MCP tool:
mcp__agtx__get_task(task_id: "<the id passed to this command>")
Use the description field as the task to work on.
Instructions
- Fetch the task description via
get_task - Explore the codebase to find relevant files, patterns, and architecture
- Identify dependencies, related code, and potential complexity
- Assess feasibility and estimate scope
Output
Write your findings to .agtx/research.md. Include:
Relevant Files
Key files and their roles — what exists, what needs changing.
Architecture
How the relevant parts of the codebase fit together.
Complexity
Assessment of scope — simple change, moderate refactor, or major undertaking.
Open Questions
Things that need clarification before planning can begin.
CRITICAL: Do Not Modify Code
This is a read-only exploration:
- Do NOT modify any source files
- Do NOT create branches or worktrees
- Do NOT start planning or implementing
- Say: "Research complete. Findings written to .agtx/research.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.
- 11d ago First seen · 54 lines · 41 tokens per session scan A 76cd89c4d941
agtx-research is a skill published in the GitHub repository fynnfluegge/agtx (1,503 stars, last pushed today), licensed Apache-2.0. It adds 41 tokens to every session and 365 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-30.
Other skills, from other repositories
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-new-track
Plans a new track (feature or bug fix), generates spec/plan documents, and updates the registry.
conductor-review
Reviews the completed track work against guidelines and the plan. Acts as a Principal Software Engineer to ensure quality and compliance.
conductor-implement
Executes the tasks defined in the specified track's plan. Use this to start or continue working on a feature, bug fix, or chore.
conductor-revert
Reverts previous work (tracks, phases, or tasks) by identifying associated commits and performing Git reverts.
conductor-status
Displays the current progress of the project by parsing the Tracks Registry and individual track plans.