Borrowing it
Nothing to install: this file belongs to pangon/ai-sdlc-framework. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/pangon/ai-sdlc-framework/main/.claude/skills/SDLC-status/SKILL.mdgit clone --depth 1 https://github.com/pangon/ai-sdlc-frameworkWrote 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/pangon/ai-sdlc-framework/sdlc-status)<a href="https://agentmods.dev/skills/pangon/ai-sdlc-framework/sdlc-status"><img src="https://agentmods.dev/badge/skills/pangon/ai-sdlc-framework/sdlc-status.svg" alt="Measured on agentmods" height="20"></a>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.00050 | $0.01899 |
| Opus 5 | $0.00025 | $0.00949 |
| Sonnet 5 | $0.00010 | $0.00380 |
| Haiku 4.5 | $0.00005 | $0.00190 |
Grade A, and why
SDLC-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 7d 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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Instructions
You are generating a comprehensive status report for the entire SDLC project.
Setup
- Read root instructions:
CLAUDE.md— extract Project Overview and Current State. - Read all four phase instruction files:
1-spec/CLAUDE.spec.md2-design/CLAUDE.design.md3-code/CLAUDE.code.md4-deploy/CLAUDE.deploy.md
- Read
1-spec/stakeholders.md. - Read
3-code/tasks.md(if it exists and has content), and the verification indexes that exist —3-code/verification.mdand3-code/<component>/verification.md. - Scan all artifact indexes in the phase files — follow File column links only when needed to resolve ambiguous statuses.
- List files in
decisions/to count decisions (excludePROCEDURES.md, templates, and.history.mdfiles; read.history.mdonly when the corresponding active record shows Deprecated or Superseded status). - List component directories in
3-code/(directories containing aCLAUDE.mdfile). - List files in
4-deploy/infrastructure/,4-deploy/scripts/,4-deploy/runbooks/to count deployment artifacts (exclude templates and placeholderREADME.mdfiles).
Phase Validation
Before generating the report, read the **Phase**: field of the ### Current State subsection in CLAUDE.md:
- If it is
Not initialized(or the Project Overview still contains placeholder text) → report the project as Not Initialized and recommend/SDLC-init. - Otherwise → proceed with full report.
Report Structure
Present the report as a single markdown document with these sections.
Project Overview
- Project: name/description (from
CLAUDE.mdProject Overview) - Date: current date
- Current State: reproduce the Current State section from
CLAUDE.mdverbatim — this is the authoritative project-level summary maintained by all skills
Phase 1: Specification
Stakeholders: N defined (list names and influence levels in a compact line)
Artifacts:
| Artifact | Total | Draft | Approved | Implemented | Deprecated |
|---|---|---|---|---|---|
| Goals | |||||
| User Stories | |||||
| Requirements |
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.
- 7d ago First seen · 182 lines · 50 tokens per session scan A 0331f680e80d
SDLC-status is a skill published in the GitHub repository pangon/ai-sdlc-framework (126 stars, last pushed 14d ago), licensed Apache-2.0. It adds 50 tokens to every session and 1,899 once invoked, about $0.0003 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.