Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add gmickel/flow-next/plugin install flow-nextWrote 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/gmickel/flow-next/flow-next-ralph-init)<a href="https://agentmods.dev/skills/gmickel/flow-next/flow-next-ralph-init"><img src="https://agentmods.dev/badge/skills/gmickel/flow-next/flow-next-ralph-init.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.00027 | $0.03737 |
| Opus 5 | $0.00014 | $0.01869 |
| Sonnet 5 | $0.00005 | $0.00747 |
| Haiku 4.5 | $0.00003 | $0.00374 |
Grade C, and why
flow-next-ralph-init scanned grade C with 1 finding 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 yesterday.
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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf scripts/ralph/flowctl_tracker && cp -R "$PLUGIN_ROOT/scripts/flowctl_tracker" scripts/ralph/flowctl_tracker How it starts
The opening of the file, as written. The whole thing — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ralph init
Scaffold or update repo-local Ralph harness. Opt-in only.
Preamble
The plugin root resolves once via the cross-platform env-var fallback (Droid uses DROID_PLUGIN_ROOT; Claude Code documents CLAUDE_PLUGIN_ROOT as its compat alias). Subsequent blocks use $PLUGIN_ROOT:
PLUGIN_ROOT="${CODEX_HOME:-$HOME/.codex}"
Rules
- Every write lands under
scripts/ralph/in the current repo. A file written anywhere else has broken this. - If
scripts/ralph/already exists, offer to update (preserves config.env). - Copy templates from
templates/intoscripts/ralph/(includesralphctl.pyfor pause/resume/stop/status). - Copy
flowctl,flowctl.cmd,flowctl.py,flowctl_bootstrap.py,flowctl-help.txt, and theflowctl_tracker/package (from$PLUGIN_ROOT/scripts/) andpick-python.sh(from$PLUGIN_ROOT/scripts/lib/) intoscripts/ralph/— flat, so the resolver lands atscripts/ralph/pick-python.shwhereralph.shand the hook wrapper source it. Apick-python.shthat landed underscripts/ralph/lib/has broken this. - Set executable bit on
scripts/ralph/ralph.sh,scripts/ralph/ralph_once.sh,scripts/ralph/flowctl, andscripts/ralph/ralphctl.py. - Hook registration is agent-driven skill prose only. The plugin ships no hooks by default; you (the host agent) merge the guard entries into the project's host settings via Read+Edit, idempotently, without clobbering unrelated hooks. The boundary is hard: there is no flowctl subcommand for hook install/remove/status and no hook machinery in Python. A settings file whose hooks object now holds only flow-next entries, or a hook-install subcommand added to the CLI, has broken this.
Workflow
-
Resolve repo root:
git rev-parse --show-toplevel -
Check if
scripts/ralph/exists:- If exists: ask "Update existing Ralph setup? (preserves config.env and runs/) [y/n]"
- If no: stop
- If yes: set UPDATE_MODE=1
- If not exists: set UPDATE_MODE=0
- If exists: ask "Update existing Ralph setup? (preserves config.env and runs/) [y/n]"
What ships with it
10 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 184 B
- templates/.gitignore 25 B
- templates/config.env 4.7 KB
- templates/prompt_completion.md 4.8 KB
- templates/prompt_plan.md 4.8 KB
- templates/prompt_work.md 3.4 KB
- templates/ralph_once.sh 256 B runs code
- templates/ralph.sh 55 KB runs code
- templates/ralphctl.py 8.4 KB runs code
- templates/watch-filter.py 6.7 KB runs code
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.
- yesterday Changed · +3 lines 5c1b76be1ce3
- 7d ago First seen · 222 lines · 27 tokens per session scan C 79fe67753bbe
flow-next-ralph-init is a skill published in the GitHub repository gmickel/flow-next (691 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 3,737 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
project-execution
Executes implementation plans with progress tracking, checkpoint validation, and quality gates. Use after planning is complete and tasks are ready to implement.
pr
Comprehensive PR/issue review - analyzes architecture, tests, identifies unrelated changes mixed in, drafts review comment or issue comment. Use when user asks to review a PR, check a PR, look at PR changes, or comment on an issue.
backlog
Read, work, and maintain a Git repo's deferred-work items in docs/backlog/, one file per item. Use when the user says "backlog", "check backlog", "what's on my backlog", "work the backlog", "address the backlog", "add to backlog", "clean up backlog", or when a review or task produced items that are real but not being…
ask-codex
Consult OpenAI Codex for investigation, debugging, or code review. Use when user explicitly asks to "ask codex", "check with codex", "codex review", or as a last resort when stuck after 4+ failed attempts at debugging, investigation, or bug fix and completely out of ideas. Codex is slow (2-5 min), so only escalate…
clarify
This skill should be used when user appears confused, frustrated, or shows misalignment between expectations and reality. Triggers on phrases like "I don't understand", "this doesn't make sense", "confused", "wait, shouldn't it...", "why is this happening", "I thought X did Y", contradictory statements, or frustration…
writing-style
Use for technical communication - GitHub/GitLab tickets, PR/MR descriptions, issue comments, code review comments, commit messages. Direct, brief style with no AI-speak. NOT for README.md, public docs, or blog posts.