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 0fuk/OpenACCP --skill formal-reportgit clone --depth 1 https://github.com/0fuk/OpenACCPWrote 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/0fuk/openaccp/formal-report)<a href="https://agentmods.dev/skills/0fuk/openaccp/formal-report"><img src="https://agentmods.dev/badge/skills/0fuk/openaccp/formal-report/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/0fuk/openaccp/formal-report"><img src="https://agentmods.dev/badge/skills/0fuk/openaccp/formal-report.svg" alt="Reviewed on agentmods" width="80" 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.00076 | $0.00704 |
| Opus 5.5 | $0.00030 | $0.00282 |
| Sonnet 5.5 | $0.00015 | $0.00141 |
| Haiku 4.5 | $0.00008 | $0.00070 |
Grade A, and why
formal-report 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 2d 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
/formal-report — 正式进度报告
读者是 owner,不是下游 agent。全文按 /human-explain 写(结论先行、业务语言、禁 AI 腔与黑话——禁词表以那边为准,这里不重抄)。
1 · 骨架:进度汇报固定四问(表格第一列固定用这四个标签)
| 类型和状态 | 内容 |
|---|---|
| 做了什么 | 每条挂证据(文件/commit/verdict/读数),没证据的不写「完成」 |
| 目标是什么 | 当前目标态一句话+离终门还差哪几站 |
| 在等什么 | 等谁的什么信号;信号到了触发什么。只写「等」不写信号=不合格 |
| 卡在哪 | 卡点/为什么没卡;有停摆先写停摆时长与根因 |
| 表格纪律:单元格短摘要;路径/命令/哈希/日志不进单元格;证据放表后「依据与验证」节;禁命令块;禁 HTML/隐字符排版技巧。 |
2 · 数字纪律
- 数字只许实测值,每个数字标来源(测试脚本原文/库读数/文件 mtime/接口响应);推算值必须标「推算」并写推算式。
- 凡出现「全绿/完成/达成/验收」字样,必须并排决策完成度四态:已合流可见 X / 在飞 Y / 已裁未派工 Z / 候 owner W。缺表禁用这些词(回归门≠完成门)。
- 「已排除/无残留/非缺陷」类全称否定:先列查过哪些面。
- 引用他人数字回原件逐字对;时刻 date 实取。
3 · 必备节
- 依据与验证(表后):证据指针一行一条。
- 未做与降级:诚实清单,空也写「无」。
- 下一步建议(结尾):当前处境一句话+下一动作;需要人做什么就点名具体路径/事实/批准;不需要人动就明说并点名下一个 agent 动作。「只说等」不合格——等待必须写明等的信号与信号到了做什么。
- 末尾两行:
Response ID、Response log path(无落盘文件写chat reply)。
4 · 语言
用用户偏好语言;中文报告标题/表格/证据/下一步全中文,英文只留稳定技术名与精确文件名,不写整段英文。
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.
- 2d ago First seen · 33 lines · 76 tokens per session scan A c0ce4f495d7f
formal-report is a skill published in the GitHub repository 0fuk/OpenACCP (2 stars, last pushed 2d ago), licensed MIT. It adds 76 tokens to every session and 704 once invoked, about $0.0003 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-10-14.
Other skills, from other repositories
coordinate-agents
Route requests that explicitly use Coordinate Agents or operate on its existing Tasks to setup, execution, review, or recovery skills.
company-handbook
The cross-director coordination protocol for the 1ai business kingdom. Defines how Content, Video, Image, Marketing, and Sales directors work together. Has memory via 1ai-hub brain, follows 1ai-rules, and coordinates with Vilona (GM). Use when coordinating multiple directors, resolving conflicts between teams, or when…
coordination-bus
Use when two or more agents share work, when a task spans sessions, or when claiming, heartbeating, completing, or blocking a coordination bus task. The bus is the single source of truth for who owns what — never coordinate through private agreement.
handoff-mesh
Built-in communication layer for multi-agent setups. Full-mesh handoff folders (any agent can hand off to any other), an hourly watcher that surfaces open handoffs, weekly archive cleanup, and a completion-reporting loop so every handoff is handled AND verified. The durable 'brain' counterpart to real-time channels…
clawmail
Canonical joelclaw mail coordination protocol for all agents. Use when announcing work, checking inboxes, reserving files, releasing locks, handling task handoffs, triaging stale reservations, or auditing coordination quality. Triggers on: 'clawmail', 'agent mail', 'joelclaw mail', 'reserve files', 'release locks'…
nexus
Use in repos coordinated by the Nexus CLI, especially when NEXUSCONSTITUTION.md, NEXUSQUEUE.md, NEXUSSTANDUP.md, or .nexus/ exists, or when the user asks about Nexus start/claim/release/doctor/status/next.