Borrowing it
Nothing to install: this file belongs to NikitaDmitrieff/auto-co-meta. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/NikitaDmitrieff/auto-co-meta/main/.claude/skills/team/SKILL.mdgit clone --depth 1 https://github.com/NikitaDmitrieff/auto-co-metaWrote 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/nikitadmitrieff/auto-co-meta/team)<a href="https://agentmods.dev/skills/nikitadmitrieff/auto-co-meta/team"><img src="https://agentmods.dev/badge/skills/nikitadmitrieff/auto-co-meta/team.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.1 | $0.00026 | $0.00761 |
| Opus 5 | $0.00013 | $0.00380 |
| Sonnet 5 | $0.00005 | $0.00152 |
| Haiku 4.5 | $0.00003 | $0.00076 |
Grade A, and why
team 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 8d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Assemble Temporary Team
Based on the task below, select the most suitable members from the company's AI Agents and form a temporary team to collaborate on it.
Task
$ARGUMENTS
Available Agents
All agents are defined in .claude/agents/:
| Agent | File | Role |
|---|---|---|
| CEO | ceo-bezos |
Strategic decisions, business models, PR/FAQ, prioritization |
| CTO | cto-vogels |
Technical architecture, technology selection, system design |
| Critic | critic-munger |
Challenge decisions, identify fatal flaws, Pre-Mortem, prevent groupthink |
| Product Design | product-norman |
Product definition, user experience, usability |
| UI Design | ui-duarte |
Visual design, design system, color and typography |
| Interaction Design | interaction-cooper |
User flows, Personas, interaction patterns |
| Full-Stack Dev | fullstack-dhh |
Code implementation, technical proposals, development |
| QA | qa-bach |
Test strategy, quality gates, bug analysis |
| DevOps/SRE | devops-hightower |
Deployment pipelines, CI/CD, infrastructure, monitoring |
| Marketing | marketing-godin |
Positioning, brand, acquisition, content |
| Operations | operations-pg |
User operations, growth, community, PMF |
| Sales | sales-ross |
Sales funnel, conversion strategy |
| CFO | cfo-campbell |
Pricing strategy, financial models, cost control, unit economics |
| Research | research-thompson |
Market research, competitive analysis, industry trends, opportunity discovery |
Execution Steps
1. Analyze the Task, Select Members
Select 2-5 of the most relevant Agents as team members based on the task. Selection principles:
- Only pick who's needed -- more people is not better; match precisely to the task
- Consider the collaboration chain -- if the task spans design to development, include key roles along the chain
- Avoid redundancy -- don't select agents with overlapping roles
Briefly state who you selected and why, then immediately begin assembling the team.
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.
- 8d ago First seen · 69 lines · 26 tokens per session scan A c30959419fcc
team is a skill published in the GitHub repository NikitaDmitrieff/auto-co-meta (43 stars, last pushed 2mo ago), licensed MIT. It adds 26 tokens to every session and 761 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-30.
Other skills, from other repositories
browser-automation
Playwright-based browser automation patterns for autonomous web interaction.
a2ui-renderer
Render A2UI (Agent-to-UI declarative surfaces) in CopilotKit v2. Enable the runtime via CopilotRuntime({ a2ui: {...} }), then enable the provider via . Auto-activates via /info — do NOT manually pass renderActivityMessages. createA2UIMessageRenderer ships from @copilotkit/react-core/v2; low-level primitives…
copilotkit-develop
Use when building AI-powered features with CopilotKit v2 -- adding chat interfaces, registering frontend tools, sharing application context with agents, handling agent interrupts, and working with the CopilotKit runtime.
copilotkit-upgrade
Use when migrating a CopilotKit v1 application to v2 -- updating package imports, replacing deprecated hooks and components, switching from GraphQL runtime to AG-UI protocol runtime, and resolving breaking API changes.
dws
A command-line guide for DingTalk, a workplace platform with chat, documents, calendars, approvals, tasks, and other business tools.
clip-hand-skill
Expert knowledge for AI video clipping — yt-dlp downloading, whisper transcription, SRT generation, and ffmpeg processing.