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-statusnpx skills add joshidikshant/devsquad --skill devsquad-statusgit 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.00016 | $0.00599 |
| Opus 5 | $0.00008 | $0.00300 |
| Sonnet 5 | $0.00003 | $0.00120 |
| Haiku 4.5 | $0.00002 | $0.00060 |
Grade A, and why
devsquad-status 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevSquad Status Skill
Displays current squad health metrics including token usage, budget zone, delegation compliance, and agent availability.
When to Use
Invoke when the user wants to check:
- Current token budget and zone status (green/yellow/red)
- Live usage percentages from Claude, Gemini, and Codex CLIs
- Delegation compliance statistics
- Squad availability (which agents are installed)
- Capacity-aware delegation recommendations
Capacity-Aware Delegation
Status reads from a local capacity cache (.devsquad/capacity.json) populated by /devsquad:capacity.
Users report their current CLI usage percentages by checking:
- Claude:
/status→ "Current session" percentage - Gemini:
/stats→ "Usage left" (subtract from 100) - Codex:
/status→ "5h limit" and "Weekly limit" (subtract from 100)
The cache expires after 30 minutes, after which status shows a "STALE" warning and recommends re-running /devsquad:capacity.
Zone Thresholds
- 🟢 Green: < 50% usage — normal operation
- 🟡 Yellow: 50-75/80% — enforce delegation
- 🔴 Red: > 75/80% — critical, delegate everything
Usage
bash "${CLAUDE_PLUGIN_ROOT}/skills/devsquad-status/scripts/show-status.sh"
For machine-readable output:
bash "${CLAUDE_PLUGIN_ROOT}/skills/devsquad-status/scripts/show-status.sh" --json
Output Format
Human-Readable (default)
=== DevSquad Status ===
Token Budget:
Zone: GREEN (42% used)
Input tokens: 84,000
Output tokens: 12,000
Total: 96,000 / 200,000
Squad Usage (this session):
Gemini: 5 invocations, ~12,400 chars response
Codex: 2 invocations, ~3,200 chars response
Self: 8 calls
Delegation Compliance:
Suggestions made: 3
Overrides (advisory): 1
Compliance rate: 67%
Squad Availability:
Gemini CLI: available
Codex CLI: available
JSON Format (with --json)
Returns the raw JSON output from get_usage_summary function.
Dependencies
- lib/state.sh - State management
- lib/usage.sh - Usage tracking and zone calculation
- .devsquad/logs/delegation.log - Delegation suggestions log
- .devsquad/logs/compliance.log - Compliance override log
What ships with it
1 file 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 · 83 lines · 16 tokens per session scan A 13ec1a3dfc5d
devsquad-status is a skill published in the GitHub repository joshidikshant/devsquad (7 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 599 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…