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 discovery-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/discovery-openaccp)<a href="https://agentmods.dev/skills/0fuk/openaccp/discovery-openaccp"><img src="https://agentmods.dev/badge/skills/0fuk/openaccp/discovery-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/discovery-openaccp"><img src="https://agentmods.dev/badge/skills/0fuk/openaccp/discovery-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.00043 | $0.00313 |
| Opus 5 | $0.00022 | $0.00156 |
| Sonnet 5 | $0.00009 | $0.00063 |
| Haiku 4.5 | $0.00004 | $0.00031 |
Grade A, and why
discovery-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 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
Discovery OpenACCP
Read facts, classify gaps, and prepare safe next steps without implementation.
Do not edit, commit, merge, or treat reference material as current fact.
Reply Contract
Every discovery reply must use human-explain-openaccp style in the preferred language. Explain what facts were found, what is still unproven, and which B0/B1/B2 action becomes possible next.
Every status-like discovery reply must use formal-report-openaccp structure or include a machine-summary artifact with Prompt ID, Response ID, source ids, authority, effects, basisRefs, locators, claims, and nextActions.
End every discovery reply with a short Recommended Next Step / 下一步建议 paragraph. If discovery unlocked a B0/B1/B2 action, name the agent-owned next action. If human input is needed, name the exact missing source, owner fact, repo boundary, path, approval, or decision.
Evidence And Locator Rules
Discovery output should name current, reference, deprecated, invalid, and unknown sources separately. Include locators for each material read, plus the exact next B0/B1/B2 action unlocked by those facts. Discovery does not claim implementation readiness unless a task card, authority charter, and verification plan already exist.
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 · 23 lines · 43 tokens per session scan A 989d28d807d8
discovery-openaccp is a skill published in the GitHub repository 0fuk/OpenACCP (2 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 313 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
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
A planning guide for coordinating work between a person and a coding agent. It turns required information, resources, feedback, actions, and handoffs into explicit checklists and protocols.
coordinate-agents
Route Codex-native multi-agent orchestration in a Git repository through a local-first, recoverable Agent Bus. Use for role-based planning, task execution, review, recovery, adapters, and human-gated release workflows. The plugin supports Codex CLI, Google Antigravity CLI, Claude, and other configured coding agents.…