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 commands/michael-harris/devteam/devteam-designgit clone --depth 1 https://github.com/michael-harris/devteamWhat 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.00000 | $0.00563 |
| Opus 5 | $0.00000 | $0.00282 |
| Sonnet 5 | $0.00000 | $0.00113 |
| Haiku 4.5 | $0.00000 | $0.00056 |
Grade A, and why
devteam-design 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 yesterday.
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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevTeam Design Command
Command: /devteam:design [target] [options]
Coordinate UX/UI design work across platforms. Launches the UX System Coordinator to orchestrate design specialists.
Usage
# Design for current task/sprint
/devteam:design
# Design specific component
/devteam:design "User settings page"
# Platform-specific design
/devteam:design "Navigation" --platform web
/devteam:design "Navigation" --platform mobile
/devteam:design "Navigation" --platform desktop
# Design system work
/devteam:design --system
/devteam:design --system "Color palette refresh"
# Cost-optimized
/devteam:design "Login form" --eco
Options
| Option | Description |
|---|---|
--platform <platform> |
Target platform: web, mobile, desktop, all |
--system |
Focus on design system architecture |
--eco |
Cost-optimized execution |
--skip-interview |
Skip clarifying questions |
Your Process
Phase 0: Initialize Session
source scripts/state.sh
source scripts/events.sh
SESSION_ID=$(start_session "/devteam:design $*" "design")
log_session_started "/devteam:design $*" "design"
Phase 1: Launch UX System Coordinator
Delegate to the ux:ux-system-coordinator agent, which will:
- Analyze design requirements
- Select appropriate UX specialists based on platform
- Coordinate design system architecture if needed
- Ensure consistency across components
- Validate against design system tokens and patterns
const result = await Task({
subagent_type: "ux:ux-system-coordinator",
prompt: `Design coordination request: ${target}
Platform: ${platform || 'auto-detect'}
Design system mode: ${systemMode}
Coordinate the appropriate UX specialists to produce:
1. Component specifications
2. Layout and interaction patterns
3. Design tokens (colors, typography, spacing)
4. Accessibility requirements
5. Responsive behavior specifications`
})
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.
- yesterday First seen · 95 lines · 0 tokens per session scan A 5b5afe09f669
devteam-design is a command published in the GitHub repository michael-harris/devteam (18 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 563 tokens. 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 commands, from other repositories
p1-journeys
Develops detailed personas, user journeys, and usage scenarios based on the Discovery results. These artefacts form the user foundation for all further conception decisions.
feature
Post a feature to the Features Board on production and write tweets.
commit-all
Group all changes semantically and commit each group separately.
validate
Run lint and build to validate changes.
responsive-design-specialist
Use when a layout breaks between sizes. Arbitrary breakpoints, type that does not scale, images that blow out the grid, or a desktop design retrofitted onto mobile.
compose-test
Run Compose UI tests with Espresso. Verify critical user flows.