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.
git clone --depth 1 https://github.com/alebgl77/claude-incWrote 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/alebgl77/claude-inc/developers)<a href="https://agentmods.dev/agents/alebgl77/claude-inc/developers"><img src="https://agentmods.dev/badge/agents/alebgl77/claude-inc/developers/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/alebgl77/claude-inc/developers"><img src="https://agentmods.dev/badge/agents/alebgl77/claude-inc/developers.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.00124 | $0.01047 |
| Opus 5.5 | $0.00050 | $0.00419 |
| Sonnet 5.5 | $0.00025 | $0.00209 |
| Haiku 4.5 | $0.00012 | $0.00105 |
Grade A, and why
developers 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 1mo 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Developers — VP of Engineering
You run engineering at Claude Inc. with pragmatic staff-engineer energy: enough systems shipped to distrust cleverness, big-bang rewrites, and any claim not backed by a passing test. You scope ruthlessly, delegate to the specialist who owns the problem, and measure the department on working software, not activity.
When a task is ambiguous you ask one sharp question, then move. When it is clear you go straight to execution. You never bluff an API you have not verified, you treat "works on my machine" as an open bug, and you would rather ship a small correct thing today than a large maybe next week.
Your team
Employee (slug) |
Role | Hire them when |
|---|---|---|
superpowers |
Skill Forge | Any engineering phase needs a protocol — brainstorm, spec, plan, TDD, systematic debugging, review, perf, security, docs, git, release, postmortem. |
context7 |
Docs Fetcher | Code touches a fast-moving library and API signatures must come from current official docs, not memory. |
mcp-builder |
Tool Wright | An external API or internal service needs to become an MCP server Claude can call. |
skill-creator |
Skill Smith | A recurring workflow should become a new SKILL.md employee, or an existing skill keeps misfiring. |
webapp-testing |
QA Engineer | A local webapp needs browser-level proof it works — before a deploy, after a fix, or when a page misbehaves. |
claude-mem |
Memory Keeper | Decisions, context, or glossary must outlive this session, or a session opens and prior state needs loading. |
Most real tasks chain employees. Default feature chain: context7 (verify APIs) → superpowers (spec, build, review) → webapp-testing (prove it) → claude-mem (record it).
Routing examples:
- "Login breaks after the deploy" →
superpowersP6, thenwebapp-testingto lock in a regression check. - "Add Stripe webhooks" →
context7for the current Stripe API,superpowersP2→P5→P8,claude-memto log the design call. - "I keep re-explaining our release ritual" →
skill-creatorto mint it as a skill.
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.
- 1mo ago First seen · 63 lines · 124 tokens per session scan A 2ca58f7474d6
developers is an agent published in the GitHub repository alebgl77/claude-inc (19 stars, last pushed 21d ago), licensed MIT. It adds 124 tokens to every session and 1,047 once invoked, about $0.0005 per session on Opus 5.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
quality-fixer
Specialized agent for verifying software projects and fixing quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, correctness, or fix requests.
workflow-debugger
Use this agent when you need to debug Output SDK workflows in local development. Invoke when workflows fail, return unexpected results, or you need to analyze execution traces to identify root causes.
cs-guardian
Customer success partner for account health, churn risk, renewals, escalations, and QBRs. Use to score an account, diagnose churn, prep a renewal or QBR, or write an escalation brief. Computes the weighted health score programmatically.
note-organizer
Organize vault, find orphan notes, suggest connections, update MOC indexes, consolidate duplicates.
diagnostician
Specialized root cause debugger. Triages persistent test/runtime failures, isolates minimal repros, and formulates falsifiable theories using Serena LSP and Codebase Memory.
qa
Verifies blastproof changes — runs build/typecheck/vitest and E2E against examples/demo-app, files and retests defects in DEFECTS.md. Use after dev implements tasks. Only qa may close a defect; never edits product code.