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-diagramgit 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-diagram)<a href="https://agentmods.dev/skills/davidomil/cloudx/cooperation-diagram"><img src="https://agentmods.dev/badge/skills/davidomil/cloudx/cooperation-diagram/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-diagram"><img src="https://agentmods.dev/badge/skills/davidomil/cloudx/cooperation-diagram.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.00031 | $0.00390 |
| Opus 5.5 | $0.00012 | $0.00156 |
| Sonnet 5.5 | $0.00006 | $0.00078 |
| Haiku 4.5 | $0.00003 | $0.00039 |
Grade A, and why
cooperation-diagram 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.
What it actually says
Draw an editable design with the user
Draft skill for the proposed helper in protocol.md. Use cooperation-board first.
Read the relevant board area, current object IDs, relation descriptions, WIP regions, and original reference images. Preserve the user’s sketch. If it is unfinished, comment briefly and wait for Ready. Do not replace a protected sketch with a cleaned-up diagram.
Use a few named shapes for responsibilities or steps, notes for decisions and evidence, code items for inert examples, and universal connections for relationships. Give every connection a useful custom description and an explicit direction. For example, connect Checkout API to Event queue with “publishes accepted payment.” Do not infer a formal depends-on or approval relation from a label.
Keep diagrams editable and text-addressable. Store IDs, labels, geometry, ports, and route points. Use brief labels for shapes and connections. Put decisions and evidence in nearby notes as short bullet points. Follow the ASD-STE100 principles in cooperation-board. Link each opened source beside its claim. Label proposed behavior as a proposal. Preserve exact code and source quotations.
Place new content in a clear unprotected area without covering the user’s work or moving their camera. Use small, bounded transactions against current revisions. Check new nodes, old/new geometry, connections and route crossings against WIP. If the service refuses a protected change, wait or ask at the target instead of routing around the guard.
Read back the touched nodes and relations after commit. Verify endpoint IDs and descriptions through text as well as the visual layout when available. Report the new object IDs in a short board pointer. Do not publish an uninspected diagram as proof of system behavior.
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 · 19 lines · 31 tokens per session scan A 7bf1849f238c
cooperation-diagram is a skill published in the GitHub repository davidomil/cloudx (1 stars, last pushed 2d ago), licensed MIT. It adds 31 tokens to every session and 390 once invoked, about $0.0001 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-diagram compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| cooperation-diagramdavidomil/cloudx | Skill | 1 | 2d ago | MIT | A | 31 | 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 |