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 review-lifecyclegit 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/review-lifecycle)<a href="https://agentmods.dev/skills/tomzx/agents/review-lifecycle"><img src="https://agentmods.dev/badge/skills/tomzx/agents/review-lifecycle/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/review-lifecycle"><img src="https://agentmods.dev/badge/skills/tomzx/agents/review-lifecycle.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.00026 | $0.01402 |
| Opus 5.5 | $0.00010 | $0.00561 |
| Sonnet 5.5 | $0.00005 | $0.00280 |
| Haiku 4.5 | $0.00003 | $0.00140 |
Grade A, and why
review-lifecycle 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 22d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Lifecycle
Audits a resource lifecycle document and reports findings across six categories: completeness, consistency, spec alignment, transition correctness, invariant soundness, and retention soundness.
Prerequisites
- Apply the shared SDLC conventions in
skills/sdlc/references/shared.md. - If no argument is provided, locate the feature directory under
.sdlc/features/whose frontmatterissuefield references$ISSUE_NUMBER. .sdlc/features/N-<slug>/lifecycle.md, or a lifecycle document provided in context or as a file path.sdlc/features/N-<slug>/specification.md(for cross-referencing data models, API contracts, and sequences).sdlc/features/N-<slug>/requirements.md(optional, for cross-referencing functional requirements that drive lifecycle behavior)
Steps
- Read the lifecycle document from
.sdlc/features/N-<slug>/lifecycle.mdif present, otherwise from context or as a file path. - Cross-reference against the specification and requirements if available.
- Identify issues in each of the six categories below.
- Report findings. Omit any category that has no findings.
- Write the findings to
.sdlc/features/N-<slug>/review-lifecycle.mdwith frontmatterartifact: lifecycle,verdict(approvedif there are no blocking findings,changes-requestedif the author must address findings,rejectedfor a fundamental flaw), andreviewed_at: <ISO date>, and the findings as the body, perskills/sdlc/references/shared.md. Record any unresolved open questions in the findings body. For any question that carries meaningful risk to the implementation, also invoke/create-assumptionto record it formally.
Review Checklist
Completeness
- Does every resource identified in the specification's data models have a corresponding lifecycle entry (or an explicit decision to exclude it)?
- Does every state machine have a state diagram showing all states and transitions?
- Does every state have an entry condition, exit condition, and description?
- Does every transition have a trigger, actor, side effects, and guard conditions?
- Are all invariants documented, or is there an explicit statement that no invariants apply?
- Are retention and expiry policies documented for resources that are not permanent?
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.
- 22d ago Changed · -1 lines aa4234b276a2
- 23d ago Changed · -4 lines 3b98abab53ab
- 24d ago Changed de1ff6e7b2d1
- 1mo ago First seen · 132 lines · 26 tokens per session scan A 0eb3d2cfd477
review-lifecycle is a skill published in the GitHub repository tomzx/agents (13 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 1,402 once invoked, about $0.0001 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
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
agui-dotnet-protobuf
Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
fastapi-router-py
Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.
dev-runtime
How the Node side of a dev stack runs without haven, and the backend host: pnpm dev (UI built once, backend reloading), pnpm dev:hmr (adds the Vite ui lane), tools/dev-runtime (api + worker in one Node process), backend reload on a file change, the debounce (quiet window + max wait), ports derived from PORT. Use when…
api-design
Use when settling the contract of an API you expose, before implementation: resources/URLs, REST vs GraphQL, versioning, one RFC 9457 error envelope, pagination, idempotency — emitted as OpenAPI 3.1. NOT implementing the endpoints (that is fastapi/nestjs/go/nodejs), NOT auth hardening (that is secure-coding), NOT…