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-script-output-placement-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-script-output-placement-workflow)<a href="https://agentmods.dev/skills/yusifeng/formax/formax-script-output-placement-workflow"><img src="https://agentmods.dev/badge/skills/yusifeng/formax/formax-script-output-placement-workflow.svg" alt="Measured on agentmods" 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.00038 | $0.00282 |
| Opus 5 | $0.00019 | $0.00141 |
| Sonnet 5 | $0.00008 | $0.00056 |
| Haiku 4.5 | $0.00004 | $0.00028 |
Grade A, and why
formax-script-output-placement-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 8d 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.
What it actually says
Formax Script Output Placement
Goal
新增或修改“会写文件”的脚本时，避免把机器产物放到 docs/。
Placement Rules
docs/只放文档与静态说明素材，不放机器生成基线/报告。- 产物就近放到 owner 目录：
- app 产物 ->
apps/<name>/perf/ - repo 级脚本产物 ->
scripts/baselines/ - 临时产物 ->
.tmp/（gitignored）
- app 产物 ->
- 生成脚本默认输出路径应指向 owner 目录，不指向
docs/**。 - 建议提供
--output或--baseline覆盖参数（便于 CI 与本地临时切换路径）。
Minimal Workflow
- 先定产物 owner 与默认输出目录。
- 再写脚本和默认路径（owner-local）。
- 同步更新 README/learning 里的路径引用。
Checks
node ./scripts/check-docs-artifact-placement.mjs
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.
- 8d ago First seen · 31 lines · 38 tokens per session scan A 941b19d06bcf
formax-script-output-placement-workflow is a skill published in the GitHub repository yusifeng/formax (193 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 282 once invoked, about $0.0002 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
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
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".