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 Obed0101/mflow --skill mflowgit clone --depth 1 https://github.com/Obed0101/mflowWrote 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/obed0101/mflow/mflow)<a href="https://agentmods.dev/skills/obed0101/mflow/mflow"><img src="https://agentmods.dev/badge/skills/obed0101/mflow/mflow/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/obed0101/mflow/mflow"><img src="https://agentmods.dev/badge/skills/obed0101/mflow/mflow.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.00077 | $0.01306 |
| Opus 5.5 | $0.00031 | $0.00522 |
| Sonnet 5.5 | $0.00015 | $0.00261 |
| Haiku 4.5 | $0.00008 | $0.00131 |
Grade A, and why
mflow 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 1mo 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mflow Skill
mflow keeps local worktrees synchronized while humans or AI agents edit. Treat it as a live sync layer, not as git, not as a secret manager, and not as a substitute for review.
Non-negotiables
- Never print, commit, log, or paste room secrets/API keys.
- Do not install, start, or configure mflow/MCP in a user's environment unless the human/project owner explicitly approves it.
- Before creating or changing harness hook files, call
mflow hook-statusand ask for human approval if the active harness is still manual. - Before commit/rebase/reset/branch surgery: pause mflow, inspect status and git diff, do the git operation, then resume.
- Use queued locks for hot files before parallel edits: shared config, migrations, schemas, auth, package manifests, generated public docs.
- If mflow is absent or stopped, do not assume peers are synced. Say so and continue with normal git safety.
- Hosted accounts are optional. The core OSS workflow is room + strong shared secret.
Before installing
If mflow is not already installed or configured, explain this to the human first:
- The CLI starts a local daemon that watches project files.
- The MCP server gives the agent status, peers, pause/resume, and lock controls.
- Room secrets must be generated by the human and never printed.
- This skill can be copied into agent runtimes that support skills.
Ask whether they want CLI only, CLI + MCP, or CLI + MCP + skill installation.
Quick start
npm i -g mflow-cli
export MFLOW_SECRET="$(openssl rand -hex 32)"
mflow start --room <repo>/<branch-or-task> --secret "$MFLOW_SECRET"
mflow status --watch
Join another worktree with the same room and secret:
mflow start --room <repo>/<branch-or-task> --secret "$MFLOW_SECRET"
Safe agent workflow
- Check sync state:
mflow hook-status
mflow status
mflow locks
If the active harness reports a missing hook, say that optional coordinated edit hooks are available, ask whether the human wants that installed now, and only then run mflow install-hooks --harness <supported-harness>.
If the harness is Codex, explain that mflow install-hooks --harness codex creates an experimental scaffold that still needs local verification before relying on it.
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.
- 1mo ago First seen · 176 lines · 77 tokens per session scan A 036d16981683
mflow is a skill published in the GitHub repository Obed0101/mflow (2 stars, last pushed 4mo ago), licensed MIT. It adds 77 tokens to every session and 1,306 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-08-31.
Other skills, from other repositories
safe-extraction
Apply when extracting code from a large monolith file into submodules. Covers barrel re-exports, internals DI seam proxy patterns, CI invariant allowlist updates, and cross-file test verification. Prevents CI failures, broken imports, and test regressions from code extraction.
git-revert-safety
Apply when reverting commits, undoing merges, or recovering from branch contamination. Covers collateral damage verification (manifest, package.json, CHANGELOG, lockfiles), cherry-pick vs revert decision matrix, partial-revert detection, merge-parent handling, and post-revert CI verification. Prevents the most common…
commit-pr
Mandatory Codex/Copilot publication adapter for opencode-swarm. Use for every GitHub issue assignment that results in code changes, commits, pushes, draft PRs, PR body edits, PR readying, release notes, or CI closeout. Must be loaded before git push, gh pr create, gh pr edit, or gh pr ready. Routes to the single…
fork-pr-operations
Operational patterns for fork PRs (head repo differs from base repo). Covers GitHub workflow approval after push, force-push protocol, remote naming conventions, stale CI verification, and bot review multi-round awareness. Load when working with fork PRs, cross-repo contributions, or workflow approval issues.
parallel-work-check
Apply before starting work on an existing branch. Checks for parallel work by other agents or developers that may supersede or conflict with your planned changes. Prevents wasted effort on stale branches.
merge-queue-readiness
Pre-queue merge-group CI simulation. Triggered before adding a PR to a GitHub merge queue. Prevents merge-queue kick-outs from integration test failures.