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 HoangNguyen0403/agent-skills-standard --skill common-sdlc-metricsgit clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standardWrote 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/hoangnguyen0403/agent-skills-standard/common-sdlc-metrics)<a href="https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/common-sdlc-metrics"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/common-sdlc-metrics/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/hoangnguyen0403/agent-skills-standard/common-sdlc-metrics"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/common-sdlc-metrics.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.00059 | $0.00975 |
| Opus 5.5 | $0.00024 | $0.00390 |
| Sonnet 5.5 | $0.00012 | $0.00195 |
| Haiku 4.5 | $0.00006 | $0.00097 |
Grade A, and why
common-sdlc-metrics 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDLC Metrics Standard
Priority: P2 (MEDIUM)
Measure the handoffs, not the keystrokes. Every metric here is derived from committed artifacts and git history, so it survives a change of runtime and cannot be inflated by activity.
1. Contract, Not Collector
- This skill defines what to report and how. It does not gather provider or CI telemetry itself.
- The host runtime or orchestrator supplies the raw counts; unavailable inputs are reported as unavailable, never estimated.
- Emit
artifacts/sdlc-metrics.mdat a workflow terminal state, alongsideartifacts/session-cost.md. - Load
references/metrics-schema.mdfor the report skeleton.
2. Aggregate Health (DORA)
- Deployment frequency: successful deploys per period, from deployment reports.
- Lead time for changes: first commit to production, per change.
- Change failure rate: deploys needing hotfix or rollback, divided by deploys.
- Time to restore: mitigation timestamp minus incident detection, from the incident record.
3. Per-Stage Indicators
| Stage | Leading | Lagging |
|---|---|---|
| BRD | first conversation to committed BRD | BRD survival rate into PRD |
| PRD / SRS | BRD to PRD to SRS commit deltas | requirement rework after first docs/srs/srs-task-list-[slug].md |
| Build | share merging on first implementation pass | plan adherence, merged diff versus docs/srs/srs-task-list-[slug].md |
| Test | first-pass CI success, eval pass rate | defect escape rate |
| Review | time to first finding | findings per review by severity |
| Release | change lead time | change failure rate |
| Maintain | band breach to intake in queue | repeat incidents by class |
4. Control Bands
- Define bands in
docs/ops/bands.yaml, version controlled and reviewed like code. Schema:references/bands-template.yaml. - Baseline is a rolling window, not a fixed target. Detection is deterministic and computed before any agent reads the signal.
- Tiers escalate by evidence: log, then read-only diagnose, then propose a change. Never let a tier act beyond its declared tools and routes.
- Dismissals tune the band. A band that fires constantly is miscalibrated, not urgent.
What ships with it
3 files 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 · 99 lines · 59 tokens per session scan A e8e0ac9e325d
common-sdlc-metrics is a skill published in the GitHub repository HoangNguyen0403/agent-skills-standard (582 stars, last pushed today), licensed MIT. It adds 59 tokens to every session and 975 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-25.
Other skills, from other repositories
intelligence-docs
Keeps the CopilotKit Intelligence landing page in sync when a new Intelligence feature ships or when Intelligence docs are added, renamed, or removed. Use when adding Intelligence capabilities, writing or moving pages under docs/intelligence, editing IntelligenceFeatureCards, or changing…
nextjs-idioms
Next.js App Router architecture: React Server Components (RSC), Server Actions, nested layouts, route handlers, and streaming. Use when building or refactoring Next.js web applications. Pair with react-idioms and typescript-idioms.
react-idioms
React 19+ patterns: custom hooks, Suspense boundaries, state management, component composition, and web performance. Use when developing or refactoring React components and client applications. Pair with typescript-idioms.
plan
PM planning workflow that gathers requirements, decomposes them into prioritized tasks, defines API contracts, and produces both a machine-readable plan and a human-readable tracker in docs/plans/.
coordinate-pro
Thorough version of coordinate - high-quality development workflow with 11 review steps out of 17.
coordinate
Coordinate multiple agents for a complex multi-domain project using PM planning, parallel agent spawning, and QA review.