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 skills add jmagly/aiwg --skill sdlc-accelerategit clone --depth 1 https://github.com/jmagly/aiwgWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/jmagly/aiwg/sdlc-accelerate)<a href="https://agentmods.dev/skills/jmagly/aiwg/sdlc-accelerate"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/sdlc-accelerate/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/jmagly/aiwg/sdlc-accelerate"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/sdlc-accelerate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 608 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
What 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.1 | $0.00023 | $0.05127 |
| Opus 5 | $0.00012 | $0.02563 |
| Sonnet 5 | $0.00005 | $0.01025 |
| Haiku 4.5 | $0.00002 | $0.00513 |
Grade A, and why
sdlc-accelerate 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 4d 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 — 609 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDLC Accelerate
You are the SDLC Accelerate Orchestrator - executing the full pipeline from raw idea (or existing codebase) to a Construction-Ready Brief in a single automated run. You drive Intake, Lifecycle Objective Milestone (LOM) evaluation, Elaboration, Architecture Baseline Milestone (ABM) evaluation, and Construction Prep without requiring the user to manually trigger each phase transition.
Core Philosophy
Weeks of SDLC ceremony compressed into hours of focused orchestration. The goal is not to skip rigor — it is to eliminate the coordination overhead between phases so that teams reach construction with a full artifact set, not just a README.
Natural Language Triggers
Users may say:
- "sdlc accelerate"
- "accelerate sdlc"
- "bootstrap project"
- "ramp up sdlc"
- "construction ready"
- "fast track sdlc"
- "take this idea to construction"
- "get us to construction ready"
- "bootstrap the sdlc for [project description]"
- "we need to be construction ready by [date]"
Parameters
description (required unless --from-codebase or --resume)
Natural language description of the project, product, or feature to accelerate through SDLC. Can be a sentence or several paragraphs. More detail yields higher-quality intake artifacts.
aiwg sdlc-accelerate "A CLI tool that monitors Bittensor subnet validator metrics and sends alerts via Slack when scores drop below configurable thresholds."
--from-codebase <path>
Skip the intake description and derive the project profile by analyzing an existing codebase. The orchestrator reads source files, infers the domain, and generates intake artifacts from the code rather than a text description.
aiwg sdlc-accelerate --from-codebase ./my-existing-project
When this flag is set:
- Phase 1 (Intake) reads the codebase instead of the user description
- Requirements are extracted from code structure, README, and existing tests
- Architecture analysis starts from current implementation rather than blank slate
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.
- 4d ago First seen · 609 lines · 23 tokens per session scan A 8dac29f0e995
sdlc-accelerate is a skill published in the GitHub repository jmagly/aiwg (210 stars, last pushed yesterday), licensed MIT. It adds 23 tokens to every session and 5,127 once invoked, about $0.0001 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-09-05.
Other skills, from other repositories
state
Use when the user says 'update state', 'project state', 'where was I', or at session start to load current context.
gstack-sprint
3-Phase Sprint workflow — design → execute → review with user interaction at decision points.
dos-dispatch
Plan and ship the next batch on one lane: run dos-next-up, acquire a lease with dos arbitrate, gate empty work, dispatch the packet, and archive the run. Use when a single lane should move end to end with collision safety.
dos-class-cycle
Run one DOS plan-class lifecycle tick from the workspace [lifecycle] table: evaluate declared transitions, have a judge approve/defer them, write gated plan-meta edits, and log the cycle. Use when gardening plan lifecycle classes automatically.
pace-bridge
Use to bridge a confirmed Superpowers/native plan into PACEflow CHG/HOTFIX artifacts, create artifact-writer prompts, and mark the specific plan as synced.
task-copilot
Use when work should be tracked with tc, including creating PRDs, tasks, handoffs, logs, and work products, or when preserving detailed outputs outside the chat context.