Borrowing it
Nothing to install: this file belongs to yusifeng/formax. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/yusifeng/formax/main/.codex/skills/formax-rework-convergence-workflow/SKILL.mdgit clone --depth 1 https://github.com/yusifeng/formaxWrote 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/yusifeng/formax/formax-rework-convergence-workflow)<a href="https://agentmods.dev/skills/yusifeng/formax/formax-rework-convergence-workflow"><img src="https://agentmods.dev/badge/skills/yusifeng/formax/formax-rework-convergence-workflow/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/yusifeng/formax/formax-rework-convergence-workflow"><img src="https://agentmods.dev/badge/skills/yusifeng/formax/formax-rework-convergence-workflow.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.00574 |
| Opus 5 | $0.00030 | $0.00287 |
| Sonnet 5 | $0.00012 | $0.00115 |
| Haiku 4.5 | $0.00006 | $0.00057 |
Grade A, and why
formax-rework-convergence-workflow 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 11d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Formax Rework Convergence Workflow
Purpose
Use this workflow to clean up code after multiple back-and-forth edits.
Primary goal:
- Reduce redundancy
- Restore structure clarity
- Keep behavior unchanged unless user explicitly asks for behavior changes
Trigger Phrases
Run this skill when the user says:
返工收敛(recommended keyword)cleanup-pass- "帮我收敛一下这波改动"
- "把返工后冗余代码清掉"
Scope Rules
- No feature expansion during convergence.
- No broad redesign unless user explicitly asks.
- Prefer local cleanup in touched files first.
- Preserve existing runtime behavior and UI semantics.
Workflow
- Freeze Intent
- Restate the target in one sentence.
- Identify "must keep" behavior before editing.
- Build Cleanup Map
- Inspect current diff and touched files.
- Group issues into:
- duplicate logic
- dead code / unreachable branches
- conflicting style patterns
- state ownership confusion
- temporary patches that became permanent
- Rank by Risk and Value
- High priority:
- behavior-risky duplication
- conflicting state sources
- repeated conditional branches causing drift
- Medium priority:
- naming inconsistencies
- repeated style tokens/classes
- Low priority:
- cosmetic micro-cleanups
- Apply Minimal Convergence Edits
- Collapse duplicated branches into one shared path.
- Remove dead paths only when replacement path is verified.
- Keep interfaces stable.
- Keep patch size small and reviewable.
- Validate
- Run targeted type-check/tests for changed scope.
- If UI is touched, do a quick manual visual sanity check path.
- If validation is blocked, report the exact blocker and impact.
- Report Back in Convergence Format
what was removedwhat was unifiedwhat behavior stayed the sameresidual risks
Guardrails
- Do not hide uncertainty: explicitly call out assumptions.
- Do not ship "temporary fixes" silently.
- If a temporary mitigation is unavoidable, mark it and define removal conditions.
- Never mix unrelated cleanup in the same pass.
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.
- 11d ago First seen · 92 lines · 60 tokens per session scan A 4a1e0ef95160
formax-rework-convergence-workflow is a skill published in the GitHub repository yusifeng/formax (194 stars, last pushed 1mo ago), licensed MIT. It adds 60 tokens to every session and 574 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
printing-press-import
Bring a published CLI from the public library into the internal library so it's identical to a freshly-generated copy — module path reverted, manuscripts placed alongside, ready for /printing-press-polish or /printing-press-emboss. Use when the public library has a CLI you don't have locally, or to recover from a…
work
Execute an approved wish plan — orchestrate subagents per task group with fix loops, validation, and review handoff.
trace
Dispatch trace subagent to investigate unknown issues — reproduces, traces, and reports root cause for fix handoff.
preview-design
Render a real artifact through this branch's local MERIDIAN design code (not the published npm package) so the team can test the new Design Convention on the document / handoff / platform surfaces before it ships. Use for /preview-design, "preview the design convention", "render this with the new design", or Design…
sw-do
Implement a SpecWeave increment task by task through the ledger, with evidence per task and a verified close. Use for "implement this", "start working", "continue the increment", "keep going".
done
Close an increment: ledger check, specweave verify, optional review, then specweave complete. Use when all tasks are done and saying "close increment", "we are done", or "finish up".