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 skills add CarbeneAI/Forge --skill devteamgit clone --depth 1 https://github.com/CarbeneAI/ForgeWrote 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/skills/carbeneai/forge/devteam)<a href="https://agentmods.dev/skills/carbeneai/forge/devteam"><img src="https://agentmods.dev/badge/skills/carbeneai/forge/devteam/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/skills/carbeneai/forge/devteam"><img src="https://agentmods.dev/badge/skills/carbeneai/forge/devteam.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.00078 | $0.01586 |
| Opus 5.5 | $0.00031 | $0.00634 |
| Sonnet 5.5 | $0.00016 | $0.00317 |
| Haiku 4.5 | $0.00008 | $0.00159 |
Grade A, and why
DevTeam 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevTeam
Security-first autonomous multi-agent software development team with hierarchical coordination through a Project Manager (Joshua), parallel developer agents (Hiram instances), QA engineer (Ezra), security auditor (Nehemiah), and code reviewer (Solomon).
Security Policy: CarbeneAI is a "Security Built In, Not Bolted On" organization. All code produced by DevTeam undergoes mandatory security review by Nehemiah before merge. OWASP Top 10 compliance is required for all web-facing code.
Key Projects:
- carbeneai (carbene.ai) - Parent brand site: open-source tools + training
- cyberdefensetactics (cyberdefensetactics.com) - Security training academy (the product)
- purpleteamops (purpleteamops.app) - Hands-on lab + recurring membership
Workflow Routing
${PAI_DIR}/tools/skill-workflow-notification WorkflowName DevTeam
| Workflow | Trigger | File |
|---|---|---|
| InitProject | "set up dev team", "initialize devteam", "start dev team for [feature]" | workflows/InitProject.md |
| RunTeam | "run the dev team", "start devteam", "execute TODO.md" | workflows/RunTeam.md |
| TeamStatus | "how's the team", "devteam status", "check agent progress" | workflows/TeamStatus.md |
| CollectResults | "collect results", "merge team work", "devteam done" | workflows/CollectResults.md |
Architecture
User (Orchestrator)
└── Joshua (PM) — manages tasks, dispatches agents, monitors progress
├── Hiram-1 (Dev) — implements tasks in git worktrees
├── Hiram-2 (Dev) — implements tasks in parallel
├── Ezra (QA) — writes tests, validates acceptance criteria
├── Nehemiah (Security) — OWASP audit, auth review, vulnerability scan
└── Solomon (Review) — code quality review
Coordination model: Hierarchical through Joshua. No peer-to-peer messaging.
Communication: File-based inbox/outbox in .devteam/agents/ directory.
Task tracking: TODO.md as single source of truth.
Parallelism: Tmux sessions via CodingAgent tools. Git worktrees for isolation.
Security gate: Nehemiah reviews ALL code before merge (mandatory, never skipped).
What ships with it
12 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- reference/EzraPrompt.md 3.9 KB
- reference/JoshuaPrompt.md 6.3 KB
- reference/MessageProtocol.md 4.5 KB
- reference/TaskFormat.md 4.6 KB
- tools/DevTeamInit.ts 9.4 KB runs code
- tools/MessageBus.ts 12 KB runs code
- tools/TaskBoard.ts 17 KB runs code
- tools/TeamStatus.ts 13 KB runs code
- workflows/CollectResults.md 4.4 KB
- workflows/InitProject.md 3.4 KB
- workflows/RunTeam.md 4.2 KB
- workflows/TeamStatus.md 1.4 KB
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 · 158 lines · 78 tokens per session scan A 7ff7a4c340e6
DevTeam is a skill published in the GitHub repository CarbeneAI/Forge (9 stars, last pushed 2mo ago), licensed MIT. It adds 78 tokens to every session and 1,586 once invoked, about $0.0003 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-31.
Other skills, from other repositories
usap-program-manager
Security program manager and passive lifecycle orchestrator (cs-security-program-manager). Use for security roadmap planning, program health scanning, debt tracking, facilitated reviews, or when the user says "security roadmap", "program planning", "security debt", "proactive scan", or "program review".
findings-tracker
../../../governance/findings-tracker/SKILL.md.
incident-commander
../../../response/incident-commander/SKILL.md.
contact-template
Contact / communications plan generator — primary operator, escalation chain, abort signal recipient, external SOC endpoint, blackout windows.
implementing-semgrep-for-custom-sast-rules
Write custom Semgrep SAST rules in YAML to detect application-specific vulnerabilities, enforce coding standards, and integrate into CI/CD pipelines.
project-context-setup
Scaffolds per-repository agent context so coding agents share the same issue tracker rules, triage label vocabulary, domain glossary, ADR layout, and handoff conventions. Triggers on: "set up project context", "configure agent docs", "create CONTEXT.md", "setup agent workflow", "agent issue tracker setup", "triage…