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/gizclaw/flowcraft/flowcraft-confignpx skills add GizClaw/flowcraft --skill flowcraft-configgit clone --depth 1 https://github.com/GizClaw/flowcraftWrote 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/gizclaw/flowcraft/flowcraft-config)<a href="https://agentmods.dev/skills/gizclaw/flowcraft/flowcraft-config"><img src="https://agentmods.dev/badge/skills/gizclaw/flowcraft/flowcraft-config.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.1 | $0.00096 | $0.01604 |
| Opus 5 | $0.00048 | $0.00802 |
| Sonnet 5 | $0.00019 | $0.00321 |
| Haiku 4.5 | $0.00010 | $0.00160 |
Grade A, and why
flowcraft-config 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 2d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FlowCraft Config Authoring
Write complete FlowCraft deployment configuration: deploy.yaml, the
runtime section, resource sub-documents, and graph JSON. Validate with
the L2 structural validator and fix errors against the reference cards.
Workflow
- Scope the deployment. Collect the agents, capabilities (chat, tools, memory, scripts, sandboxing), and runtime needs (sessions, resume, event bus, checkpoint stores).
- Draft the deployment document.
deploy.yamlis the convention but any filename works; pass whatever path you choose to the validator. Read references/deploy.md first. Order the areas: resources → agents → runtime. Decide whole-resource vs item dep refs (infervsws/project). - Write sub-documents. Read
references/resources.md for the owning
module's schema. Workspace before sandbox (custom sandbox runners may
depend on workspace resources). Memory implementation modules are
app-registered — omit implementation examples;
core/memorycontracts and hooks are fine to use. - Write graph JSON. Read references/graph.md.
Prefer routing: wire the
inference.Routerinto the graph engine and omitmodelin inference nodes; pinmodelonly when no router is wired. Model refs must use the nestedidform; script nodes needruntimeandsource; wire edges back to the inference node after tool nodes. - Validate structurally with L2. Run
skills/flowcraft-config/scripts/validate-config.sh <deployment-file>(or the installed copy's script). The validator pins the FlowCraft core module in itsgo.modand works standalone from any directory. It is structural only: it strictly decodes the document throughcore/deploy.Parse(unknown fields are rejected, resource/agent entries are shape-checked), strictly decodes and validates theruntimesubtree throughcore/runtime.DecodeConfigwhen present, and structurally validates graph definitions throughcore/graph.GraphDefinition.Validate. It does not build resources: no factory registry, no settingsfile/embedresolution, no node config decoding, no credentials, and no provider calls. Custom and app-registered kinds pass as long as they fit the resource envelope; their settings semantics are the host build's job.
What ships with it
15 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- agents/openai.yaml 256 B
- assets/minimal-deploy/deploy.yaml 783 B
- assets/minimal-deploy/graphs/assistant.json 451 B
- assets/minimal-deploy/inference.yaml 200 B
- assets/minimal-deploy/workspace.yaml 218 B
- assets/minimal-deploy/workspace/.gitkeep 1 B
- references/deploy.md 4.2 KB
- references/graph.md 16 KB
- references/pitfalls.md 5.1 KB
- references/resources.md 12 KB
- references/runtime.md 4.5 KB
- scripts/validate-config.sh 645 B runs code
- scripts/validator/go.mod 1.9 KB
- scripts/validator/go.sum 8.5 KB
- scripts/validator/main.go 2.5 KB
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.
- 2d ago Changed bbab33133e7a
- 6d ago First seen · 128 lines · 96 tokens per session scan A 6635f5b378d3
flowcraft-config is a skill published in the GitHub repository GizClaw/flowcraft (415 stars, last pushed yesterday), licensed MIT. It adds 96 tokens to every session and 1,604 once invoked, about $0.0005 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
fetch-tweets
Search and curate X/Twitter behind one selector - keyword, topic roundup, a single or tracked-account digest, an X list, or the AI-agent buzz preset - clustered into signal-scored sub-narratives.
operator-scorecard
Three recap modes - default synthesizes agent health, community growth, and economic activity into a was-it-worth-it verdict; ops recaps what shipped and failed; push ranks push impact.
token-movers
Crypto market scanner and single-token analyst - movers scans top winners/losers/trending or on-chain runners with pump-risk flags; single-token produces a verdict-first deep report for one token.
vuln-tracker
One lifecycle poll over everything vuln-scanner produces - PR and advisory status, PVR triage transitions, and pending-disclosure aging, with a stars-secured impact headline and one action queue.
article
Write a publication-ready article in one of three angles - a trending long-form piece, a watched-repo thesis, or a project-through-a-lens essay. Optional Replicate hero image with --visual.
auto-workflow
Two-mode aeon.yml workflow builder - analyze inspects URLs and emits a tiered, signal-verified skill-enablement plan plus an aeon.yml diff; enable flips slugs to enabled:true and opens a PR.