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/dosco/aithy/ax-flownpx skills add dosco/aithy --skill ax-flowgit clone --depth 1 https://github.com/dosco/aithyWrote 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/dosco/aithy/ax-flow)<a href="https://agentmods.dev/skills/dosco/aithy/ax-flow"><img src="https://agentmods.dev/badge/skills/dosco/aithy/ax-flow.svg" alt="Measured on agentmods" 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 | $0.00059 | $0.06679 |
| Opus 5 | $0.00030 | $0.03340 |
| Sonnet 5 | $0.00012 | $0.01336 |
| Haiku 4.5 | $0.00006 | $0.00668 |
Grade A, and why
ax-flow 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 today.
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 — 687 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AxFlow Codegen Rules (@ax-llm/ax)
Use this skill to generate AxFlow workflow code. Prefer short, modern, copyable patterns. Do not write tutorial prose unless the user explicitly asks for explanation.
Use These Defaults
- Use
flow()factory, notnew AxFlow(). - Import:
import { ai, flow, f } from '@ax-llm/ax'; autoParallel: trueis the default; independent executes and derives run in parallel when their metadata reads/writes are known and non-conflicting.- Node results are stored as
${nodeName}Resultin state. - Always define
.node()before.execute()for that node. - Use
.returns()(or.r()) as the last step to lock the output type. - Use descriptive node names:
documentSummarizer, notproc1. - Use descriptive field names:
userInput,responseText, nottext,result.
Critical Rules
- Use
flow()factory syntax for new code. - Node results in state follow the pattern
state.${nodeName}Result.${fieldName}. .execute()maps current state to node inputs;.map()transforms state without AI calls..returns()maps final state to the flow output type.- Always define nodes before executing them; reversed order throws at runtime.
- Keep state flat; avoid deep nesting in
.map(). - Ensure loop conditions can change to avoid infinite loops.
- Structure independent executes to maximize safe auto-parallelization.
- Use
flow<InputType, OutputType>()for typed flows. - Aliases:
.n()=.node(),.nx()=.nodeExtended(),.m()=.map(),.r()=.returns().
Canonical Pattern
import { ai, flow } from '@ax-llm/ax';
const llm = ai({ name: 'openai', apiKey: process.env.OPENAI_APIKEY! });
const wf = flow<{ userInput: string }, { responseText: string }>()
.node('testNode', 'userInput:string -> responseText:string')
.execute('testNode', (state) => ({ userInput: state.userInput }))
.returns((state) => ({ responseText: state.testNodeResult.responseText }));
const result = await wf.forward(llm, { userInput: 'Hello world' });
console.log(result.responseText);
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.
- today Changed · +244 lines 674be774b2d8
- 4d ago First seen · 443 lines · 59 tokens per session scan A a7950219f9d0
ax-flow is a skill published in the GitHub repository dosco/aithy (107 stars, last pushed 3d ago), licensed Apache-2.0. It adds 59 tokens to every session and 6,679 once invoked, about $0.0003 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
worker-mcp-orchestrator
Guides the coordinator agent on how to orchestrate, delegate to, and supervise local worker agents using the worker-mcp server.
research-assistant
Conduct deep, multi-source research on technologies, companies, markets, and topics — synthesizing findings into structured reports with citations and actionable insights.
code-review
Analyze pull requests and diffs for bugs, security vulnerabilities, performance issues, style violations, and test coverage gaps — producing structured, actionable feedback.
customer-support
Triage incoming support tickets, draft responses, detect customer sentiment, suggest knowledge base articles, and track resolution metrics.
fleet-orchestration
Decompose a large task into DISJOINT file-owned workstreams, fan out isolated full-power peers, collect structured reports, run ONE authoritative gate, and commit when green — the collision-free, self-verifying multi-agent flow. Ultra-gated.
content-writer
Draft blog posts, social media content, email campaigns, and marketing copy.