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 agentmods add skills/fengjunhui31/building-autonomous-team/runnpx skills add fengjunhui31/building-autonomous-team --skill rungit clone --depth 1 https://github.com/fengjunhui31/building-autonomous-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/fengjunhui31/building-autonomous-team/run)<a href="https://agentmods.dev/skills/fengjunhui31/building-autonomous-team/run"><img src="https://agentmods.dev/badge/skills/fengjunhui31/building-autonomous-team/run.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.01415 |
| Opus 5 | $0.00013 | $0.00707 |
| Sonnet 5 | $0.00005 | $0.00283 |
| Haiku 4.5 | $0.00003 | $0.00142 |
Grade A, and why
building-autonomous-team-run 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 5d 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 — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Autonomous Team Operation Skill (v2.0)
Overview
Resume team operation: pre-flight checks, recover Project Manager, start monitoring loop.
v2.0 changes: Only 1 persistent agent to recover (Project Manager). State reconstructed from GitHub, not local files. Team Lead is sole agent spawner — all dynamic roles spawned as team members via SendMessage requests from Project Manager.
Step 0: Pre-flight Git State Detection
CRITICAL: Detect and clean up state from previous interrupted session.
0.1 Check Working Directory
git status --porcelain
- Clean → Continue
- Dirty → Warn user: "Uncommitted changes detected. Please commit or stash before proceeding."
0.2 Check Stashes
git stash list
- Empty → Continue
- Has stashes → Warn user: "Git stashes found. Review with
git stash list."
0.3 Clean Orphan Worktrees
git worktree list
- Only main worktree → Continue
- Extra worktrees → Clean up:
git worktree prune # For each remaining orphan: git worktree remove {path} --force
0.4 Detect Orphan PRs
gh pr list --state open --json number,title,headRefName
For each open PR:
- Record for Project Manager to handle during state reconstruction
0.5 Sync with Remote
git pull origin master --ff-only
- Success → Continue
- Fail → Warn user: "Cannot fast-forward. Please resolve manually."
Step 1: Read Config
cat .autonomous-team/config.json
Extract: language, boss_github_username, version, mission_checkpoint_interval
Step 2: Responsibility Coverage Check
RESPONSIBILITIES="topic_collect topic_schedule flow_advancement discussion_create consensus_facilitate spec_write spec_freeze perspective_post technical_solution code_implement code_review feature_accept security_review pr_merge executor_cleanup env_support perspective_spawn github_scan boss_resource mission_analysis heartbeat liveness_check"
missing=0
for resp in $RESPONSIBILITIES; do
search_term=$(echo "$resp" | sed 's/_/ /g')
count=$(grep -rl "$search_term\|$resp" .claude/agents/*.md .autonomous-team/workflow.md 2>/dev/null | wc -l | tr -d ' ')
if [ "$count" -eq 0 ]; then
echo "MISSING: $resp"
missing=$((missing + 1))
fi
done
if [ "$missing" -gt 0 ]; then
echo "CRITICAL: Team configuration incomplete."
fi
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.
- 5d ago First seen · 219 lines · 26 tokens per session scan A 8ea23e9adb4a
building-autonomous-team-run is a skill published in the GitHub repository fengjunhui31/building-autonomous-team (2 stars, last pushed 4mo ago), licensed MIT. It adds 26 tokens to every session and 1,415 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
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…