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/opensquad-ai/opensquad/collaboration_managementnpx skills add opensquad-ai/opensquad --skill collaboration_managementgit clone --depth 1 https://github.com/opensquad-ai/opensquadWrote 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/opensquad-ai/opensquad/collaboration_management)<a href="https://agentmods.dev/skills/opensquad-ai/opensquad/collaboration_management"><img src="https://agentmods.dev/badge/skills/opensquad-ai/opensquad/collaboration_management.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 | $0.00025 | $0.04554 |
| Opus 5 | $0.00013 | $0.02277 |
| Sonnet 5 | $0.00005 | $0.00911 |
| Haiku 4.5 | $0.00003 | $0.00455 |
Grade A, and why
Collaboration Management 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 — 796 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Collaboration Management Skill
This Skill provides a complete management workflow and best practices for multi-agent collaboration cards (Collab Cards).
What is a Collaboration Card?
A collaboration card is a predefined multi-agent collaboration pattern that defines:
- Collaboration phases and workflow: Complete lifecycle from requirements to delivery
- Role responsibilities: Specific responsibilities for PM, Developer, QA, and other roles
- Message formats and conventions: Standardized formats for task assignment, status reporting, and bug reports
- Behavioral constraints: Avoiding overstepping, silence, and assumptions
Storage location: collab_cards/*.md
Core mechanism:
- Collaboration card content is injected into the Agent's system prompt during the session
- The PM loads the collaboration card when starting a collaboration; Workers load the same card when joining
- The collaboration card is automatically unloaded when leaving the collaboration
Collaboration Card Structure
Standard Format
---
name: card_name
description: Collaboration card description
tags: tag1, tag2
suggested_roles: pm, developer, qa
min_members: 2
---
## Project Lifecycle
| Phase | Lead | Output | Transition Condition |
|-------|------|--------|---------------------|
| P1 Requirements | PM | Requirements doc | User approval |
| P2 Implementation | Dev | Code | Development complete |
| P3 Testing | QA | Test report | Tests pass |
## Standard Message Formats
**Task Assignment**:
\```
@Agent [TASK] Task Name
Description: ...
Acceptance Criteria: ...
\```
**Status Report**:
\```
[STATUS] Completed: XXX Blocked: YYY
\```
## Behavioral Constraints
- No overstepping
- No silence
- No assumptions
Workflows
Workflow 1: View Available Collaboration Cards
Scenario: Learn which collaboration modes are available in the system
<tool name="collaboration">
<function>list_collab_cards</function>
<parameters></parameters>
</tool>
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 796 lines · 25 tokens per session scan A e7c3d89e8f3d
Collaboration Management is a skill published in the GitHub repository opensquad-ai/opensquad (5 stars, last pushed 21d ago), licensed MIT. It adds 25 tokens to every session and 4,554 once invoked, about $0.0001 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
typescript-expert
TypeScript and JavaScript expert with deep knowledge of type-level programming, performance optimization, monorepo management, migration strategies, and modern tooling.
trello
Manage Trello boards, lists, and cards via the Trello REST API.
apple-reminders
Manage Apple Reminders via the remindctl CLI on macOS (list, add, edit, complete, delete). Supports lists, date filters, and JSON/plain output.
things-mac
Manage Things 3 via the things CLI on macOS (add/update projects+todos via URL scheme; read/search/list from the local Things database). Use when a user asks Kabot to add a task to Things, list inbox/today/upcoming, search tasks, or inspect projects/areas/tags.
electron-pro
Expert in building cross-platform desktop applications using web technologies (HTML/CSS/JS) with the Electron framework.
lat-md
Writing and maintaining lat.md documentation files — structured markdown that describes a project's architecture, design decisions, and test specs. Use when creating, editing, or reviewing files in the lat.md/ directory.