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/updatenpx skills add fengjunhui31/building-autonomous-team --skill updategit 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/update)<a href="https://agentmods.dev/skills/fengjunhui31/building-autonomous-team/update"><img src="https://agentmods.dev/badge/skills/fengjunhui31/building-autonomous-team/update.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.00028 | $0.02250 |
| Opus 5 | $0.00014 | $0.01125 |
| Sonnet 5 | $0.00006 | $0.00450 |
| Haiku 4.5 | $0.00003 | $0.00225 |
Grade C, and why
building-autonomous-team-update scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf ~/.claude/plugins/cache/building-autonomous-team How it starts
The opening of the file, as written. The whole thing — 284 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Autonomous Team Update Skill (v2.0)
Overview
Update agent definitions and workflow rules to latest version without reinitializing.
v2.0 major changes:
- 9 persistent agents → 2 persistent + dynamic
- Local state files → GitHub-only state
- New roles: facilitator (merged 4), mission-analyst (new)
- Removed roles: discussion-facilitator, consensus-manager, spec-writer, merge-manager, env-manager
Step 0: Pre-check
0.1 Check Team Exists
ls .autonomous-team/workflow.md .claude/agents/ 2>/dev/null || echo "NO_TEAM"
If NO_TEAM: Block. Run /building-autonomous-team to initialize first.
0.2 Check Remote Plugin Version
Before anything else, check if the installed plugin is up-to-date with the remote marketplace:
# Current installed plugin version
LOCAL_PLUGIN_VERSION=$(cat ${CLAUDE_PLUGIN_ROOT}/.claude-plugin/plugin.json | jq -r '.version')
# Fetch latest version from remote marketplace (GitHub)
REMOTE_PLUGIN_VERSION=$(gh api repos/fengjunhui/building-autonomous-team/contents/.claude-plugin/marketplace.json \
--jq '.content' | base64 -d | jq -r '.plugins[0].version')
echo "Local plugin: $LOCAL_PLUGIN_VERSION | Remote: $REMOTE_PLUGIN_VERSION"
If REMOTE > LOCAL (plugin itself needs update):
⚠️ Plugin update available: v{LOCAL} → v{REMOTE}
Updating plugin first...
# Clear cache and reinstall
rm -rf ~/.claude/plugins/cache/building-autonomous-team
claude plugin uninstall building-autonomous-team@building-autonomous-team
claude plugin install building-autonomous-team@building-autonomous-team
After plugin update completes, inform user:
✅ Plugin updated to v{REMOTE}.
Please restart this session for the new plugin to take effect,
then run `/building-autonomous-team` again to update the team.
STOP HERE — the new plugin version may contain different update logic. User must restart session.
If REMOTE == LOCAL (plugin is current): Continue to Step 0.3.
0.3 Compare Team Version
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 · 284 lines · 28 tokens per session scan C 50250bbea8ce
building-autonomous-team-update is a skill published in the GitHub repository fengjunhui31/building-autonomous-team (2 stars, last pushed 4mo ago), licensed MIT. It adds 28 tokens to every session and 2,250 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). 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…
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…
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…