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 aAAaqwq/AGI-Super-Team --skill collaborationgit clone --depth 1 https://github.com/aAAaqwq/AGI-Super-TeamWrote 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/aaaaqwq/agi-super-team/collaboration)<a href="https://agentmods.dev/skills/aaaaqwq/agi-super-team/collaboration"><img src="https://agentmods.dev/badge/skills/aaaaqwq/agi-super-team/collaboration/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/aaaaqwq/agi-super-team/collaboration"><img src="https://agentmods.dev/badge/skills/aaaaqwq/agi-super-team/collaboration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00035 | $0.00370 |
| Opus 5.5 | $0.00014 | $0.00148 |
| Sonnet 5.5 | $0.00007 | $0.00074 |
| Haiku 4.5 | $0.00003 | $0.00037 |
Grade A, and why
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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- collaboration — 100% identical, 0 lines differ
What it actually says
Collaboration
This skill documents how to collaborate on projects on GitHub.
Working on Projects
With write access
If you have write access to the project, you may work directly in the project.
With read-only access
If you only have read-only access and cannot write directly to any branches:
- Create a fork under your own GitHub user account
- Work exclusively on the fork, not the original repository
- The fork is your workspace for all development
Making Changes
To submit changes to a project:
- Create a new branch (never commit directly to main)
- Make commits on this branch as work progresses
- When ready, create a PR from the working branch towards the main branch (from one repo to another if it's a fork)
Code Reviews
When asked to review code:
- Do the review directly on the GitHub PR
- Add comments inline in the code where they make sense
- Use general PR comments only for overarching feedback
Addressing Review Comments
When responding to review feedback:
- Address comments on GitHub, not just in code
- Reply to each comment explaining what was changed or why something was kept
- Mark conversations as resolved when the feedback has been addressed
After PR is Merged
Once a PR has been merged:
- Switch back to the main branch
- Pull from origin to sync with the merged changes
Issues
Always create GitHub issues on the original repository, never on the fork. The fork is only for development work, if needed.
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.
- 1mo ago First seen · 59 lines · 35 tokens per session scan A 503063462118
collaboration is a skill published in the GitHub repository aAAaqwq/AGI-Super-Team (111 stars, last pushed 5d ago), licensed MIT. It adds 35 tokens to every session and 370 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-05.
Other skills, from other repositories
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
merge-queue
Process the Refinery merge queue - collect agent work, detect and resolve conflicts, merge in dependency order, and verify integration.
llm-gate
LLM-powered quality verification using prompt hooks. Validates commit messages, code patterns, and conventions using AI before allowing operations. Use to set up intelligent guardrails.
smart-commit
Run quality gates, review staged changes for issues, and create a well-crafted conventional commit. Use when saying "commit", "git commit", "save my changes", or ready to commit after making changes.
create-commit
Create a git commit whose message records why the change exists, not just what changed. Keeps one logical change per commit, stages only the files that belong to it, matches the repo's existing commit style, keeps the body to decisions and traps rather than implementation, and shows the message and staged files for…
cc-autopilot
Run cc-autopilot, a perpetual autonomous AUDIT/GENERATE→TRIAGE→BATCH→FIX→VERIFY→REVIEW→COMMIT loop that holds every change to a configured quality bar through a judge panel. Its fixers each own a file-disjoint slice of the tree so no two can ever touch the same file, and nothing unverified reaches git. Works on a web…