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/endorphin-ai/claude-code-teams/react-architect-meangit clone --depth 1 https://github.com/endorphin-ai/claude-code-teamsWrote 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/endorphin-ai/claude-code-teams/react-architect-mean)<a href="https://agentmods.dev/agents/endorphin-ai/claude-code-teams/react-architect-mean"><img src="https://agentmods.dev/badge/agents/endorphin-ai/claude-code-teams/react-architect-mean.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.00122 | $0.01824 |
| Opus 5 | $0.00061 | $0.00912 |
| Sonnet 5 | $0.00024 | $0.00365 |
| Haiku 4.5 | $0.00012 | $0.00182 |
Grade A, and why
react-architect-mean 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 3d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 3d ago First seen · 178 lines · 122 tokens per session scan A 9b1a728a8305
react-architect-mean is an agent published in the GitHub repository endorphin-ai/claude-code-teams (3 stars, last pushed 6mo ago), with no licence file. It adds 122 tokens to every session and 1,824 once invoked, about $0.0006 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
full-stack-developer
Full-stack developer with TDD expertise, specializing in end-to-end application development with modern TypeScript, React, and Node.js stack. Expert in testing automation and continuous integration practices.
react-specialist
React and Next.js development expert specializing in modern React patterns, performance optimization, and scalable component architecture. Deep expertise in hooks, context, state management, and the React ecosystem.
frontend-dev
Frontend development specialist focusing on UI/UX, React, TypeScript, and modern web technologies. Use for building user interfaces, components, state management, and frontend architecture.
react-frontend
React Frontend Execution Agent.
ci-watcher
Polls Nx Cloud CI pipeline and self-healing status. Returns structured state when actionable. Spawned by /nx-cloud-ci-monitor command to monitor CI Attempt status.
security-reviewer
Use proactively when attacker-controlled input, trust boundaries, authorization decisions, sensitive sinks, secrets, or security-impacting changes require exploitability analysis. Do not use for generic correctness review without a meaningful security boundary.