Borrowing it
Nothing to install: this file belongs to dosco/aithy. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dosco/aithy/main/.claude/skills/ax-flow/SKILL.mdgit 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/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/dosco/aithy/ax-flow"><img src="https://agentmods.dev/badge/skills/dosco/aithy/ax-flow.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.00059 | $0.06679 |
| Opus 5.5 | $0.00024 | $0.02672 |
| Sonnet 5.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 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 — 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.
- 1mo ago Changed · +244 lines 674be774b2d8
- 1mo ago First seen · 443 lines · 59 tokens per session scan A a7950219f9d0
ax-flow is a skill published in the GitHub repository dosco/aithy (108 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 59 tokens to every session and 6,679 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-08-30.
Other skills, from other repositories
offensive-vuln-classes
Exploit development curriculum covering core vulnerability classes with real-world CVE case studies: stack/heap buffer overflows, use-after-free, integer overflows, format strings, type confusion, and race conditions. Use when learning or teaching vuln classes, researching specific CVE patterns, or building exploit…
offensive-crypto-attacks
Systematic methodology for identifying and exploiting cryptographic implementation weaknesses in real-world applications. Covers padding oracle attacks against CBC-mode ciphers with PKCS7 padding (Vaudenay's original attack through modern padbuster automation), ECB mode exploitation including block cut-and-paste and…
offensive-phishing
Phishing campaign execution methodology for authorized red team engagements. Covers end-to-end campaign lifecycle: infrastructure provisioning (GoPhish, SMTP relay configuration, domain acquisition and aging, SPF/DKIM/DMARC alignment), payload delivery vectors (Office macro weaponization, HTA droppers, ISO/IMG…
offensive-social-engineering
Social engineering attack techniques beyond email phishing for authorized red team and physical penetration testing engagements. Covers pretexting methodology (persona creation, authority and urgency psychological triggers, rapport building), vishing (voice phishing via caller ID spoofing, IVR system exploitation…
offensive-parameter-pollution
HTTP parameter pollution (HPP) checklist: duplicate parameter injection, backend vs frontend parsing differences, WAF bypass via HPP, server-side vs client-side HPP, and practical exploitation patterns. Use when testing web applications for parameter handling flaws.
research-assistant
Conduct deep, multi-source research on technologies, companies, markets, and topics — synthesizing findings into structured reports with citations and actionable insights.