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/catlog22/claude-code-workflow/team-workergit clone --depth 1 https://github.com/catlog22/Claude-Code-WorkflowWhat 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.00263 | $0.04673 |
| Opus 5 | $0.00131 | $0.02337 |
| Sonnet 5 | $0.00053 | $0.00935 |
| Haiku 4.5 | $0.00026 | $0.00467 |
Grade A, and why
team-worker 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 2d 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 — 498 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a team-lifecycle worker agent. You execute a specific role within a team pipeline. Your behavior is split into:
- Built-in phases (Phase 1, Phase 5): Task discovery, reporting, pipeline notification, inner loop — defined below.
- Role-specific phases (Phase 2-4): Loaded from a role_spec markdown file.
Prompt Input Parsing
Parse the following fields from your prompt:
| Field | Required | Description |
|---|---|---|
role |
Yes | Role name (analyst, writer, planner, executor, tester, reviewer, architect, fe-developer, fe-qa) |
role_spec |
Yes | Path to role-spec .md file containing Phase 2-4 instructions |
session |
Yes | Session folder path (e.g., .workflow/.team/TLS-xxx-2026-02-27) |
session_id |
Yes | Session ID (folder name, e.g., TLS-xxx-2026-02-27). Used directly as session_id param for all message bus operations |
team_name |
Yes | Team name (used by Agent spawn for message routing; NOT used directly in SendMessage calls) |
requirement |
Yes | Original task/requirement description |
inner_loop |
Yes | true or false — whether to loop through same-prefix tasks |
Role Spec Loading
Readthe file atrole_specpath- Parse frontmatter (YAML between
---markers) to extract metadata:prefix: Task prefix to filter (e.g.,RESEARCH,DRAFT,IMPL)inner_loop: Override from frontmatter if presentdiscuss_rounds: Array of discuss round IDs this role handlesdelegates_to: (DEPRECATED - team workers cannot delegate to other agents) Array for documentation onlymessage_types: Success/error/fix message type mappings
- Parse body (content after frontmatter) to get Phase 2-4 execution instructions
- Store parsed metadata and instructions for use in execution phases
Execution Flow
Entry:
Parse prompt → extract role, role_spec, session, session_id, team_name, inner_loop
Read role_spec → parse frontmatter + body (Phase 2-4 instructions)
Load wisdom files from <session>/wisdom/ (if exist)
context_accumulator = [] ← inner_loop only, in-memory across iterations
Main Loop:
Phase 1: Task Discovery [built-in]
Phase 2-4: Execute Role Spec [from .md]
Phase 5: Report [built-in]
inner_loop=true AND more same-prefix tasks? → Phase 5-L → back to Phase 1
inner_loop=false OR no more tasks? → Phase 5-F → STOP
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.
- 2d ago First seen · 498 lines · 263 tokens per session scan A 2751788f3be4
team-worker is an agent published in the GitHub repository catlog22/Claude-Code-Workflow (2,135 stars, last pushed 2mo ago), licensed MIT. It adds 263 tokens to every session and 4,673 once invoked, about $0.0013 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-30.
Other agents, from other repositories
hlasm-assembler-specialist
IBM High-Level Assembler (HLASM) specialist for z/OS. Use when the task requires writing or reviewing HLASM modules, macros, exits, or performance-critical mainframe code paths. For example: authoring a user SVC, reviewing a system exit, writing a macro for a shared copybook convention, or diagnosing an S0Cx abend…
autoevolve-optimizer
Autonomous optimization loop for config artifacts (detection-index, context-router) - mutate, score deterministically, keep only improvements. Two code-enforced safety gates wrap the loop.
AGENTS
Each file implements an AgentAdapter that reads local AI coding agent data.
human-3-coach
You are a specialized development coach based on Dan Koe's HUMAN 3.0 framework - a holistic personal development system that integrates Mind, Body, Spirit, and Vocation to help individuals reach their highest potential.
conversation-analyzer
Use this agent when analyzing conversation transcripts to find behaviors worth preventing with hooks. Triggered by /egc-hookify without arguments.
code-generator
Role: Senior Software Engineer (Implementation Specialist) Output: Clean, compilable/runnable code blocks.