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 agents/hulupeep/specflow/team-namesgit clone --depth 1 https://github.com/Hulupeep/SpecflowWrote 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/agents/hulupeep/specflow/team-names)<a href="https://agentmods.dev/agents/hulupeep/specflow/team-names"><img src="https://agentmods.dev/badge/agents/hulupeep/specflow/team-names.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 | $0.00000 | $0.02351 |
| Opus 5 | $0.00000 | $0.01175 |
| Sonnet 5 | $0.00000 | $0.00470 |
| Haiku 4.5 | $0.00000 | $0.00235 |
Grade A, and why
team-names 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 4d 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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Team Names
Overview
Agent Teams mode assigns mythic Irish names to agents instead of functional IDs like "issue-50". This makes completion messages memorable and gives each wave a distinct identity.
This is cosmetic. Agent behavior is defined entirely by prompts, not names. The CLAUDE_CODE_AGENT_TYPE env var still carries the functional role (e.g., "issue-lifecycle"). The name is just CLAUDE_CODE_AGENT_NAME.
Your team name is cosmetic. Your behavior is defined entirely by your agent prompt.
Team Names (CLAUDE_CODE_TEAM_NAME)
Teams are named after mythic Irish bands. The wave orchestrator picks one per wave:
| Team Name | Origin | Character | Best For |
|---|---|---|---|
| Fianna | Finn McCool's warband | Loyal, strategic, mobile | General-purpose waves |
| Tuatha | Tuatha De Danann (the gods) | Masterful, multi-skilled, luminous | Foundation / architecture waves |
| Red Branch | Ulster's warrior order | Fierce, disciplined, elite | Bug fix / combat waves |
| Brigid's Forge | Goddess of craft | Warm, precise, principled | Feature building waves |
| Tir na nOg | The Otherworld | Timeless, transformative, bold | Migration / refactor waves |
Singleton Role Names
These agents run once per team. Their names are fixed:
| Role | Name | From | Why |
|---|---|---|---|
| waves-controller | Finn McCool | Fenian Cycle | "Warrior-leader with salmon of knowledge; calm, strategic, protective" |
| db-coordinator | Hamilton | William Rowan Hamilton | "Abstract reasoning, pattern-finding, notation" — schema and numbers |
| quality-gate | Keane | Roy Keane | "Ruthless standards, fearless honesty" — nothing gets past the gate |
| journey-gate | Scathach | Warrior-trainer myth | "Legendary instructor; demanding, precise, formidable" — gating heroes |
Issue-Lifecycle Name Pools
Issue-lifecycle agents (one per issue) draw names from themed pools. The waves-controller picks the pool based on wave character, then assigns names round-robin.
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.
- 4d ago First seen · 220 lines · 0 tokens per session scan A d3c60620d81b
team-names is an agent published in the GitHub repository Hulupeep/Specflow (24 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,351 tokens. 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-30.
Other agents, from other repositories
api-architect
Use this agent PROACTIVELY when designing API architectures, defining contracts, planning integration patterns, making decisions about REST vs GraphQL, establishing authentication strategies, designing rate limiting systems, planning API versioning approaches, or creating OpenAPI specifications. Invoke for any API…
code-reviewer
Reviews code for bugs, logic errors, security vulnerabilities, code quality issues, and adherence to project conventions. Merges security review capabilities including OWASP validation, secrets scanning, and regression detection. Uses confidence-based filtering for quality issues and severity classification for…
architect
Code architecture analyst, optimization planner, and feature architecture designer. Reviews code from a design perspective, identifies architectural improvements, creates prioritized optimization plans, performs final quality assessments, and designs comprehensive implementation blueprints for new features.
refactor-code
Code implementation specialist for refactoring workflows. Implements architectural optimizations focusing on clean code principles, fixes test failures, and ensures all changes preserve existing functionality without introducing bugs.
code-explorer
Deep codebase discovery agent for refactoring and feature development workflows. Traces execution paths, maps architecture layers, catalogs dependencies, and produces structured codebase maps that feed all downstream agents. Runs as Phase 0.5 in refactoring or as parallel explorers in feature development.
feature-code
Implementation specialist for new feature development. Reads architecture blueprints and codebase context from the blackboard, then creates new code following established patterns and conventions. Designed for feature-dev workflows.