Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/eric-cielo/moflonpx agentmods add skills/eric-cielo/moflo/flo-simplifyWrote 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/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/eric-cielo/moflo/flo-simplify"><img src="https://agentmods.dev/badge/skills/eric-cielo/moflo/flo-simplify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00060 | $0.03096 |
| Opus 5.5 | $0.00024 | $0.01238 |
| Sonnet 5.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 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 — 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.
- 1mo 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 (19 stars, last pushed yesterday), licensed MIT. It adds 60 tokens to every session and 3,096 once invoked, about $0.0002 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-30.
Other skills, from other repositories
suede-code-review
Suede AI findings-only code review with full context: changed files, callers, contracts, and deploy surface. Covers TypeScript, React, Next.js, database, Swift/iOS, OWASP, accessibility, SEO, observability, commit hygiene, and deploy risk, ranked P0-P3 with file:line evidence and a fix path. Use when asked to review a…
suede-code
Suede AI combined code review and ship grade in one pass: findings with file:line evidence plus an A-F lane grade, Instant-F security triggers, OWASP checks, a deploy-safety gate, and fix briefs. Use when asked to review this, grade this, security-check this, is this safe to ship, or check this PR before merge…
suede-code-grader
Suede AI blunt A-F ship grade for a code change across correctness, security and permissions, data and state, domain truth, UX and release behavior, tests and verification, and deploy readiness, with Instant-F triggers and evidence-based grade caps on auth, payment, migration, and public-API surfaces. Use when asked…
init
Opt-in onboarding for the mARC agent team. Scaffolds a per-repo team binding so the team graduates from ephemeral session-memory to persistent, versioned config — without ever writing a file silently. Discovers the repo's org/repo/ project at runtime via gh, prefills {{ agentsdir }}/team.toml, and (optionally) a lean…
tech-lead
Channel operator (IRC handle @techlead) for the mARC agent team. Compiles chat demands into ready-to-execute work, records them on the GitHub Project board/Issues, and dispatches to specialists (@dev, @sre, @design, @sec, @rev, @research). Invoke with /tech-lead to turn discussion into tracked, delegated tasks.
upstream
Opt-in upstream contribution workflow for process improvements and field lessons. Scans the consuming repo's local AGENTS.md, {{ agentsdir }}/team.toml, and commit history for emergent rules, sanitizes sensitive client context, formats governed rule origins, and drafts an upstream Pull Request or Issue to the upstream…