Borrowing it
Nothing to install: this file belongs to Caspian-Sun/claude-code-workflow. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Caspian-Sun/claude-code-workflow/main/.claude/agents/README.mdgit clone --depth 1 https://github.com/Caspian-Sun/claude-code-workflowWrote 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/caspian-sun/claude-code-workflow/readme)<a href="https://agentmods.dev/agents/caspian-sun/claude-code-workflow/readme"><img src="https://agentmods.dev/badge/agents/caspian-sun/claude-code-workflow/readme/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/caspian-sun/claude-code-workflow/readme"><img src="https://agentmods.dev/badge/agents/caspian-sun/claude-code-workflow/readme.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00901 |
| Opus 5.5 | $0.00000 | $0.00360 |
| Sonnet 5.5 | $0.00000 | $0.00180 |
| Haiku 4.5 | $0.00000 | $0.00090 |
Grade A, and why
README 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 2mo 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agents/ — Sub-Agent Definitions
Specialized agents spawned by main commands via the
Agenttool, each running in an independent context, supporting parallelism without polluting the main session.
File Manifest
| Agent | Responsibility | Spawned By |
|---|---|---|
| test-writer.md | Generate tests for specified source files (reads @rules → writes it() per rule) |
After /code completes / /test for multi-module parallelism |
| code-reviewer.md | Read-only review of a file/directory, outputs issue list | /review splitting large directories / pre-PR self-check |
| bug-fixer.md | Fix a single bug (from bug-report) | /fix for parallel handling of multiple bug reports |
| meta-auditor.md | God-mode meta-audit, scans the entire codebase for inconsistencies/drift/dead links, outputs report to docs/retrospectives/ |
Triggered by /meta-audit command |
Sub-Agents vs. Slash Commands
| Slash Commands (commands/) | Sub-Agents (agents/) | |
|---|---|---|
| Runs in | Main context | Independent context (created at spawn time) |
| Parallel | No, serial execution | Yes, multiple agents can run concurrently |
| Memory | Full main session visible | Only sees the passed-in prompt |
| Output | Written directly to main session | Returns a summary to main agent |
| Best for | User-triggered workflows | Independent sub-tasks spawned inside main commands |
Why sub-agents:
- Parallel acceleration — 5 independent bugs reported in tests → spawn 5
bug-fixeragents in parallel, 5× faster than serial - Protect main context — reviewing a large directory reads many files; stuffing that into main context quickly overflows; let sub-agents run and return summaries
- Responsibility isolation — sub-agents only see the passed-in prompt, free from main session pollution, producing more focused output
Agent MD File Format
---
name: <agent-name> # Unique identifier, matches filename
description: <one sentence> — when to spawn # Main agent uses this to decide whether to use it
tools: [Read, Edit, Write, Bash, Grep, Glob] # Optional, inherits by default
---
# <agent-name>
<Complete system prompt: role / input / execution steps / output format / boundaries>
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.
- 2mo ago First seen · 73 lines · 0 tokens per session scan A 2191b5302607
README is an agent published in the GitHub repository Caspian-Sun/claude-code-workflow (10 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 901 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-31.
Other agents, from other repositories
check
Code quality auditor for the Trellis channel runtime. Reviews uncommitted diffs against task artifacts and specs, self-fixes issues, and reports verification results.
planner
Strategic planning agent — read-only exploration before implementation. Use to decompose tasks, analyze codebases, and produce a detailed plan. Never modifies files.
implementer
Executes well-scoped implementation tasks with clear specifications. Use when the plan is defined and subtasks have explicit "done when" criteria. Not for architecture decisions or ambiguous tasks.
ux-designer
An interface-review role focused on how easily users can reach their goal, using screenshots, brand rules, and concrete design suggestions.
data-validate
Run dbt and Snowflake validation via agentic-workstation HOW skills and report evidence.
project-manager
The user-facing interface for every session. The user talks to the PM — not to a neutral assistant. PM owns the roadmap, challenges scope, approves work, and routes everything through the forge. Does not write code or touch implementation files.