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 davidomil/cloudx --skill cooperation-boardgit clone --depth 1 https://github.com/davidomil/cloudxWrote 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/davidomil/cloudx/cooperation-board)<a href="https://agentmods.dev/skills/davidomil/cloudx/cooperation-board"><img src="https://agentmods.dev/badge/skills/davidomil/cloudx/cooperation-board/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/davidomil/cloudx/cooperation-board"><img src="https://agentmods.dev/badge/skills/davidomil/cloudx/cooperation-board.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.00039 | $0.00719 |
| Opus 5.5 | $0.00016 | $0.00288 |
| Sonnet 5.5 | $0.00008 | $0.00144 |
| Haiku 4.5 | $0.00004 | $0.00072 |
Grade A, and why
cooperation-board 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 4d 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 — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Work with the user on the blackboard
Draft for the proposed Cooperation plugin. The helper and environment contract are specified in protocol.md; they are not installed by this design package.
When this tab has a board, communicate substantive design work through it. Put graphs, decisions, evidence, questions, and explanations on the board. Keep terminal replies to brief progress, an honest tool problem, or a pointer to changed objects. Do not leave the board stale while writing the real discussion in chat.
- Run
contextandread --format markdownthrough the trusted helper. Read the board revision, assignment generation, WIP regions, addressed inbox, and relevant object IDs. If unassigned or closed, report that state. Do not choose another board or use a remembered path. - Read the relevant objects and sources. Resolve each relevant image with
asset --id ID, then open its returnedlocalPathwith your image-viewing tool. Alt text is not evidence that you saw the image. If viewing is unavailable, state what you could not inspect. - Work beside the user. Preserve their wording and layout unless the task calls for a change. Put a useful plan, proposal, or explanation near its subject. Use
cooperation-diagramfor editable graphs andcooperation-feedbackfor addressed questions. - Submit bounded operations with the observed revisions through
apply. The service derives your actor identity. Never replace a projection file, impersonate the user, release WIP, change assignments, or bypass a conflict. - Inspect the receipt and changed objects. For a question, commit its answer and
respondsToEventIdstogether. End with a short board pointer, such as “I added the replay boundary to System design, note-decision.”
Write short board items
- Use a short title and a few bullet points for each note or thread answer.
- Put the answer or decision first. Give one fact, action, or question per bullet.
- Follow ASD-STE100 principles: short complete sentences, active voice, and consistent technical terms.
- Split separate topics into separate items. Link detailed material instead of adding long paragraphs.
- Keep conditions and uncertainty. Label proposals and inferences. State missing evidence as a precise question.
- Cite an opened source beside its claim. Report only tests and measurements actually observed.
- Preserve exact code, quotations, IDs, and source links when shortening text.
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.
- 4d ago First seen · 37 lines · 39 tokens per session scan A bd0c1b5d2922
cooperation-board is a skill published in the GitHub repository davidomil/cloudx (1 stars, last pushed 2d ago), licensed MIT. It adds 39 tokens to every session and 719 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-11-03.
cooperation-board compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| cooperation-boarddavidomil/cloudx | Skill | 1 | 2d ago | MIT | A | 39 | Claude Code, Codex |
| desktop-brand-builderQwenLM/qwen-code | Skill | 29k | yesterday | Apache-2.0 | A | 68 | Claude Code, Codex |
| datavizQwenLM/qwen-code | Skill | 29k | yesterday | Apache-2.0 | A | 26 | Claude Code |
| brand-visual-qualitydevcodex-labs/devcodex | Skill | 432 | 10d ago | AGPL-3.0 | A | 86 | Codex |
| ux-interaction-architecturedevcodex-labs/devcodex | Skill | 432 | 10d ago | AGPL-3.0 | A | 80 | Claude Code, Codex |
| design-system-architecturedevcodex-labs/devcodex | Skill | 432 | 10d ago | AGPL-3.0 | A | 72 | Claude Code, Codex |
| frontend-ux-engineerDominikTobureto/awesome-grok-build | Skill | 69 | 2mo ago | MIT | A | 42 | Claude Code, Codex |