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/joshidikshant/devsquad/devsquad-confignpx skills add joshidikshant/devsquad --skill devsquad-configgit clone --depth 1 https://github.com/joshidikshant/devsquadWhat 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.00010 | $0.00584 |
| Opus 5 | $0.00005 | $0.00292 |
| Sonnet 5 | $0.00002 | $0.00117 |
| Haiku 4.5 | $0.00001 | $0.00058 |
Grade A, and why
devsquad-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 2d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevSquad Config Skill
Displays and updates DevSquad configuration without re-running onboarding.
When to Use
Invoke when the user wants to:
- View current configuration settings
- Update delegation preferences
- Change enforcement mode
- Adjust word/line limits for agents
- Modify default routing for task types
Usage
View Current Config
bash "${CLAUDE_PLUGIN_ROOT}/skills/devsquad-config/scripts/show-config.sh"
Update a Setting
bash "${CLAUDE_PLUGIN_ROOT}/skills/devsquad-config/scripts/update-config.sh" "key=value"
Editable Keys
| Key | Type | Valid Values | Description |
|---|---|---|---|
enforcement_mode |
string | advisory, strict | Delegation enforcement mode |
gemini_word_limit |
number | 0-1000 | Word limit for Gemini responses (0=disabled) |
codex_line_limit |
number | 0-200 | Line limit for Codex responses (0=disabled) |
auto_suggest |
boolean | true, false | Auto-suggest delegation when applicable |
default_routes.research |
string | gemini, codex, self | Default agent for research tasks |
default_routes.reading |
string | gemini, self | Default agent for reading tasks |
default_routes.code_generation |
string | gemini, codex | Default agent for code generation |
default_routes.testing |
string | gemini, codex | Default agent for testing tasks |
default_routes.synthesis |
string | self | Default agent for synthesis tasks |
Output Format
show-config.sh
=== DevSquad Configuration ===
Enforcement Mode: advisory
Default Routes:
research: gemini
reading: gemini
code_generation: codex
testing: codex
synthesis: claude
Preferences:
gemini_word_limit: 300
codex_line_limit: 50
auto_suggest: true
Edit: /devsquad:config enforcement_mode=strict
update-config.sh
Updated enforcement_mode to strict
Dependencies
- lib/state.sh - State management and atomic writes
- .devsquad/config.json - Configuration storage
- jq (required for updates) - JSON manipulation
What ships with it
2 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.
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.
- 2d ago First seen · 85 lines · 10 tokens per session scan A 0c0cc3e27a75
devsquad-config is a skill published in the GitHub repository joshidikshant/devsquad (7 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 584 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…