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/bryanweaver/claude-agent-kit/team-run-testsnpx skills add bryanweaver/claude-agent-kit --skill team-run-testsgit clone --depth 1 https://github.com/bryanweaver/claude-agent-kitWrote 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/bryanweaver/claude-agent-kit/team-run-tests)<a href="https://agentmods.dev/skills/bryanweaver/claude-agent-kit/team-run-tests"><img src="https://agentmods.dev/badge/skills/bryanweaver/claude-agent-kit/team-run-tests.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.00020 | $0.00920 |
| Opus 5 | $0.00010 | $0.00460 |
| Sonnet 5 | $0.00004 | $0.00184 |
| Haiku 4.5 | $0.00002 | $0.00092 |
Grade A, and why
team-run-tests 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test — Batch Test and Fix
Run all tests, batch-fix failures, and verify. Loops until green.
Test scope: $ARGUMENTS
Execution
With Agent Teams (recommended)
Enable with CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1
Create a team and spawn teammates:
- Create team named
test-run - Spawn teammates: shipper, full-stack-developer, database-admin, reviewer, documentor
Create the following task list with dependencies:
| # | Task | Owner | Blocked By |
|---|---|---|---|
| 1 | Create branch test/<timestamp> from main |
shipper | — |
| 2 | Run full test suite, compile failure report | shipper | 1 |
| 3 | Fix application test failures (dynamic sub-tasks per failure) | full-stack-developer | 2 |
| 4 | Fix data layer test failures (dynamic sub-tasks per failure) | database-admin | 2 |
| 5 | Commit all fixes | shipper | 3, 4 |
| 6 | Re-run previously failed tests | shipper | 5 |
| 7 | Run full validation suite | shipper | 6 |
| 8 | Review all fixes for quality | reviewer | 7 |
| 9 | Update documentation if fixes affect docs | documentor | 8 |
| 10 | Create PR to main with test report | shipper | 8, 9 |
Parallelism: Tasks 3 and 4 can run simultaneously.
Loop: If task 6 finds remaining failures, create new fix tasks and loop back to task 6.
Dynamic tasks: After task 2, create specific sub-tasks for each failure group and assign to the appropriate developer.
Without Agent Teams (fallback)
Execute sequentially using the Task tool:
Task(shipper, "Create branch test/<timestamp> from main")Task(shipper, "Run full test suite, report all failures")- For each failure group:
Task(full-stack-developer, "Fix: <failure details>")— for app failuresTask(database-admin, "Fix: <failure details>")— for data failures
Task(shipper, "Commit fixes: fix: <test-name> - <description>")Task(shipper, "Re-run previously failed tests")- If still failing, loop back to step 3
Task(shipper, "Run full test suite for final validation")Task(reviewer, "Review all test fixes")Task(documentor, "Update docs if test fixes changed documented behavior")Task(shipper, "Create PR to main with test report")
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 · 82 lines · 20 tokens per session scan A 2f1ea4e68895
team-run-tests is a skill published in the GitHub repository bryanweaver/claude-agent-kit (2 stars, last pushed 2mo ago), licensed MIT. It adds 20 tokens to every session and 920 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…
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…