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.
git clone --depth 1 https://github.com/jezweb/claude-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/commands/jezweb/claude-skills/team-update)<a href="https://agentmods.dev/commands/jezweb/claude-skills/team-update"><img src="https://agentmods.dev/badge/commands/jezweb/claude-skills/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.00012 | $0.00186 |
| Opus 5 | $0.00006 | $0.00093 |
| Sonnet 5 | $0.00002 | $0.00037 |
| Haiku 4.5 | $0.00001 | $0.00019 |
Grade B, and why
team-update scanned grade B 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 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
allowed-tools: "*" What it actually says
Load the team-update skill and execute based on $ARGUMENTS:
| Argument | Action |
|---|---|
update |
Full cycle: gather context, draft, post, read feedback, triage |
check |
Read and triage team feedback only (Phase 3) |
standup |
Gather and post update, skip feedback (Phase 1 + 2) |
feedback |
Read feedback and plan next steps (Phase 3 + 4) |
plan |
Gather, post, and plan — skip feedback triage (Phase 1 + 2 + 4) |
| (none) | Default to full cycle (update) |
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 · 17 lines · 12 tokens per session scan B 4c49d7c5ed74
team-update is a command published in the GitHub repository jezweb/claude-skills (995 stars, last pushed 2mo ago), licensed MIT. It adds 12 tokens to every session and 186 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
portfolio-status
Review the health of all projects in the portfolio.
pr
Create a pull request using the git-pushing skill.
update-docs
Scan for recently modified files and update corresponding documentation.
handoff
Create a handoff document for seamless session continuity.
roadmap-track.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
vision-adjust.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.