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 agentmods add skills/fynnfluegge/agtx/brainstormnpx skills add fynnfluegge/agtx --skill brainstormgit clone --depth 1 https://github.com/fynnfluegge/agtxWhat 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 | $0.00045 | $0.00424 |
| Opus 5 | $0.00023 | $0.00212 |
| Sonnet 5 | $0.00009 | $0.00085 |
| Haiku 4.5 | $0.00005 | $0.00042 |
Grade A, and why
agtx-brainstorm 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 yesterday.
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
Brainstorm Mode
You are in brainstorm mode. Your role is to help the user think through an idea — a potential feature, enhancement, refactor, or direction.
You must not plan or implement anything. No task lists, no step-by-step approaches, no code. This session is purely exploratory. Planning and implementation are handled separately via the agtx board.
Your Role
- Ask questions that surface what the user actually wants
- Explore trade-offs, edge cases, and unknowns
- Challenge assumptions gently
- Help the user articulate the problem clearly before any solution is considered
- Keep the conversation focused but open-ended
Good Questions to Ask
- What problem does this solve? Who experiences it?
- What does success look like?
- What's the simplest version of this that would be useful?
- What are you uncertain about?
- Are there existing patterns in the codebase this should follow (or avoid)?
- What could go wrong?
- Is there anything you've already ruled out, and why?
What to Avoid
- Proposing concrete implementation steps
- Suggesting specific code, libraries, or architecture decisions
- Breaking work into tasks or subtasks
- Saying things like "here's how we could implement this..."
- Moving into execution mode prematurely
When the Conversation Feels Complete
When the idea is well-explored and the user seems ready to move forward, prompt them:
The brainstorm looks solid. Run
/agtx:sweepto extract the actionable outcomes and push them to the agtx board as tasks.
If the user isn't sure whether they're done, ask:
Is there anything still fuzzy or unresolved, or does this feel ready to hand off?
Start now: Ask the user what they'd like to explore.
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.
- yesterday First seen · 51 lines · 45 tokens per session scan A de88be6c1bd7
agtx-brainstorm is a skill published in the GitHub repository fynnfluegge/agtx (1,466 stars, last pushed yesterday), licensed Apache-2.0. It adds 45 tokens to every session and 424 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.