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/ai-driven-dev/framework/02-runnpx skills add ai-driven-dev/framework --skill 02-rungit clone --depth 1 https://github.com/ai-driven-dev/frameworkWhat 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.00117 | $0.00644 |
| Opus 5 | $0.00059 | $0.00322 |
| Sonnet 5 | $0.00023 | $0.00129 |
| Haiku 4.5 | $0.00012 | $0.00064 |
Grade A, and why
aidd-async-dev:02:run 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.
How it starts
The opening of the file, as written. The whole thing — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run
Executes one orchestration cycle. Reads ready issues, resolves blockers, acquires a per-issue lock, hands the implementation to the active SDLC orchestration capability discovered in the runtime, and records audit + observability artifacts.
Available actions
| # | Action | Role | Input |
|---|---|---|---|
| 01 | poll-ready |
List ready issues by label, project column, or mention | repo + config |
| 02 | resolve-deps |
Filter out blocked issues via dependency chain | candidate issues |
| 03 | acquire-lock |
Add ai:running label to dedupe parallel runs |
target issue |
| 04 | check-sdlc |
Discover an active SDLC orchestration capability | runtime context |
| 05 | delegate-sdlc |
Invoke the discovered SDLC capability with issue context | locked issue |
| 06 | write-audit |
Persist run record to aidd_docs/async-runs/ and Check Run |
run result |
| 07 | emit-webhook |
POST run record to SIEM webhook if configured | run record |
Default flow
Sequential: 01 -> 02 -> 03 -> 04 -> 05 -> 06 -> 07. Action 03 runs once per selected issue. If no issue passes 02, the skill stops cleanly without locking.
Transversal rules
- Read
.claude/aidd-async-dev.jsonfirst; abort with a clear message if absent (refer the user to the setup skill of this plugin). - Acquire the lock before delegating. Release the lock by removing
ai:runningonly after06-write-auditsucceeds, regardless of pipeline outcome. - On any failure between 03 and 06, attach the error to the audit record and the issue as a comment; keep
ai:runningso a human can investigate. - Never auto-merge. The pipeline ends at PR creation.
- Apply
tool_allowlistfrom config via the pluginPreToolUsehook when hooks are wired.
What ships with it
8 files 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.
- actions/skills/01-poll-ready.md 1.3 KB
- actions/skills/02-resolve-deps.md 1.3 KB
- actions/skills/03-acquire-lock.md 1.0 KB
- actions/skills/04-check-sdlc.md 1.4 KB
- actions/skills/05-delegate-sdlc.md 1.5 KB
- actions/skills/06-write-audit.md 1.3 KB
- actions/skills/07-emit-webhook.md 1.2 KB
- evals/scenarios.json 488 B
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 · 38 lines · 0 tokens per session scan A ebd6bfaa5c75
aidd-async-dev:02:run is a skill published in the GitHub repository ai-driven-dev/framework (445 stars, last pushed 2d ago), licensed MIT. It adds 117 tokens to every session and 644 once invoked, about $0.0006 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
smoke-test
End-to-end smoke test skill for DeerFlow. Guides through: 1) Pulling latest code, 2) Docker OR Local installation and deployment (user preference, default to Local if Docker network issues), 3) Service availability verification, 4) Health check, 5) Final test report. Use when the user says "run smoke test", "smoke…
image-generation
Use this skill when the user requests to generate, create, imagine, or visualize images including characters, scenes, products, or any visual content. Supports structured prompts and reference images for guided generation.
podcast-generation
Use this skill when the user requests to generate, create, or produce podcasts from text content. Converts written content into a two-host conversational podcast audio format with natural dialogue.
vercel-deploy
Deploy applications and websites to Vercel. Use this skill when the user requests deployment actions such as "Deploy my app", "Deploy this to production", "Create a preview deployment", "Deploy and give me the link", or "Push this live". No authentication required - returns preview URL and claimable deployment link.
zeroclaw
Help users operate and interact with their ZeroClaw agent instance — through both the CLI (zeroclaw commands) and the REST/WebSocket gateway API. Use this skill whenever the user wants to: send messages to ZeroClaw, manage memory or cron jobs, check system status, configure channels or providers, hit the gateway API…
github-issue-triage
Issue triage and lifecycle management agent for ZeroClaw. Use this skill whenever the user wants to: triage open issues, close stale/duplicate/fixed issues, apply labels, run a backlog sweep, enforce the current issue stale policy, or handle a specific issue. Trigger on: 'triage issues', 'issue triage', 'sweep…