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 pdlc-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/pdlc-status)<a href="https://agentmods.dev/skills/tomzx/agents/pdlc-status"><img src="https://agentmods.dev/badge/skills/tomzx/agents/pdlc-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/pdlc-status"><img src="https://agentmods.dev/badge/skills/tomzx/agents/pdlc-status.svg" alt="Reviewed on agentmods" width="80" 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.00026 | $0.00585 |
| Opus 5 | $0.00013 | $0.00293 |
| Sonnet 5 | $0.00005 | $0.00117 |
| Haiku 4.5 | $0.00003 | $0.00059 |
Grade A, and why
pdlc-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 6d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PDLC Status
Reads .pdlc/ and reports where each initiative sits across the six PDLC phases, plus the latest gate verdict for each. Read-only: produces no side effects.
Prerequisites
- Apply the shared PDLC conventions in
skills/pdlc/references/shared.md. - An initialized
.pdlc/directory (if absent, report that and suggest/pdlc setup).
Steps
- List
.pdlc/initiatives/*/directories. For each, readprogress.mdfrontmatter if present. - For each initiative, determine which artifacts exist under its directory and map them to phases:
- Discover:
problems.md,market.md,competitors.md,opportunity-tree.md - Validate:
assumptions.md,experiment-plan.md,experiment-result.md - Strategy: (writes to
context/vision.md,context/goals.md,context/roadmap.md) - Define:
prd.md,acceptance-contract.md,prototype.md - Launch:
launch-plan.md,messaging.md,enablement-kit.md,pricing.md - Measure:
analytics-spec.md,health-report.md,feedback-loop.md,eol-plan.md
- Discover:
- Find the most recent decision record in
.pdlc/decisions/matching each initiative (initiative: INIT-N) and report itsphaseandgate_verdict. - Read
.pdlc/state.ymlfor the currently active run, if any.
Output Format
## PDLC Status
Active run: <current_phase for INIT-N, or "none">
| Initiative | Title | Phase | Last Gate | Next Step |
|---|---|---|---|---|
| INIT-42 | Onboarding redesign | Define | proceed | handoff to SDLC |
| INIT-p1 | Usage-based pricing | Validate | pivot | re-run design-experiment |
| INIT-7 | Mobile app | Measure | iterate | back to Discover |
### INIT-42 — Onboarding redesign
Phase: Define (acceptance contract ready — SDLC handoff)
Gate history: discover:proceed → validate:proceed → strategy:proceed → define:proceed
Artifacts: problems.md ✓, opportunity-tree.md ✓, prd.md ✓, acceptance-contract.md ✓
If no initiatives exist, report that .pdlc/ is empty and suggest /pdlc discover to start.
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.
- 6d ago First seen · 52 lines · 26 tokens per session scan A 77954a1864fb
pdlc-status is a skill published in the GitHub repository tomzx/agents (6 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 585 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-03.
Other skills, from other repositories
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.
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.
remove
Remove a deployed framework or addon from the current workspace.