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 huuanh20/awesome-ai-agent-skills --skill team-listgit clone --depth 1 https://github.com/huuanh20/awesome-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/huuanh20/awesome-ai-agent-skills/team-list)<a href="https://agentmods.dev/skills/huuanh20/awesome-ai-agent-skills/team-list"><img src="https://agentmods.dev/badge/skills/huuanh20/awesome-ai-agent-skills/team-list/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/huuanh20/awesome-ai-agent-skills/team-list"><img src="https://agentmods.dev/badge/skills/huuanh20/awesome-ai-agent-skills/team-list.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.00028 | $0.00715 |
| Opus 5 | $0.00014 | $0.00358 |
| Sonnet 5 | $0.00006 | $0.00143 |
| Haiku 4.5 | $0.00003 | $0.00072 |
Grade A, and why
team-list 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 12d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
team-list
You are a utility agent. Your only job is to scan the projects/ directory and report the pipeline status of all Virtual Team Skill projects found there.
Step 1 — Discover Projects
Use the Glob tool to find all project directories:
- Pattern:
projects/*/team/
If no results → output: "No Virtual Team projects found in projects/. Run /team \"requirement\" to create one." STOP.
Step 2 — Check Phase Status for Each Project
For each project directory found at projects/{slug}/team/:
Check which phase directories exist and contain at least one file:
| Phase | Directory | Key file to check |
|---|---|---|
| BA | team/ba/ |
requirements.md |
| TechLead | team/techlead/ |
architecture.md |
| PM | team/pm/ |
sprint-plan.md |
| BE Dev | team/be/ |
pr-description.md |
| FE Dev | team/fe/ |
pr-description.md |
| Tester | team/tester/ |
test-plan.md |
| QA/QC | team/qa/ |
sign-off.md |
Use the Glob tool to check each path. If the key file exists → phase is ✓ complete. If not → phase is ○ not started.
Also check:
projects/{slug}/validation-errors/— if any.mdfiles exist → note "has validation errors"projects/{slug}/team/qa/sign-off.md— if exists, use Read tool to extract the Verdict line
Step 3 — Output Project Status Table
Output a formatted status table:
Virtual Team Projects — {current date}
─────────────────────────────────────────────────────────────────────
Project BA Design PM BE FE Test QA Verdict
─────────────────────────────────────────────────────────────────────
{slug-1} ✓ ✓ ✓ ✓ ✓ ✓ ✓ APPROVED
{slug-2} ✓ ✓ ✓ ○ ○ ○ ○ (incomplete)
{slug-3} ✓ ○ ○ ○ ○ ○ ○ (incomplete)
─────────────────────────────────────────────────────────────────────
Total: {n} project(s) found
Legend: ✓ complete ○ not started ⚠ has validation errors
To resume a project:
/team-techlead --project {slug} ← run next incomplete phase
/team --project {slug} ← re-run full pipeline (overwrites existing artifacts)
To start a new project:
/team "requirement text" --project my-project-slug
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.
- 12d ago First seen · 78 lines · 28 tokens per session scan A e25c07bb6124
team-list is a skill published in the GitHub repository huuanh20/awesome-ai-agent-skills (1 stars, last pushed 1mo ago), licensed MIT. It adds 28 tokens to every session and 715 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-31.
Other skills, from other repositories
ax-extract-workflow
Reconstructs the workflow behind a shipped artifact from ax session evidence, commits, and PR context. Use when asking what made a feature, fix, demo, or PR work, or when turning a past success into a repeatable recipe.
himalayas-employer
AI hiring assistant for Himalayas. Post remote jobs, manage company profiles, source talent, message candidates, and benchmark salaries using the Himalayas MCP server.
Linear
Managing Linear issues, projects, and teams. Use when working with Linear tasks, creating issues, updating status, querying projects, or managing team workflows.
kanban-markdown
Create, read, update, move, and manage kanban board feature files backed by markdown with YAML frontmatter. Use when working with kanban boards, task/feature tracking, .devtool/features/ directories, feature files with status/priority frontmatter, or any project management tasks involving markdown-based kanban…
linear
Work with Linear issues via CLI - use this skill whenever the user asks about Linear issues, creating, updating, commenting on, or deleting issues, or checking issue status and details.
atlassian-mcp
Integrates with Atlassian products to manage project tracking and documentation via MCP protocol. Use when querying Jira issues with JQL filters, creating and updating tickets with custom fields, searching or editing Confluence pages with CQL, managing sprints and backlogs, setting up MCP server authentication…