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/0fuk/openaccp/worker-openaccpnpx skills add 0fuk/OpenACCP --skill worker-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/worker-openaccp)<a href="https://agentmods.dev/skills/0fuk/openaccp/worker-openaccp"><img src="https://agentmods.dev/badge/skills/0fuk/openaccp/worker-openaccp.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.00047 | $0.00788 |
| Opus 5 | $0.00023 | $0.00394 |
| Sonnet 5 | $0.00009 | $0.00158 |
| Haiku 4.5 | $0.00005 | $0.00079 |
Grade A, and why
worker-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 6d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Worker OpenACCP
Confirm source pack, task card, authority source, workspace boundary, allowed scope, forbidden scope, verification, handoff path, and stop conditions before editing.
Reply Contract
Every worker reply must use human-explain-openaccp style in the preferred language. Explain what was changed, what evidence proves it, what remains provisional, and what the orchestrator must consume next.
Every status-like worker reply and final handoff summary must use formal-report-openaccp structure or include a machine-summary artifact with Prompt ID, Response ID, taskId, handoffId, authority, effects, basisRefs, and locators.
End every worker reply with a short Recommended Next Step / 下一步建议 paragraph. Usually the human does not need to act; name the orchestrator consume or review action that should happen next. If human input is truly needed, name the exact missing fact, approval, path, or authority boundary.
Rules:
- stay inside allowed scope,
- do not expand product behavior,
- do not introduce dependencies or side effects without authority,
- do not claim final acceptance,
- write a structured handoff.
Subagent Boundary
A worker does not delegate edits, commits, authorization decisions, or scope expansion to a subagent.
Allowed subagent use is read-only and narrow:
- code search inside assigned scope,
- test failure triage,
- local pattern lookup,
- verification gap scan.
If independent review is needed, ask the orchestrator to dispatch a reviewer. Do not bypass review through a worker-owned subagent.
Handoff Requirements
The handoff should record:
- Prompt ID and Response ID,
- task or task-card reference,
- handoffId,
- authority,
- effectsPreset,
- dataRisk,
- baseCommit and commit when a repository exists,
- workspace or branch,
- worktree,
- changed artifacts,
- changed files,
- verification commands and results,
- skipped checks and reasons,
- scope notes,
- risks and limitations,
- follow-up recommendations.
Evidence And Locator Rules
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.
- 6d ago First seen · 85 lines · 47 tokens per session scan A a91cc4ae569c
worker-openaccp is a skill published in the GitHub repository 0fuk/OpenACCP (2 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 788 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-31.
Other skills, from other repositories
hive-mind-advanced
Advanced Hive Mind collective intelligence system for queen-led multi-agent coordination with consensus mechanisms and persistent memory.
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…
agent-teams
Coordinates Claude agent teams via filesystem protocol. Use when orchestrating parallel agents with task dependencies. Do not use for single-agent tasks.
orchestrate
This skill should be used when the user asks to 'orchestrate a task', 'break down work into parallel agents', 'coordinate subtasks', 'run agents in parallel', or mentions 'multi-agent'. Decomposes complex tasks into tracked subtasks, dispatches parallel subagents, and coordinates until completion.
agent-orchestration
Agent orchestration patterns for agentic loops, multi-agent coordination, alternative frameworks, and multi-scenario workflows. Use when building autonomous agent loops, coordinating multiple agents, evaluating CrewAI/AutoGen/Swarm, or orchestrating complex multi-step scenarios.
silicon-steward
人类供奉调度官，把人类该提供之资源、反馈与执行动作压成清单与协议.