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 instructions/caspian-sun/claude-code-workflow/claude-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/instructions/caspian-sun/claude-code-workflow/claude-md)<a href="https://agentmods.dev/instructions/caspian-sun/claude-code-workflow/claude-md"><img src="https://agentmods.dev/badge/instructions/caspian-sun/claude-code-workflow/claude-md.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.01385 | $0.01385 |
| Opus 5 | $0.00692 | $0.00692 |
| Sonnet 5 | $0.00277 | $0.00277 |
| Haiku 4.5 | $0.00138 | $0.00138 |
Grade A, and why
claude-code-workflow CLAUDE.md 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Configuration — AI Frontend Automation Knowledge Base
Onboarding for Claude Code. Detailed rules are split under
.claude/rules/and loaded on demand. When a specific scenario comes up, read the relevant rule file first, then execute.
Project Structure
This project has two layers:
| Layer | Directory | Responsibility |
|---|---|---|
| Root | .claude/ / docs/ / CLAUDE.md |
AI automation framework (commands / rules / PRDs / tasks) |
| workspace/ | workspace/src/ / workspace/config/ / ... |
The actual frontend project (UmiJS) |
Commands like pnpm dev / pnpm gen:api at the root automatically proxy into workspace/, so you never have to cd manually.
P0 No Hardcoding (Highest Priority)
Every variable value is introduced via config / constants / Design Tokens / i18n — never hardcoded. Config itself must not duplicate; reuse hierarchically. Covers: copy i18n, colors and styles, API endpoints, business enums, sizes and spacing, magic numbers.
Detailed rules and examples → .claude/rules/no-hardcode.md
Tech Stack (Summary)
UmiJS 4 + React 18 + TypeScript 5 + Ant Design 5 (@umijs/max)
- Routing: Umi convention-based routing | Requests: @umijs/plugin-request | State: useModel + Zustand
- Build: Umi + Vite mode | Lint: @umijs/lint | Package manager: pnpm
- Do not install dependencies that Umi already bundles (axios / react-router-dom / webpack, etc.)
Full tech stack and project structure → .claude/rules/tech-stack.md
Coding Style (Summary)
- Comments explain "why," not restate code; file-header JSDoc is mandatory; commented-out code is deleted outright
- Components PascalCase / hooks
useprefix / constants UPPER_SNAKE_CASE / types withoutIprefix - Function components + exported Props interface + logic extracted to hooks + components only render
- Requests use umi-request; interceptors live in app.ts; no axios
- State: useModel first → Zustand as fallback → server data never goes in the store
- Routing: convention-based first; permissions via @umijs/plugin-access + wrappers
- Git:
type(scope): description; branchesfeature/fix/refactor/
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 · 120 lines · 1,385 tokens per session scan A 67fc95004142
claude-code-workflow CLAUDE.md is an instructions file published in the GitHub repository Caspian-Sun/claude-code-workflow (10 stars, last pushed 4d ago), licensed MIT. It adds 1,385 tokens to every session, about $0.0069 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 instructions, from other repositories
telegram-ai-bridge AGENTS.md
AGENTS.md instructions for AliceLJY/telegram-ai-bridge, covering telegram-ai-bridge agent rules, 1. plan before coding, 2. follow repo constraints, 3. closed-loop verification is mandatory and 4. make workflow reusable.
vibe-coding-prompt-template backend.instructions.md
Instructions for KhazP/vibe-coding-prompt-template: Read AGENTS.md, agentdocs/techstack.md, and agentdocs/codepatterns.md.
FDEOps AGENTS.md
Instructions for suboss87/FDEOps, covering agents.md - working in the fdeops repository, if you are helping use fdeops in an engagement, if you are contributing to this repository and boundaries.
Library-First-Engineering copilot-instructions.md
Instructions for StChiotis/Library-First-Engineering: You are an AI agent operating in a Library-First Engineering (LFE) repository. This adapter is a pointer. Canonical rules live in human-readable docs.
festival GEMINI.md
Gemini CLI instructions for Obedience-Corp/festival: Festival is a goal-oriented project management methodology for human and AI development workflows, driven by the fest and camp CLIs, installed and kept in sync by a third tool, festival. The skills imported below describe how to plan and execute festivals. Load them…
unity-ai-workflow CLAUDE.md
Instructions for devdavv/unity-ai-workflow, covering unity ai workflow, workspace layout, project config, dev modes and non-negotiable rules.