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 human-explain-openaccpgit 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/human-explain-openaccp)<a href="https://agentmods.dev/skills/0fuk/openaccp/human-explain-openaccp"><img src="https://agentmods.dev/badge/skills/0fuk/openaccp/human-explain-openaccp/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/human-explain-openaccp"><img src="https://agentmods.dev/badge/skills/0fuk/openaccp/human-explain-openaccp.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.00051 | $0.01155 |
| Opus 5.5 | $0.00020 | $0.00462 |
| Sonnet 5.5 | $0.00010 | $0.00231 |
| Haiku 4.5 | $0.00005 | $0.00115 |
Grade A, and why
human-explain-openaccp 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 1mo 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Human Explain OpenACCP
Use the user's preferred language when it is known. If the preferred language is Chinese, use Chinese as the main language and keep English only for stable technical terms and exact names such as Primary, Frontier, worker, reviewer, handoff, validator, source pack, Prompt ID, Response ID, CARD, task-card, B0/B1/B2/B3, CI, CLI, JSON, schema, exact file names, or project-specific product terms. Do not write long English sentences or paragraphs in a Chinese explanation.
Explain:
- plain conclusion,
- what is happening,
- what is proven,
- what is provisional,
- what is missing,
- next meaningful decision.
Do not invent progress or hide authority limits.
Required Response Ending
Every OpenACCP role response should end with a short human-readable next-step paragraph. This applies to Primary, Frontier, worker, reviewer, discovery, validator, and bootstrap replies.
The ending should say:
- what the situation means right now,
- whether the human needs to act,
- the exact next action.
If no human action is needed, say that plainly and name the next agent-owned action, for example: No human action is needed right now; Frontier will continue B0/B1/B2 lane-local closure and consume the next child handoff.
If human input is needed, name the exact missing path, fact, decision, approval, repo boundary, branch, source root, test entrypoint, or authority boundary. Do not end with a file list, validator result, command output, or vague "wait for Primary" statement.
Explain Orchestration Meaning
Translate coordination terms into delivery meaning:
- Primary: what final decision, dispatch, or consume action it owns.
- Frontier: what lane it is closing and which B0/B1/B2 work remains.
- worker: what bounded task it executed and what evidence it returned.
- reviewer: what it checked and whether the recommendation is final or provisional.
- handoff: what it proves, what it does not prove, and who still needs to consume it.
- subagent: what bounded question it answered and how the parent orchestrator used the result.
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.
- 1mo ago First seen · 73 lines · 51 tokens per session scan A 188e6062e3b8
human-explain-openaccp is a skill published in the GitHub repository 0fuk/OpenACCP (2 stars, last pushed 15d ago), licensed MIT. It adds 51 tokens to every session and 1,155 once invoked, about $0.0002 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-08-31.
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.