Borrowing it
Nothing to install: this file belongs to radiantlogicinc/fastworkflow. 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/radiantlogicinc/fastworkflow/main/.claude/skills/fastworkflow-change-control/SKILL.mdgit 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/fastworkflow-change-control)<a href="https://agentmods.dev/skills/radiantlogicinc/fastworkflow/fastworkflow-change-control"><img src="https://agentmods.dev/badge/skills/radiantlogicinc/fastworkflow/fastworkflow-change-control.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.00176 | $0.06732 |
| Opus 5 | $0.00088 | $0.03366 |
| Sonnet 5 | $0.00035 | $0.01346 |
| Haiku 4.5 | $0.00018 | $0.00673 |
Grade A, and why
fastworkflow-change-control 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 7d 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 — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
fastWorkflow Change Control
TEAM-PRIVATE: embeds content from uncommitted internal docs. Do not commit or publish this skill without the developer'sexplicit approval.
How changes are classified, gated, reviewed, versioned, and released in this repo — and the four non-negotiable rules, each earned through a real incident. This is policy inferred from what actually happened in git history and the beads tracker, not aspiration.
Jargon, defined once:
- bd / beads — the git-backed issue tracker used here (
bdCLI; source of truth is.beads/issues.jsonl). Issue IDs look likefix-vof, children likefix-vof.1. - Epic — a bd issue of type
epicwith child issues. - tau-bench / tau2-bench (τ²-bench) — public customer-service agent benchmarks this project reports scores on. "Parity" = running under standard, unmodified benchmark conditions.
- Design doc of record — a markdown file in
docs/that a change was reviewed against (e.g.docs/turn_result_design_final.md). - Adversarial review — a structured pass where reviewers (here: parallel AI review agents) attack a design and every finding gets a written resolution.
1. When to use / when NOT to use
Use this skill when deciding whether and how a change may land: commit/push etiquette, bd workflow, design-review gating, version bumps, test removal, and what may never enter the public repo.
| Your actual need | Use instead |
|---|---|
| Why the architecture is shaped this way; invariants | fastworkflow-architecture-contract |
| Triage a runtime/build/train failure | fastworkflow-debugging-playbook |
| History of past investigations and dead ends | fastworkflow-failure-archaeology |
| What counts as test evidence; adding tests | fastworkflow-validation-and-qa |
| Env vars / CLI flags catalog | fastworkflow-config-and-flags |
| Running the CLI / server / examples | fastworkflow-run-and-operate |
| tau-bench mechanics and our published claims | fastworkflow-taubench-reference |
| Executing the tau2 E0–E25 campaign itself | tau2-reliability-campaign |
| Doc style, publication boundaries, external claims | fastworkflow-docs-and-positioning |
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.
- 7d ago First seen · 231 lines · 176 tokens per session scan A 9859f93f4c1b
fastworkflow-change-control is a skill published in the GitHub repository radiantlogicinc/fastworkflow (52 stars, last pushed 3d ago), licensed Apache-2.0. It adds 176 tokens to every session and 6,732 once invoked, about $0.0009 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
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
codex-autoresearch
Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".