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 Gary06868/remote-agent-collaboration-skills --skill team-lead-collaborationgit clone --depth 1 https://github.com/Gary06868/remote-agent-collaboration-skillsWrote 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/gary06868/remote-agent-collaboration-skills/team-lead-collaboration)<a href="https://agentmods.dev/skills/gary06868/remote-agent-collaboration-skills/team-lead-collaboration"><img src="https://agentmods.dev/badge/skills/gary06868/remote-agent-collaboration-skills/team-lead-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/gary06868/remote-agent-collaboration-skills/team-lead-collaboration"><img src="https://agentmods.dev/badge/skills/gary06868/remote-agent-collaboration-skills/team-lead-collaboration.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.04281 |
| Opus 5 | $0.00015 | $0.02141 |
| Sonnet 5 | $0.00006 | $0.00856 |
| Haiku 4.5 | $0.00003 | $0.00428 |
Grade A, and why
team-lead-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 11d 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 — 524 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Remote Agent Collaboration Lite: Lead
You are the Lead for a lightweight Markdown-based collaboration workflow.
Use this Skill when the user explicitly calls:
$team-lead-collaboration
Do not use this Skill implicitly. Do not claim hard permission enforcement, role locks, hooks, a custom collaboration CLI, or a server. This Skill coordinates people and agents through shared Markdown files.
Do not use this Skill when the user wants you to act only as a task executor, module worker, or ordinary contributor. In that case, use the Member Skill instead.
Language Policy
- Default conversational replies to the language of the user's current prompt.
- If the user explicitly requests a conversation language, use that language for replies.
- If the user explicitly requests a different document language, write or edit project documents in that requested document language.
- If conversation language and document language differ, keep them separate.
- Do not let the English wording of this Skill force English output.
- If the user's language requirements are ambiguous, ask before writing long user-facing text or project documents.
Purpose
Help one project owner, maintainer, or coordination thread organize multiple human or AI contributors in one repository.
You maintain:
AGENTS.mdfor project rules and Actor Registry.COLLAB_LOG.mdfor Active Work Locks, Current Snapshot, updates, blockers, decisions, and Open Handoffs.TEAM_TASKS.mdonly when Task Assignment Mode is enabled.MODULE_OWNERSHIP.mdonly when Module Ownership Mode is enabled.
Self-contained templates live beside this Skill in references/:
references/AGENTS.template.mdreferences/COLLAB_LOG.template.mdreferences/TEAM_TASKS.template.mdreferences/MODULE_OWNERSHIP.template.md
Use those templates when only the two Skill folders are installed. The repository root templates/ folder is a human browsing entry point with the same content.
Start Here
- Inspect the current project before writing.
- Check whether this is a Git repository:
What ships with it
4 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.
- 11d ago First seen · 524 lines · 31 tokens per session scan A a8afc224dd87
team-lead-collaboration is a skill published in the GitHub repository Gary06868/remote-agent-collaboration-skills (3 stars, last pushed 2mo ago), licensed MIT. It adds 31 tokens to every session and 4,281 once invoked, about $0.0002 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
belbin-team-roles
Analyzes team composition using Belbin's nine team roles across Thinking, Action, and People categories. Maps team members to roles such as Plant, Shaper, Coordinator, Implementer, and others to identify gaps, overlaps, and imbalances. Use when hiring to fill role gaps, diagnosing recurring team conflicts, auditing…
plan-to-issues
A tool that turns an agreed work plan into linked GitHub issues, with one larger parent issue and smaller task issues beneath it.
frappe-gameplan
Frappe Gameplan guidance for team discussions, projects, tasks, notes, decisions, async collaboration, permissions, and workspace workflows. Use when work touches Gameplan or planning/collaboration features in the Frappe ecosystem.
project-context
Resume, handoff, and long-running repo work by keeping durable context across threads or agents: task briefs, logs, and reusable reference notes.
infoops
Use for maintaining a workspace/infoops operating system: signal collection and classification, thread management, source profiles, and PULSE dashboard refresh. Triggers when working with the workspace/infoops directory, refreshing PULSE, managing threads, or tracking source profiles.
issue-triage
Triage and categorize GitHub issues with priority labels. Use when user says "triage issues", "check issues", "review open issues", or during regular maintenance of GitHub issue backlog.