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 tomzx/agents --skill sdlc-statusgit clone --depth 1 https://github.com/tomzx/agentsWrote 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/tomzx/agents/sdlc-status)<a href="https://agentmods.dev/skills/tomzx/agents/sdlc-status"><img src="https://agentmods.dev/badge/skills/tomzx/agents/sdlc-status/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/tomzx/agents/sdlc-status"><img src="https://agentmods.dev/badge/skills/tomzx/agents/sdlc-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00062 | $0.01593 |
| Opus 5.5 | $0.00025 | $0.00637 |
| Sonnet 5.5 | $0.00012 | $0.00319 |
| Haiku 4.5 | $0.00006 | $0.00159 |
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 1mo 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDLC Status Report
Produces a progress dashboard for all SDLC features in a repository. This is a read-only operation that does not modify any artifacts.
When to Use
- The user wants to see current progress on one or all features.
- The user wants to pick up where they left off and needs a summary.
- The user asks "where am I?" or "what's the status?" about the SDLC pipeline.
- The
/sdlcorchestrator enters at thestatusentry point.
Inputs
$1(optional): A specific feature directory name (e.g.,42-notification-system) or path to.sdlc/.- If not provided, defaults to
.sdlc/in the current repository.
Outputs
A formatted status report displayed to the user, containing:
- A summary table of all features (if multiple exist).
- Per-feature detail: pipeline progress, task status, blockers, session log.
- A prompt asking which feature to work on and at which phase to resume.
Steps
- Locate the
.sdlc/directory. Use$1if it specifies a path, otherwise use.sdlc/in the current repository root. Applysdlc/references/shared.mdfor path resolution (repo first, then$SDLC_DIR/{owner}/{repository}/.sdlc/);state.ymlandprogress.mdare never read from the mirror. - Read
.sdlc/state.ymlif it exists. Surfacecurrent_phase,github_ref, andfeaturein the report header so the user can see at a glance what the pipeline was last doing. - Scan
.sdlc/features/for all feature directories (excludingtemplates/). - If
$1specifies a feature ID (e.g.,FEAT-1), filter to that feature only. - For each feature, read
progress.mdif it exists. Otherwise scan the directory for artifacts and task files. - Read all task files in
.sdlc/features/N-<slug>/tasks/and collect their frontmatter. - Render the status report.
Preferred: Use the bundled script
scripts/sdlc-status.py renders a self-contained HTML dashboard (one tabbed panel per feature, with pipeline status, task progress, blockers, and session log) directly from the .sdlc/ directory. Prefer it over hand-building a report, especially when the user asks for HTML.
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.
- 1mo ago First seen · 134 lines · 62 tokens per session scan A d5ef0b623aa2
sdlc-status is a skill published in the GitHub repository tomzx/agents (13 stars, last pushed yesterday), licensed MIT. It adds 62 tokens to every session and 1,593 once invoked, about $0.0002 per session on Opus 5.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-03.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.