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/vcs_collaborationnpx skills add opensquad-ai/opensquad --skill vcs_collaborationgit 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/vcs_collaboration)<a href="https://agentmods.dev/skills/opensquad-ai/opensquad/vcs_collaboration"><img src="https://agentmods.dev/badge/skills/opensquad-ai/opensquad/vcs_collaboration.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.00016 | $0.00794 |
| Opus 5 | $0.00008 | $0.00397 |
| Sonnet 5 | $0.00003 | $0.00159 |
| Haiku 4.5 | $0.00002 | $0.00079 |
Grade A, and why
vcs_collaboration 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VCS Collaboration Skill (OpenSquad Edition)
This skill enables agents to participate in complex, multi-agent software development using Git and GitHub within the OpenSquad local-first architecture. It emphasizes Local Branching Isolation and VCS Audit Transparency.
1. Local Shared Workspace Etiquette
In OpenSquad, agents share the same physical directory. To avoid collision:
- ALWAYS check out a new branch for your task:
git.checkout(target="agent_id/feat-name", create=True). - NEVER modify files directly on
mainordevunless you are the PM or Reviewer during a merge. - NEVER use
git commit --no-verifyor other commands that bypass hooks.
2. Implementation & Handoff Loop
- Assigned: When PM assigns a task via @mention, acknowledge receipt in group chat.
- Setup: Switch to a feature branch:
git.checkout(target="agent_id/feat-name", create=True). - Commit: Perform atomic commits. The
git_coreplugin will automatically inject your Agent ID as the author. - Handoff: Once complete, notify the Senior/Reviewer in group chat: "@Senior_Bot, feature logic finished on branch agent_id/feat-name. Please review and merge."
- Sync: If someone else merged to main, rebase your branch:
git.checkout(target="main")->git.pull()->git.checkout(target="your-branch")->git.rebase(upstream="main").
3. Remote Synchronization (VCS Coordinator Only)
Only agents designated as "VCS Coordinator" (holding the master GitHub token) should perform remote operations:
- Push:
git.push(remote="origin", branch="main"). - PR:
vcs.pr_create(repo="owner/repo", title="...", body="..."). - Audit: All remote actions are logged in the VCS Audit Timeline. Review this UI periodically to ensure transparency.
4. Communication Examples
For practical messaging patterns and handoff scenarios, refer to HANDOFF_EXAMPLES.md. Always follow the "@mention + [STATUS/BUG/PHASE]" message format to maintain team visibility.
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 · 66 lines · 16 tokens per session scan A 8bb7282cea3e
vcs_collaboration is a skill published in the GitHub repository opensquad-ai/opensquad (5 stars, last pushed 21d ago), licensed MIT. It adds 16 tokens to every session and 794 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.
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.
git-workflow
When the user asks you to perform git operations, create branches, open PRs, manage releases, or resolve conflicts, follow this guide. These are the procedural patterns you should apply consistently.
x-intelligence
When the user asks you to search, monitor, or analyze content on X (formerly Twitter), follow this guide. All operations use the official X API v2 and optionally the xAI Grok API for analysis. Never scrape. Never use unofficial endpoints.
life-automation-audit
Use this as an on-demand long prompt. Do not paste it into SOUL.md / PRINCIPLES.md / AGENTS.md. When the user asks to audit their life for automation opportunities, load and follow this prompt.