Maintainer of this skill?
Automated security scan — not a certification.
by marcuspat
The rules layer for AI-written code — rig-lite: a fail-closed cross-model review gate, a written constitution, git-versioned memory. Any harness, any repo. v1-4 were the agentic dev environment.
# Add to your Claude Code skills
git clone https://github.com/marcuspat/turbo-flowLast scanned: 5/30/2026
{
"issues": [],
"status": "PASSED",
"scannedAt": "2026-05-30T15:57:47.408Z",
"npmAuditRan": true,
"pipAuditRan": true
}See how turbo-flow compares with popular alternatives.
turbo-flow is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by marcuspat. The rules layer for AI-written code — rig-lite: a fail-closed cross-model review gate, a written constitution, git-versioned memory. Any harness, any repo. v1-4 were the agentic dev environment. It has 176 GitHub stars.
Yes. turbo-flow passed SkillsLLM's automated security scan — a dependency vulnerability audit plus prompt-injection heuristics — with no high-severity issues. You can read the full report in the Security Report section on this page.
Clone the repository with "git clone https://github.com/marcuspat/turbo-flow" and add it to your Claude Code skills directory (see the Installation section above).
turbo-flow is primarily written in Shell. It is open-source under marcuspat on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh turbo-flow against similar tools.
No comments yet. Be the first to share your thoughts!
30 days in the Featured rail · terms & refunds
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
Automated security scan — not a certification.
⚡ TURBO FLOW — THE RULES LAYER FOR AI-WRITTEN CODE. One product lives here:
rig-lite/— a portable governance kit. It ships no harness, installs nothing, and depends only on bash. Drop it into any repo and your agents get laws with teeth.
Turbo Flow is an open-source project by Adventure Wave Labs (Marcus Patman). Versions 1–4 (2025–2026) packaged an agentic development environment around Claude Code and Ruflo — at its peak, 215+ MCP tools and 60+ agents. In September 2026 the project pivoted to a thinner, governed approach, and by v5.2 (October 2026) the orchestration stack was fully removed: Turbo Flow is now the rules layer (rig-lite), and the integrated successor, Turbo Rig, runs in private beta. Site: turboflow.online · full story: why Turbo Flow became Turbo Rig · version history.
Turbo Flow bundles no agent and no orchestrator. It names harnesses by role, and works with any tool that reads AGENTS.md and can run bash:
| Role | Who | How the kit uses it |
|---|---|---|
| Builder | ZCode (GLM), Claude Code, Codex, Gemini, Grok | gate.sh --builder <cli> knows the family; anyone can build |
| Reviewer | Claude Code or Codex CLI — never the builder's family | the gate auto-detects and refuses same-family review |
| Orchestration (optional) | Ruflo, as a Claude Code mod | bring it if you want swarms — the kit doesn't care |
ZCode builds · Claude Code reviews (Ruflo mod installed when you want orchestration) · Codex backs up the review. That loop runs in production on this repo today: every PR since rig-lite landed (v5.0) was built by one family, reviewed by another, merged by a human.
A fresh Codespace from main (unauthenticated): the first shell triggers the boot (no menu), Claude Code + Codex + Ruflo install visibly, then tmux fires with all 5 windows — each landing inside its harness.
tf (one command for everything)
Recorded on the same Codespace: tf help shows every subcommand, tf status gives the at-a-glance view (repo, gate verdict counts, tree health), tf gate fails closed without --builder, tf tokens shows the live dashboard, and tf test runs the full suite. The tf command is installed automatically in Codespaces and by init-repo.sh anywhere else.
rig-lite/gate.sh was itself reviewed by a model family that didn't write it — and got REVISE'd seventeen times before earning APPROVED (counted from the gate's own JSONL log). The findings are exactly the class the gate exists to catch: a prompt-injection hole that let a diff approve itself, a fail-open path that skipped review entirely, a quoting bug that swallowed failing tests, a silent-reviewer misdiagnosis. Every fix became a self-test. Builder ≠ reviewer isn't a slogan in this repo — it's the reason this script is trustworthy.
| file | what it gives you |
|---|---|
tf |
one command for everything — tf gate, tf test, tf status, tf wt, tf secrets, tf tokens, tf digest, tf init, tf protect. Installed by init-repo.sh and by the Codespace boot. |
gate.sh |
a cross-model review gate — deterministic checks first (they're free), then a reviewer from a different model family must return a parseable APPROVED / REVISE. Fail-closed; never merges. --pr <n> gates a GitHub PR and posts the verdict as a comment; --sweep gates every open PR that has no verdict yet; -C <repo> gates another checkout. Every verdict lands in a local JSONL log the digest joins. |
protect.sh |
makes the gate a GitHub rule, not a promise: one command turns on branch protection with the gate's verdict as a required status check (gate-verdict, set by gate.sh on the exact SHA it reviewed), so main can't take an un-gated PR even by accident. It does not make merging human-only: --require-review demands an approving review (an account permission, not proof of who typed it), and any account with merge rights can still merge an approved PR — keeping merges human-only is an access-control decision (whose accounts hold merge rights) that protection can't make for you. --dry-run / --status to look before touching. Its companion workflow gate-check.yml re-checks on every push and, once the gate posts APPROVED, flips the PR's own check green by itself — fork PRs get the exact one-click re-run instead, because GitHub won't link their runs to the PR. |
wt.sh |
an isolated worktree per parallel writer: wt <name> creates .worktrees/<name> + branch, --clean tidies up after merge. |
init-repo.sh |
one-command onboarding for any repo: a thin AGENTS.md (constitution pointer + project cheat-sheet) and the CLAUDE.md → AGENTS.md symlink. Never clobbers existing files. |
specs/ |
the spec + UAT contract templates: plan before build, verify behavior against the deployed app. |
digest.sh |
one command, one file: repo health for your whole fleet — merge queue joined with gate verdicts, merged PRs, dirty/behind working copies, site liveness, stale codespaces, repo-hygiene gaps. |
automations/ |
the background tier as a portable prompt pack: 9 scheduled tasks (morning digest, security scan, memory consolidation, weekly retro, repo-hygiene pass, site sentinel, gate canary, portability canary, nightly sweep) plus two ways to schedule them. |
secret.sh |
encrypted-at-rest secrets, backend auto-detected (macOS Keychain → libsecret → age → loudly-warned chmod-600 plaintext). set/get/rm/list — listing shows names, never values; values never appear in ps. |
memory.md + memory/ |
the git-versioned memory pattern: index, decisions, gotchas, project index, inbox — agents forget, git doesn't. |
tokens.py |
live token-burn dashboard across zcode + claude + codex + gate — reads each CLI's local usage data read-only; --watch live view, --json, TZ-pinned fixture self-test covering every adapter (including malformed-shape rows). The first open-core drop from Turbo Rig. On macOS the default run also reads the Claude OAuth token from the Keychain and calls Anthropic's usage endpoint for plan bars — --no-quota skips both. |
hooks/pre-commit |
deletion guard: staged deletions print loudly instead of silently vanishing. Warn-only, fail-open. |
constitution.md |
the laws — builder ≠ reviewer, agents never merge, worktrees for parallel writers, secrets encrypted, state on disk. |
self-test.sh |
the kit's own fail-closed test suite (hundreds of checks); says so when shellcheck-gated coverage is skipped. |
# from any repo you want to govern:
bash /path/to/turbo-flow/rig-lite/init-repo.sh # writes AGENTS.md + installs tf, never clobbers
export PATH="$HOME/.local/bin:$PATH" # tf lives here (init warns if not on PATH)
tf test # prove the kit (322 checks)
tf gate --builder <your-cli> # gate your first change
tf status # everything at a glance
No Codespace? Fine — it's bash. Want the 30-second container tour anyway? Open this repo in a Codespace; postCreate runs the self-test and installs tf on PATH automatically. That's the whole install surface.
In a Codespace (or after running bash workspace.sh), you're inside a 5-window tmux session. Here's what to do:
Ctrl+B 0 → jump to the claude window, type /login (browser OAuth)
Ctrl+B 4 → jump to the shell, type codex login (browser); then Ctrl+B 2
After that, every window opens ready for work, forever on this box.
| Keys | What you see |
|---|---|
Ctrl+B 0 |
claude — reviewer when window 1 is claude-glm; otherwise use codex (window 2) to review |
Ctrl+B 1 |
builder — claude-glm if wired, else claude with ruflo plugins loaded |
Ctrl+B 2 |
codex — your OpenAI lane (ruflo reachable via MCP) |
Ctrl+B 3 |
tokens — live burn across all three harnesses, always updating |
Ctrl+B 4 |
shell — free bash for git, builds, anything |
Ctrl+B d |
detach (come back any time — the session survives) |
The tf command is installed automatically in Codespaces (and by init-repo.sh anywhere else). In the shell window (Ctrl+B 4), from any branch you or an agent built:
# prove the kit works:
tf test
# gate a branch — the builder names itself (--builder is required):
tf gate --builder claude # if claude wrote it → a non-Anthropic reviewer checks it
tf gate --builder glm # if claude-glm wrote it