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/statusnpx skills add agentic-development/adev-plugin --skill statusgit 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.00081 | $0.07005 |
| Opus 5 | $0.00041 | $0.03503 |
| Sonnet 5 | $0.00016 | $0.01401 |
| Haiku 4.5 | $0.00008 | $0.00700 |
Grade A, and why
adev: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 — 532 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Status Dashboard
Query and display the current status of adev lifecycle artifacts. This skill is read-only — it never modifies files.
Announcement: "I'm using the adev:status skill to query project status."
Persona adaptation: All output formats below are defaults for the Developer persona; adapt the chat output to the active persona's output rules. Verbosity is resolved separately across templates/verbosity/terse.md, templates/verbosity/normal.md, and templates/verbosity/deep.md: when the resolved verbosity is terse and a section below carries a **Terse form:** block, that block is the section's declared rendering at terse verbosity.
Terse-form convention. The marker
**Terse form:**(used verbatim, never rephrased) is the last block of a governed section: its content runs from the marker line to the end of that section. A section's extent is its heading line through the line before the next heading of equal or shallower depth (depth = leading#count), or end of file; heading detection is fence-aware and frontmatter-aware, so a#-prefixed line inside a fenced code block or the leading YAML frontmatter is not a heading. Exactly one marker per governed section.Table substitution inside a terse form (BEH-3). A terse form contains at most one table of the section's own data. Every further table is replaced by a count plus a pointer: the repo-relative path of the artifact already holding the data, or — when no artifact holds it — the narrower invocation of the same skill that renders detail for one item. When neither exists, state the count alone with nothing named.
Arguments
--spec <path>: Show detailed status for a single spec--charter <name>: Show status for a charter and its specs/capabilities--milestone <name>: Show detailed status for a single milestone (mutually exclusive with--specand--charter)--issue <id>: Trace full lifecycle chain for a single issue (issue → plan task → spec → commits → files → drift)--epic <id>: Show epic status with all child issues, code coverage, and completeness--file <path>: Reverse lookup — file → spec (via source manifest) → issue → commits → drift--backlog: Aggregate all pending work from charters, specs, issue board, and code provenance--milestone <name>: Show all capabilities in a milestone across all charters with spec/plan/issue/code status--all: Show full project status dashboard (default when no args)
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 · 532 lines · 81 tokens per session scan A bd36fdbc0ab9
adev:status is a skill published in the GitHub repository agentic-development/adev-plugin (11 stars, last pushed 2d ago), licensed MIT. It adds 81 tokens to every session and 7,005 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…