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/issuesnpx skills add agentic-development/adev-plugin --skill issuesgit 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.00082 | $0.04499 |
| Opus 5 | $0.00041 | $0.02250 |
| Sonnet 5 | $0.00016 | $0.00900 |
| Haiku 4.5 | $0.00008 | $0.00450 |
Grade A, and why
adev:issues 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 — 317 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Management
Manage project issues and epics using the configured task backend.
Announce at start: "I'm using the adev:issues skill to manage project issues."
Arguments
- No arguments: display the full issue board
create "<title>" [--type bug|feature|task] [--epic <epic-id>] [--priority 0-4] [--spec-ref <path>] [--next-action <text>]: create an issueepic "<title>" [--milestone <name>]: create a new epic in the epic store, optionally assigning it to a milestoneupdate <id> --status <open|in_progress|closed|deferred> [--milestone <name>]: update issue status and/or milestone (for epics).--statusand--milestonecan be used together or independently — both fields are updated in a single callclose <id> --reason "<text>": close an issue with a reasonlist [--status <status>] [--epic <epic-id>] [--milestone <name>]: filtered issue list.--milestonefilters to epics and issues belonging to epics with that milestonedep <issue-id> <depends-on-id>: add a blocking dependencyready: show actionable issues (open + unblocked)
Prerequisites
Check that .context-index/ exists with manifest.yaml. If not:
Run
/adev:initfirst to set up the context index.
Process
Backend Resolution
The active backend is whatever tasks.backend names in .context-index/manifest.yaml. The default is json (.context-index/tasks/tasks.json); file (legacy markdown, read-only) and beads are also supported.
Nothing has to be resolved here. Every adev issues sub-verb reads the manifest, selects the matching adapter, and resolves the storage root from the git common dir on its own — so one invocation is correct from the main checkout and from a linked worktree alike. The board storage is created on the first write, so there is no separate initialisation step to run.
Load Skill Extensions: Load any skill extension instructions before proceeding:
adev skill-ext load --skill issues
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 · 317 lines · 82 tokens per session scan A 72c3846da4d0
adev:issues is a skill published in the GitHub repository agentic-development/adev-plugin (11 stars, last pushed 3d ago), licensed MIT. It adds 82 tokens to every session and 4,499 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…