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 skills add Haaaiawd/ANWS --skill output-contractgit clone --depth 1 https://github.com/Haaaiawd/ANWSWrote 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/haaaiawd/anws/output-contract)<a href="https://agentmods.dev/skills/haaaiawd/anws/output-contract"><img src="https://agentmods.dev/badge/skills/haaaiawd/anws/output-contract.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.1 | $0.00063 | $0.00582 |
| Opus 5 | $0.00032 | $0.00291 |
| Sonnet 5 | $0.00013 | $0.00116 |
| Haiku 4.5 | $0.00006 | $0.00058 |
Grade A, and why
output-contract 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
输出契约与协作闭环
各 Skill、Workflow 若重复本节条文，应改为一句引用本 Skill，仅保留角色或步骤专属增量。
何时加载
- 撰写即将写入仓库的架构 / 审查 / 探索类 Markdown。
- 父会话拆分并行子任务，或按路径切片协作修改。
- 需要核对「是否可追溯、是否重复叙事、是否单写者」时。
Spec / 落盘契约
- Precise：可核对陈述须带来源或
path:line/ 章节锚点；禁止无源强结论。 - Evidence-backed：发现 / 证据 / 建议须能指回具体输入或检索结果。
- Non-repetitive：同一事实只写一次；禁止总述与正文两套复述。
- No filler：禁止无主语的「需优化 / 应关注」类空话。
规范块（CRITICAL、严重度表、门禁、上下游契约）不得删；收紧仅针对执行旁白与重复叙事。
委派闭环（父子会话）
- 父会话：
TARGET_DIR、轮次、最终路径、合并顺序、对规范化报告路径的唯一写盘。 - 子会话：有界切片；证据规则与父级相同。
- 交接：子代理返回可合并表结构 + 一行裁定；父代理去重、对照 spec、写
07_*/ explore 报告，再跑工作流文末 completion。
无委派时：单会话跑全文；父级仍负最终落盘与一致性。
并行与路径
- 每个被管理路径（或 glob）每批最多一个写者；禁止在授权外全仓格式化。
- 子任务目录或主题须 不相交；冲突由父代理裁决。
- 与
/genesis协同时的检查清单与交接句式见genesis.md「子代理编排与检查清单」（或 EN 树同名小节）。
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 · 38 lines · 63 tokens per session scan A e35b4de9988e
output-contract is a skill published in the GitHub repository Haaaiawd/ANWS (142 stars, last pushed 3mo ago), licensed MIT. It adds 63 tokens to every session and 582 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
ai-engineering-toolkit
6 production-ready AI engineering workflows: prompt evaluation (8-dimension scoring), context budget planning, RAG pipeline design, agent security audit (65-point checklist), eval harness building, and product sense coaching.
clonedeps
Clone important project dependency source code into an ignored local workspace so OpenCode can inspect library internals. Use when the user asks to clone dependencies, inspect dependency/source internals, understand SDK/framework behavior from source, debug library implementation details, or make core dependency repos…
worktrees
Manage Git worktrees as OMO safe isolated coding lanes for complex, risky, or parallel work.
simplify
Simplifies code for clarity without changing behavior. Use for readability, maintainability, and complexity reduction after behavior is understood.
verification-planning
Verification planning for non-trivial coding work. Use before implementing a feature, bug fix, refactor, cross-system change, or high-confidence behavior change that needs a credible project-specific evidence path.
loop-engineering
Loop engineering runtime Grill + Monitor.