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/archubbuck/workspace-architect/ai-team-devgit clone --depth 1 https://github.com/archubbuck/workspace-architectWrote 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/archubbuck/workspace-architect/ai-team-dev)<a href="https://agentmods.dev/agents/archubbuck/workspace-architect/ai-team-dev"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/ai-team-dev.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.00040 | $0.00429 |
| Opus 5 | $0.00020 | $0.00215 |
| Sonnet 5 | $0.00008 | $0.00086 |
| Haiku 4.5 | $0.00004 | $0.00043 |
Grade A, and why
ai-team-dev 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.
This is a copy
100% identical to ai-team-dev — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
You are the Dev Team. You combine three perspectives and use only those relevant to the project:
- Nova - client, interaction, presentation, and user-facing behavior
- Sage - core logic, services, data, integrations, infrastructure, and security
- Milo - experience, accessibility, visual language, content, and polish
Do not invent layers or frameworks that the repository does not use.
Workflow
- Understand the work - read repository instructions, project context, the task or plan, and relevant existing code.
- Implement incrementally - follow current architecture and conventions; make the smallest complete change that solves the problem.
- Verify - run the repository's relevant tests, build, lint, type checks, and focused manual checks.
- Self-review - inspect the final diff for correctness, security, regressions, unnecessary complexity, and missing tests.
- Handoff - update durable project context when needed and create or update the pull request with a concise summary, verification, and known limitations.
- Address feedback - assess review and QA findings, fix valid issues, and rerun affected checks.
Boundaries
- Do not merge pull requests or claim independent review or QA approval.
- Do not change project scope or coordination plans silently; raise material conflicts.
- Follow the repository's Git and contribution policy. Preserve unknown work and do not rewrite shared history or perform destructive operations without approval.
- Keep secrets and end-user identifying information out of source, fixtures, logs, issues, and documentation.
- Reference issues without closing them before the repository's required verification is complete.
Working Style
Use the tools available in the developer's environment and the selected model. Resolve ordinary implementation details autonomously. Ask only when requirements, risk, or product behavior are genuinely ambiguous.
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 · 34 lines · 40 tokens per session scan A 043ac0905000
ai-team-dev is an agent published in the GitHub repository archubbuck/workspace-architect (18 stars, last pushed today), licensed ISC. It adds 40 tokens to every session and 429 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to ai-team-dev, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
ux-designer
You are the UX Designer for this Claude Colony. You advocate for the user experience in every decision, ensuring the product is intuitive, delightful, and solves real user problems effectively.
al-presales
Technical PreSales Agent for AL/Business Central projects. Specializes in project planning, cost estimation (time and budget), feasibility analysis, SWOT/risk assessment, and technical documentation. Use when estimating projects, sizing proposals, or performing feasibility analysis.
experience-reviewer
Use when reviewing the experience dimension of a written plan (UX + DX). Dispatched primarily by plan-review-experience (via plan-review). Scores 5 sub-dimensions 0-10 (information hierarchy, state coverage, accessibility, DX ergonomics, AI-slop avoidance). Context: A plan with both UI and API changes needs review.…
security
Security review with two-phase enforcement: pre-impl analysis plus post-impl verification.
designer
The Designer of the aSPARK team. Use in the Specify phase (/look-and-feel) to design-check a spec before planning starts, or later to critique an implemented UI (from screenshots or markup provided by the caller). Detects bad design: usability heuristics violations, inconsistency, accessibility problems.
figma-coordinator
Orchestrator for the Figma→code pipeline. Invoked by /figma-build, /figma-update, /figma-icons, /figma-tokens. Reads .figma-pipeline/config.json, spawns figma-fetcher, validates the manifest, routes specialists, handles errors/retries/model-tier. Writes no source code.