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/agentic-development/adev-plugin/deploynpx skills add agentic-development/adev-plugin --skill deploygit clone --depth 1 https://github.com/agentic-development/adev-pluginWhat 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.00077 | $0.01683 |
| Opus 5 | $0.00039 | $0.00842 |
| Sonnet 5 | $0.00015 | $0.00337 |
| Haiku 4.5 | $0.00008 | $0.00168 |
Grade A, and why
adev:deploy 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy Pipeline
Execute a structured deployment pipeline defined in .context-index/deploy.yaml. Steps run in order with fail-fast behavior, output redaction, and rollback guidance on failure.
Announce at start: "I'm using the adev:deploy skill to run a deployment pipeline."
Arguments
--version <tag>: explicit version/tag for this deploy (bypasses milestone lookup)--env <name>: target environment name (uses default if omitted)--dry-run: print what would execute without running anything
Prerequisites
Before starting, verify all conditions. If any fails, stop with the indicated message.
-
Deploy config exists.
.context-index/deploy.yamlmust exist. If missing: "No deploy.yaml found. Run/adev:deploy initto set up deployment." -
Config validates. Load and validate the config using the companion library. If validation fails: print each error with step ID and description, then exit.
-
Version resolved. Either
--version <tag>is provided, or a shipped milestone exists inmilestones.yaml. If neither: "No shipped milestone found. Use--version <tag>to deploy explicitly."
Process
Step 1: Load and Validate Config
import { loadDeployConfig, validateDeployConfig } from '<project-root>/lib/deploy.mjs';
const config = loadDeployConfig(projectRoot);
// If null: print NO_CONFIG message and exit
// If config._loadError: print errors and exit
const { errors, warnings } = validateDeployConfig(config);
// If errors.length > 0: print each error and exit
// If warnings.length > 0: print warnings (non-blocking)
Load Skill Extensions: Load any skill extension instructions before proceeding:
adev skill-ext load --skill deploy
If the output is not __NONE__, incorporate it as additional standing instructions that apply to this skill's entire execution. Frame it as: "The following skill extension instructions apply to this invocation (source: installed domain extensions and/or project-level overrides)." If the output is __NONE__, continue normally.
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 · 175 lines · 77 tokens per session scan A 3e8e0bb13ae0
adev:deploy is a skill published in the GitHub repository agentic-development/adev-plugin (11 stars, last pushed 2d ago), licensed MIT. It adds 77 tokens to every session and 1,683 once invoked, about $0.0004 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
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…