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/yusifeng/formax/formax-dev-loop-workflownpx skills add yusifeng/formax --skill formax-dev-loop-workflowgit clone --depth 1 https://github.com/yusifeng/formaxWhat 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.00068 | $0.00628 |
| Opus 5 | $0.00034 | $0.00314 |
| Sonnet 5 | $0.00014 | $0.00126 |
| Haiku 4.5 | $0.00007 | $0.00063 |
Grade A, and why
formax-dev-loop-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 3d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Formax Dev Loop (Mainline Discipline)
Default loop (repeat per TODO item)
-
Pick one mainline item and finish it end-to-end before starting another.
- If a new idea appears mid-flight, write it down in a backlog note and continue the mainline.
-
Write/adjust tests first to lock behavior (when feasible).
-
Implement the smallest change that satisfies the item.
-
Incremental optimization check (required)
- After implementation, do a quick pass:
- Is there newly-dead/unused logic introduced by this increment?
- Is there a low-risk simplification that reduces branching/duplication?
- If yes, include a small optimization in the same item (no scope drift, no behavior change).
- If no, explicitly proceed without optimization.
- After implementation, do a quick pass:
-
Run only targeted tests (never
bun run test:coverageunless explicitly asked).- Preferred:
bun run test -- <changed-test-files...> - Helper (repo):
bun run test:changed- Use default (staged only) for the commit you are about to make.
- Use
bun run test:changed -- --allonly when you intentionally want staged + unstaged + untracked.
- Preferred:
-
Pre-commit hygiene
- Avoid partial staging (“MM” state). If needed, check with:
bun run check:partial-stage
- Run review before every commit using
AGENTS.md->Review Profile (Single Source of Truth). - If review returns findings: fix -> re-run targeted tests -> re-run review.
- Avoid partial staging (“MM” state). If needed, check with:
-
Commit
- Keep it small (2–4 files ideally, unless refactor forces more).
- Prefer one concern per commit (tests + implementation together for that concern).
Guardrails (Formax-specific)
- Do not fix unrelated failures mid-loop unless they block the mainline.
- If a command would usually be run with pipes/redirections for convenience, prefer running it plain and rely on Formax’s own output truncation/Expand UI.
- Don’t “clean up” formatting/copy/colors/spacing unless explicitly requested or required for parity.
Quick commands
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.
- 3d ago First seen · 62 lines · 68 tokens per session scan A 0b7f03f259df
formax-dev-loop-workflow is a skill published in the GitHub repository yusifeng/formax (192 stars, last pushed 1mo ago), licensed MIT. It adds 68 tokens to every session and 628 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
git-workflow
Guides you through Git workflows — branching strategies, commit conventions, merge conflict resolution, and release management. Use when working with Git repositories or when the user asks about version control best practices.
openakita/skills@changelog-generator
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Use this skill whenever the user mentions changelogs, release notes, version updates, "what changed", product updates, app…
clawbox-git-commit-push
Use when the user asks to stage ClawBox changes, write a git commit, create a non-interactive commit, or push the current branch safely without mixing unrelated worktree changes.
git-commit
Smart git commit with branch protection, session-aware staging, and conventional commits.
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
interactive-login
How to complete browser/interactive logins (aws / gh / glab / gcloud). The platform backgrounds the login poller so it survives the human's browser round-trip — and when that does NOT work.