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 flc1125/skills --skill design-workflow-graphsgit clone --depth 1 https://github.com/flc1125/skillsWrote 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/flc1125/skills/design-workflow-graphs)<a href="https://agentmods.dev/skills/flc1125/skills/design-workflow-graphs"><img src="https://agentmods.dev/badge/skills/flc1125/skills/design-workflow-graphs/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/flc1125/skills/design-workflow-graphs"><img src="https://agentmods.dev/badge/skills/flc1125/skills/design-workflow-graphs.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.00095 | $0.02161 |
| Opus 5 | $0.00048 | $0.01081 |
| Sonnet 5 | $0.00019 | $0.00432 |
| Haiku 4.5 | $0.00010 | $0.00216 |
Grade A, and why
design-workflow-graphs 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 8d 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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Workflow Graphs
Design workflow graphs as explicit engineering contracts rather than decorative diagrams. Make control flow, state mutation, termination, failure behavior, and side effects reviewable before choosing an execution framework.
Operating Principles
- Start from the objective, state, and termination contract; do not start by inventing agents or nodes.
- Use a graph only when branching, parallelism, bounded iteration, durable recovery, approval gates, or independently observable stages justify it.
- Prefer a linear workflow or one bounded agent loop when it is sufficient.
- Keep deterministic control in edges, guards, budgets, and validation. Use model reasoning inside nodes only where judgment is required.
- Give each state field and side effect an owner.
- Bound every cycle by attempts, elapsed time, cost, or another measurable budget.
- Place irreversible side effects after validation and approval whenever possible.
- Keep the core design framework-neutral. Map it to a runtime only after the graph contract is stable.
Resource Map
Load only what the request needs:
- For field definitions and invariants, read references/graph-model.md.
- For reusable topologies, read references/graph-patterns.md.
- For audits or final design review, read references/review-checklist.md.
- To create a machine-readable artifact, copy assets/graph-spec.json and adapt it.
- To validate a Graph Spec, run
python3 scripts/validate_graph_spec.py --strict path/to/graph.json.
Choose the Work Mode
Choose one primary mode and state it when the distinction affects the deliverable:
design: Create a new workflow graph from goals and constraints.transform: Convert a linear process, implicit agent loop, or prose procedure into an explicit graph.review: Find structural, state, concurrency, recovery, termination, and side-effect defects in an existing graph.evolve: Revise a graph using observed failures, traces, evaluation results, or changed requirements.
What ships with it
6 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.
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.
- 8d ago First seen · 204 lines · 95 tokens per session scan A 05871c56734e
design-workflow-graphs is a skill published in the GitHub repository flc1125/skills (36 stars, last pushed yesterday), licensed MIT. It adds 95 tokens to every session and 2,161 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
gemini
Use when the user requests to run Gemini CLI for code analysis, refactoring, or automated editing.
superlint
This skill describes the mandatory standard operating procedure for using our internal SuperLint tool. Use this when tasks require fixing code quality issues according to corporate standards.
iflytek-hyper-tts
A text-to-speech tool that turns written text into an MP3 recording. It can use an authorized voice and adjust speaking speed, volume, and pitch.
iflytek-pdf-image-ocr
AI-powered OCR service for images and PDF documents using iFlytek's advanced recognition APIs.
iflytek-translate
A text-translation tool that uses iFlytek's machine-translation service and supports more than 70 language pairs. It can translate text supplied directly, through standard input, or from a file.
iflytek-contract-intelligence-review
A contract-review workflow for scanned or digital agreements. It can recognize document text, examine clauses, detect risks, check compliance, and create translation summaries; its output is for review and is not formal legal advice.