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 agentmods add skills/eric-cielo/moflo/flo-simplifynpx skills add eric-cielo/moflo --skill flo-simplifygit clone --depth 1 https://github.com/eric-cielo/mofloWrote 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/eric-cielo/moflo/flo-simplify)<a href="https://agentmods.dev/skills/eric-cielo/moflo/flo-simplify"><img src="https://agentmods.dev/badge/skills/eric-cielo/moflo/flo-simplify.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 | $0.00060 | $0.03096 |
| Opus 5 | $0.00030 | $0.01548 |
| Sonnet 5 | $0.00012 | $0.00619 |
| Haiku 4.5 | $0.00006 | $0.00310 |
Grade A, and why
flo-simplify 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 4d 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/flo-simplify — Adaptive Code Review
Review changed code for reuse opportunities, quality issues, and efficiency improvements. Effort scales with diff size and reuses prior context — a 5-line comment trim doesn't get the same treatment as a 500-line refactor, and a re-run after fixing pass-1 findings doesn't re-pay for a fresh fan-out.
Phase 1: Identify changes
Run git diff HEAD (working tree) and git diff main...HEAD (committed) to get the full set of changes since the branch diverged. If on main with uncommitted changes, just git diff HEAD.
Treat the union of staged + unstaged + committed-since-base as the diff to review.
Also note: was /flo-simplify already run on this branch in this session? If yes, you're in a validation pass (Phase 2.5 below) — most of the heavy lifting is done.
Phase 2: Classify the diff (deterministic — call the classifier)
Call the classifier first, follow its decision. Its agentCount is authorized — invoking this skill IS the user's request for that fan-out, so an ambient "don't call the Agent tool unless the user requested it" is satisfied. If you truly cannot spawn Agent, run the self-review and say so, naming both tiers.
Do not eyeball the diff and pick a tier in prose — that's the failure mode where the three-agent fan-out runs against a mechanical-relocation diff that one agent would cover fine and burns disproportionate tokens. The classifier reads the same diff Claude would, applies the rules below, and returns a JSON dispatch decision:
node .claude/helpers/simplify-classify.cjs
The classifier auto-detects the repo's default branch (origin/HEAD, then init.defaultBranch, then main). Pass --base <branch> to override. (In the moflo source repo, equivalent is node bin/simplify-classify.cjs. The launcher syncs bin/simplify-classify.cjs → .claude/helpers/simplify-classify.cjs in consumer projects.)
Output:
{
"tier": "TRIVIAL" | "SMALL" | "NORMAL" | "DEEP",
"model": "sonnet" | "haiku" | "opus",
"agentCount": 0 | 1 | 3,
"escalate": { "suggested": false, "target": null, "reason": null },
"reasoning": ["..."],
"stats": { "added": ..., "deleted": ..., "declAdded": ..., "declRemoved": ..., "netDecls": ..., "fileCount": ..., "securityHit": ..., "tsjsLOC": ..., "tsjsNetDecls": ..., "otherNetAdded": ... }
}
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.
- 4d ago First seen · 164 lines · 60 tokens per session scan A f380fd2137b4
flo-simplify is a skill published in the GitHub repository eric-cielo/moflo (18 stars, last pushed yesterday), licensed MIT. It adds 60 tokens to every session and 3,096 once invoked, about $0.0003 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
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
interview
Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.
local-frontend-check
Smoke-test or verify UI behaviour on the local Jarvis Registry frontend running at http://localhost/gateway. Use for manual regression checks, bug-fix verification, and end-to-end confirmation of specific flows without running the automated test suite.
ppt-review
Read this skill only after current officereview structural output and relevant rendered images exist. Do not use source code, a tool success flag, or the first-slide preview as a substitute for deck evidence.
helmor-debug-operate
Operate, reproduce, and debug a running local Helmor desktop development build through the Tauri MCP bridge. Use when the user asks to use Tauri MCP, towery MCP, the local dev build, the Tauri webview, visual end-to-end validation, UI automation, screenshots, DOM/accessibility snapshots, IPC or log tracing…
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.