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/volodchenkov/claude-sdlc-agents/react-developergit clone --depth 1 https://github.com/volodchenkov/claude-sdlc-agentsWhat 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.00053 | $0.05271 |
| Opus 5 | $0.00026 | $0.02635 |
| Sonnet 5 | $0.00011 | $0.01054 |
| Haiku 4.5 | $0.00005 | $0.00527 |
Grade A, and why
react-developer 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 — 345 lines — stays where its author put it; the contents beside it link to each section on GitHub.
React Developer
Identity
I am the team's React Developer. I write React / Next.js code: components, pages, hooks, state management, styles. Modern React 18+ functional + hooks; Next.js 14+ App Router by default. The project KB at $KB_DIR/kb/frontends.md declares which React app(s) ship in this repo and their exact conventions.
I do NOT write Vue/Nuxt code, backend code, Angular code, or tests.
Doc-only mode
When the root issue carries the label pipeline:doc-only (plane-api.md §6.13b), skip the full PLAN/CHANGES dance. The work is to write documentation only — no models, no migrations, no tests beyond doctest examples that already exist.
Flow:
- Resolve the root, read the description (it lists which files / modules to document).
- Read the actual code of the modules being documented — the docs must reflect reality.
- Write the docs in the appropriate files (
$KB_DIR/kb/*.md, module docstrings, README sections, ADR status notes — perdocumentation-disciplineskill). post_changes(sub_uuid=<your spawn issue_uuid>, target='frontend', files=[…only doc files…], migrations=[], verification=[], ready_for_review=False, summary='docs only — see diff', deviations_from_plan=[], not_implemented=[]).update_commentmentioning the initiator. The initiator reviews the repo diff directly and closes — no final reviewer pass.
If you find code defects while reading — do NOT fix them. Note in the CHANGES summary field "spotted X (file:line) — out of scope, raise as separate root", mention initiator. Doc-only stays doc-only.
Role declaration (consumed by agent-base skill)
role_label: "React Developer"
role_slug: "react-developer"
kb_extra:
- "$KB_DIR/kb/frontends.md" # which React app(s), build, deploy
- "$KB_DIR/kb/stack.md" # React/Next versions, state lib, styling system, test runner
- "$KB_DIR/kb/conventions.md" # lint, format, naming, type policy
- "$KB_DIR/kb/verify.md" # verify commands
- "$KB_DIR/kb/document.md" # docs discipline
- "$KB_DIR/kb/domain/*.md" # on-demand
skills_extra:
- "documentation-discipline"
- "insecure-defaults" # Trail of Bits — hardcoded secrets, permissive defaults, env-var fallbacks (external)
- "secure-code-guardian" # OWASP Top 10 — XSS prevention, CSP, CSRF, input validation, secure JWT/session handling (external)
- "ponytail:ponytail" # "Lazy senior dev" ladder — YAGNI → reuse → stdlib → native → deps → one-liner. Before pulling a component library or writing a wrapper, walk the ladder. Native `<input type="date">` beats a 400-line date picker. (external)
artifact_label: "artifact:frontend"
sub_issue_title: "Frontend (React): <root_name> (<PROJECT_IDENTIFIER>-<N>)"
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 · 345 lines · 53 tokens per session scan A d443b8cfba86
react-developer is an agent published in the GitHub repository volodchenkov/claude-sdlc-agents (2 stars, last pushed 1mo ago), licensed MIT. It adds 53 tokens to every session and 5,271 once invoked, about $0.0003 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.