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 skills/michael-harris/devteam/devteam-confignpx skills add michael-harris/devteam --skill devteam-configgit 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.00012 | $0.01514 |
| Opus 5 | $0.00006 | $0.00757 |
| Sonnet 5 | $0.00002 | $0.00303 |
| Haiku 4.5 | $0.00001 | $0.00151 |
Grade A, and why
devteam-config 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 — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevTeam Config Command
Command: /devteam:config [action] [key] [value]
View and modify DevTeam configuration settings.
Usage
/devteam:config # Show current configuration
/devteam:config show # Same as above
/devteam:config get eco.enabled # Get specific setting
/devteam:config set eco.enabled true # Set specific setting
/devteam:config reset # Reset to defaults
/devteam:config init # Initialize configuration
Actions
| Action | Description |
|---|---|
show |
Display all configuration (default) |
get <key> |
Get a specific setting |
set <key> <value> |
Set a specific setting |
reset |
Reset all settings to defaults |
init |
Initialize configuration for new project |
Configuration Options
Execution Settings
| Key | Type | Default | Description |
|---|---|---|---|
execution.mode |
string | normal |
Default mode: normal, eco |
execution.max_iterations |
int | 10 |
Max Task Loop iterations |
execution.parallel_gates |
bool | true |
Run quality gates in parallel |
Model Settings
| Key | Type | Default | Description |
|---|---|---|---|
models.escalation_threshold |
int | 2 |
Failures before escalation |
models.eco_threshold |
int | 4 |
Escalation threshold in eco mode |
Quality Gates
| Key | Type | Default | Description |
|---|---|---|---|
gates.tests.enabled |
bool | true |
Run tests |
gates.tests.command |
string | auto |
Test command (auto-detect) |
gates.lint.enabled |
bool | true |
Run linting |
gates.typecheck.enabled |
bool | true |
Run type checking |
gates.security.enabled |
bool | false |
Run security scan |
Interview Settings
| Key | Type | Default | Description |
|---|---|---|---|
interview.enabled |
bool | true |
Enable interview phase |
interview.max_questions |
int | 5 |
Max questions per interview |
interview.skip_for_plans |
bool | true |
Skip for planned tasks |
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 · 262 lines · 12 tokens per session scan A 3162e5340d7c
devteam-config is a skill published in the GitHub repository michael-harris/devteam (18 stars, last pushed 6mo ago), licensed MIT. It adds 12 tokens to every session and 1,514 once invoked, about $0.0001 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-30.
Other skills, from other repositories
hydra
Multi-agent orchestration framework for Claude Code. Automatically delegates tasks to cheaper, faster sub-agents (Haiku, Sonnet) while maintaining Opus-level quality through verification. Use when working on any coding task — Hydra activates automatically to route file exploration, test running, documentation, code…
quality-stack
Scan a project to detect configured quality and testing tools across JVM (Gradle/Maven), Android (AGP/Compose/KMP), Node.js/TypeScript, and Python ecosystems. Cross-reference against research-backed recommendations and assist with setup. Auto-detects project type(s) including monorepos with mixed ecosystems. Use when…
prototype
Rapid UI prototyping — generates 3 visually distinct HTML/CSS components from a text prompt and serves them in a live browser gallery. Use when user runs /prototype, asks to "prototype a UI", "mock up a component", "generate HTML mockups", "create UI variations", "design exploration", "quick UI concept", or wants to…
lyra
Transform vague inputs into precision-optimized AI prompts for Claude, ChatGPT, Gemini, or other LLMs. Use when user mentions "optimize prompt", "improve prompt", "lyra", "prompt engineering", or needs help crafting effective AI prompts.
taskfile-setup
Install Taskfile (task) and scaffold or audit Taskfile.yml configurations with ecosystem-aware templates. Auto-detects Node.js/pnpm, JVM/Gradle, Python/uv, Docker, and recommends single-file or multi-file (includes) patterns based on project complexity. Use when user runs /devtools:taskfile-setup, mentions "taskfile…
sops-add-key
Add a new machine's age public key to .sops.yaml and re-encrypt all files. Use for multi-machine setups. Use when user mentions "add key", "add machine", "sops add key", "new machine", "authorize machine", "share key", "add public key", "multi machine sops".