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 hoangsonww/AI-Agents-Orchestrator --skill collaboration-statusgit clone --depth 1 https://github.com/hoangsonww/AI-Agents-OrchestratorWrote 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/hoangsonww/ai-agents-orchestrator/collaboration-status)<a href="https://agentmods.dev/skills/hoangsonww/ai-agents-orchestrator/collaboration-status"><img src="https://agentmods.dev/badge/skills/hoangsonww/ai-agents-orchestrator/collaboration-status/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/hoangsonww/ai-agents-orchestrator/collaboration-status"><img src="https://agentmods.dev/badge/skills/hoangsonww/ai-agents-orchestrator/collaboration-status.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.00026 | $0.00126 |
| Opus 5.5 | $0.00010 | $0.00050 |
| Sonnet 5 | $0.00005 | $0.00025 |
| Haiku 4.5 | $0.00003 | $0.00013 |
Grade A, and why
collaboration-status 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 2d 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
Collaboration Status
Call ai_collaboration.status for the current repository and report:
- active task ID, title, and status;
- current branch, head, and changed-file count;
- providers and session event counts;
- latest checkpoint and recent failures;
- the most useful next action supported by the data.
Keep this operation read-only. If there is no active task, say so and offer to call ai_collaboration.start_task with the user's title.
What ships with it
1 file 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.
- 2d ago First seen · 17 lines · 26 tokens per session scan A 468e9824f219
collaboration-status is a skill published in the GitHub repository hoangsonww/AI-Agents-Orchestrator (84 stars, last pushed 2d ago), licensed MIT. It adds 26 tokens to every session and 126 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-09-21.
Other skills, from other repositories
github-review-pr
Review GitHub pull requests with detailed, multi-perspective code analysis using parallel subagents. Use this skill whenever the user wants to review a PR, asks for code review on a pull request, mentions "review PR", "check this PR", "look at pull request", or references a PR number or GitHub PR URL. Do NOT use for…
github-fix-issue
Fix GitHub issues end-to-end — analysis, branch creation, implementation, testing, and PR submission. Use whenever the user mentions fixing a GitHub issue, says "fix issue.
github-review-pr
Review a GitHub pull request with evidence-backed, multi-angle analysis and false-positive filtering. Use when the user asks to review, inspect, or check a pull request by number or URL. Not for local uncommitted changes.
respond-to-pr-comments
Respond to pull request review comments on GitHub or Azure DevOps Services. Reads review threads, validates each, proposes fixes or explanations, applies changes with user confirmation, and updates thread status via the platform's API. Use when the user wants to address PR feedback or resolve review threads.
apex-github-operations
WORKFLOW SKILL — Full GitHub contribution lifecycle: branches, conventional commits, issues, PRs, Actions, releases. gh CLI-first with MCP fallback. WHEN: "commit", "push", "open PR", "create branch", "create issue", "cut release", "GitHub operation". DO NOT USE FOR: Azure infrastructure, Bicep/Terraform code…
apex-host-git-commit
Stage scoped changes, commit, push, and offer a PR in Agent Host. Use /apex-host-git-commit only after selecting the built-in agent owner and MAI-Code-1.1-Flash.