team-add-tests

team-add-tests is a skill for Claude Code from bryanweaver/claude-agent-kit. It costs 18 tokens per session (843 once invoked), scanned A, original, MIT.

A workflow for adding tests only around functionality whose failure could cause serious production harm. It can divide the work among specialists such as developers, reviewers, and database administrators.

In plain words
What is it for?
Use it to identify critical untested paths, write focused tests, run the full test suite, and document the coverage. It can also organize the work into a branch and pull request.
Why use it?
It concentrates testing effort on risks such as broken access control, lost data, payment failures, or major outages. This avoids spending the same effort on low-impact behavior.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the team plugin — 17 skills, 7 agents, 1 hook shipped together

Install

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.

agentmods
npx agentmods add skills/bryanweaver/claude-agent-kit/team-add-tests
Any agent
npx skills add bryanweaver/claude-agent-kit --skill team-add-tests
Clone the repo
git clone --depth 1 https://github.com/bryanweaver/claude-agent-kit

Made for: Claude Code.

Or install team, the plugin that ships this one along with the rest of its 17 skills, 7 agents, 1 hook.

Wrote 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.

agentmods badge for team-add-tests

README.md
[![agentmods](https://agentmods.dev/badge/skills/bryanweaver/claude-agent-kit/team-add-tests.svg)](https://agentmods.dev/skills/bryanweaver/claude-agent-kit/team-add-tests)
Your own site
<a href="https://agentmods.dev/skills/bryanweaver/claude-agent-kit/team-add-tests"><img src="https://agentmods.dev/badge/skills/bryanweaver/claude-agent-kit/team-add-tests.svg" alt="Measured on agentmods" height="20"></a>
Per session 18 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 843 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00018 $0.00843
Opus 5 $0.00009 $0.00421
Sonnet 5 $0.00004 $0.00169
Haiku 4.5 $0.00002 $0.00084

Measured 5d ago against content hash 394112b0bd4b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

team-add-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.

skills/team-add-tests/SKILL.md · 78 lines

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.

Add Tests — Critical Test Coverage

Add tests for CRITICAL functionality only. Test the 20% that prevents 80% of disasters.

Area to cover: $ARGUMENTS

Execution

With Agent Teams (recommended)

Enable with CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1

Create a team and spawn teammates:

  1. Create team named add-tests-<area-slug>
  2. Spawn teammates: shipper, reviewer, full-stack-developer, database-admin (if data layer), documentor

Create the following task list with dependencies:

# Task Owner Blocked By
1 Create branch test/critical-coverage-<area> from main shipper
2 Identify CRITICAL untested code paths reviewer 1
3 Write minimal tests for critical application paths full-stack-developer 2
4 Write minimal tests for critical data integrity paths (if needed) database-admin 2
5 Run full test suite including new tests shipper 3, 4
6 Update documentation for new test coverage documentor 5
7 Commit and create PR to main shipper 5, 6

Critical = code that could:

  • Break authentication or authorization
  • Lose or corrupt user data
  • Break payments or money flow
  • Cause a production outage

Skip tests for:

  • UI formatting and styling
  • Nice-to-have features
  • Edge cases that won't impact production
  • Anything that can be quickly fixed if it breaks

Parallelism: Tasks 3 and 4 can run simultaneously.

Without Agent Teams (fallback)

Execute sequentially using the Task tool:

  1. Task(shipper, "Create branch test/critical-coverage-<area> from main")
  2. Task(reviewer, "Identify CRITICAL untested code in $ARGUMENTS — focus on auth, data integrity, payments, outage risks")
  3. Task(full-stack-developer, "Write minimal tests for critical paths: <reviewer findings>")
  4. Task(database-admin, "Write data integrity tests: <reviewer findings>") — only if needed
  5. Task(shipper, "Run full test suite including new tests")
  6. Task(documentor, "Update docs to reflect new test coverage for: $ARGUMENTS")
  7. Task(shipper, "Commit and create PR: test: add critical coverage for <area>")

Read the full file on GitHub · 78 lines

Changes

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.

  1. 5d ago First seen · 78 lines · 18 tokens per session scan A 394112b0bd4b

Subscribe to this mod's changes

team-add-tests is a skill published in the GitHub repository bryanweaver/claude-agent-kit (2 stars, last pushed 2mo ago), licensed MIT. It adds 18 tokens to every session and 843 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 103 tokens

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…

microsoft/vscode · 72 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens