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 radiantlogicinc/fastworkflow --skill create-workflow-benchmarksgit clone --depth 1 https://github.com/radiantlogicinc/fastworkflowWrote 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/radiantlogicinc/fastworkflow/create-workflow-benchmarks)<a href="https://agentmods.dev/skills/radiantlogicinc/fastworkflow/create-workflow-benchmarks"><img src="https://agentmods.dev/badge/skills/radiantlogicinc/fastworkflow/create-workflow-benchmarks/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/radiantlogicinc/fastworkflow/create-workflow-benchmarks"><img src="https://agentmods.dev/badge/skills/radiantlogicinc/fastworkflow/create-workflow-benchmarks.svg" alt="Reviewed on agentmods" width="80" 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.00063 | $0.01566 |
| Opus 5.5 | $0.00025 | $0.00626 |
| Sonnet 5.5 | $0.00013 | $0.00313 |
| Haiku 4.5 | $0.00006 | $0.00157 |
Grade A, and why
create-workflow-benchmarks 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 9d 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create workflow benchmarks and tasks
A benchmark defines repeatable work; its tasks have stable IDs. An experiment records attempts against a specific benchmark version. Creating either in the UI does not execute the workflow.
Author in run_chatbot
Start fastworkflow run_chatbot, select the application workflow, then open Benchmark setup.
Use the printed authenticated local URL. Selecting a workflow normally starts its server; reuse
an existing session when only authoring or reviewing. Follow the project's runtime permissions.
- Choose New benchmark, enter a title and optional description, and add task rows. Each task's prompt is optional: a runner can supply the actual messages later.
- Save benchmark assigns the benchmark ID,
v1, and new task IDs. Keep those identities when adding execution code; do not derive task IDs from conversation topics. - Edit benchmark saves a new immutable version. Existing task IDs are retained; new rows receive new IDs. Removing a row removes it only from the new version.
- Select the intended version, then New experiment. Copy the generated experiment ID and task IDs to the driver. This creates a registration, initially without an evidence store.
- Once the driver records execution, use Open execution records to inspect it.
The left navigation is benchmark → experiment → conversation. Ad-hoc conversations appear under ad-hoc conversations → UTC date → conversation. Node clicks show details on the right and expand/collapse the left tree. Turns and trace components are inspected on the right; only the right pane shows the complete breadcrumb. Tasks are listed in benchmark/experiment details, not as another required left-tree level. Sidebar filters and the old Experiments/ Benchmarks navigation buttons are no longer part of this flow.
Author the same objects from Python
For the UI's simple title/prompt model, use the setup API:
from fastworkflow.benchmark import setup as benchmark_setup
version = benchmark_setup.save_benchmark(workflow_folderpath, {
"title": "Order support regressions",
"description": "Lookup, ambiguity and recovery using disposable test orders",
"tasks": [{"prompt": "Show the delivery status of my most recent order."}],
})
registration = benchmark_setup.create_experiment(
workflow_folderpath, version["benchmark_id"], version["version"]
)
experiment_id = registration["experiment_id"]
task_ids = registration["task_ids"]
What ships with it
1 file 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.
- 9d ago Changed e8752fbe1baf
- 11d ago Changed 35c18a26e53e
- 1mo ago First seen · 139 lines · 63 tokens per session scan A cb4d07b2e470
create-workflow-benchmarks is a skill published in the GitHub repository radiantlogicinc/fastworkflow (52 stars, last pushed 5d ago), licensed Apache-2.0. It adds 63 tokens to every session and 1,566 once invoked, about $0.0003 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-09-11.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.