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/code-generationnpx skills add joshidikshant/devsquad --skill code-generationgit 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.00044 | $0.00359 |
| Opus 5 | $0.00022 | $0.00179 |
| Sonnet 5 | $0.00009 | $0.00072 |
| Haiku 4.5 | $0.00004 | $0.00036 |
Grade A, and why
code-generation 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.
What it actually says
Code Generation Skill
Transforms a natural language description into a working DevSquad skill by researching existing patterns with Gemini and drafting implementation with Codex.
When to Use
Use this skill when the user:
- Describes an automation they want as a slash command (e.g., "bulk rename files matching pattern")
- Asks to "generate a skill" or "create a new DevSquad command"
- Wants to add a new capability to DevSquad without writing it manually
Usage
bash "${CLAUDE_PLUGIN_ROOT}/skills/code-generation/scripts/generate-skill.sh" "<description>"
# or with explicit name
bash "${CLAUDE_PLUGIN_ROOT}/skills/code-generation/scripts/generate-skill.sh" "<description>" --name my-skill-name
What It Does
- Derives a skill name from the description (or uses --name)
- Uses Gemini to research existing DevSquad patterns (skill structure, argument conventions, library usage)
- Uses Codex to draft SKILL.md, the implementation script, and the command stub
- Displays the full draft for user review
- On confirmation, writes files atomically and runs bash -n validation
Dependencies
- lib/gemini-wrapper.sh — Codebase pattern research via invoke_gemini_with_files
- lib/codex-wrapper.sh — Implementation drafting via invoke_codex
- lib/state.sh — Atomic file writes via write_state
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.
- yesterday First seen · 39 lines · 44 tokens per session scan A 006e2e79a00b
code-generation is a skill published in the GitHub repository joshidikshant/devsquad (7 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 359 once invoked, about $0.0002 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…