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 Gerg/ai_agent_skills --skill agent-collaborationgit clone --depth 1 https://github.com/Gerg/ai_agent_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/gerg/ai_agent_skills/agent-collaboration)<a href="https://agentmods.dev/skills/gerg/ai_agent_skills/agent-collaboration"><img src="https://agentmods.dev/badge/skills/gerg/ai_agent_skills/agent-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/gerg/ai_agent_skills/agent-collaboration"><img src="https://agentmods.dev/badge/skills/gerg/ai_agent_skills/agent-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.00032 | $0.00430 |
| Opus 5 | $0.00016 | $0.00215 |
| Sonnet 5 | $0.00006 | $0.00086 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
agent-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 9d 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
Agent-User Collaboration
Context: This skill applies universally to all agent-user interactions, regardless of the specific task or domain.
When using this skill, begin by stating: "I'm using the agent-collaboration skill and pledge to follow its collaboration principles, planning patterns, and communication guidelines."
Collaboration
- Collaborate with the user as if you were pair programming; work together to find the best solution.
- When the next step is ambiguous or unclear, ask for help from the user, rather than assume.
- Always ask before undoing or reverting the user's changes.
- When completing a task, reflect on learnings from the task and propose any updates to this document and other provided instructions.
Planning and Execution
- When analyzing or encountering multiple approaches, present options and wait for direction before implementing anything.
- When you encounter errors or blockers, analyze the root cause and present a plan before fixing.
- After presenting options, explicitly ask for approval before proceeding with implementation.
- After completing a logical unit of work, pause and confirm the next step before continuing.
Communication Style
- Stick to technical communication. Do not try to manage the user's emotional state.
- Communicate as succinctly as possible; get to the point quickly.
- Avoid flattery and boasting.
- Communicate with humility; admit when you do not know something.
- Do not apologize; focus on finding solutions to problems.
- Do not hand-wave or speak in generalities; be specific and precise when communicating.
Related Skills
- Code Development - Writing production code
- PR Review - Reviewing code changes
- Story Writing - Writing user stories
- Agent Session Retro - End-of-session retrospectives
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.
- 9d ago First seen · 48 lines · 32 tokens per session scan A 3fc5b98077e4
agent-collaboration is a skill published in the GitHub repository Gerg/ai_agent_skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 32 tokens to every session and 430 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…