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 sdlcgit 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/sdlc)<a href="https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/sdlc"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/sdlc/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/sdlc"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/sdlc.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.00022 | $0.01966 |
| Opus 5.5 | $0.00009 | $0.00786 |
| Sonnet 5.5 | $0.00004 | $0.00393 |
| Haiku 4.5 | $0.00002 | $0.00197 |
Grade A, and why
sdlc 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 11d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sdlc Skill
[!IMPORTANT] Route a task to the next synced SDLC workflow based on current artifacts and repo state.
Optional args: slug=, ticket=<id/url>, mode=interactive|autonomous|channel, channel=, auto_continue=true|false, profile=business|hybrid|technical.
Instructions
When the user asks to perform this workflow, execute the following steps:
SDLC Router Workflow
Goal: Select the next native workflow without loading every workflow body, while preserving a traceable BA -> PM -> IT Department handoff for offshore delivery.
Steps
- Inspect state:
- User request; infer
operator_profile(business | hybrid | technical) percommon-operator-profileand carry it in every Handoff Payload. - Search for the requested task's linked brief/ticket using its stable slug; do not select an unrelated newest document or infer task authority/approval from
git status. If no matching approved task record exists, identify the missing authority/input and route to the appropriate intake. Slug = lowercase kebab-case, minted once atbrainstorm-feature, reused verbatim downstream; never re-derived. - If multiple candidates exist, list them and ask whether to focus, consolidate, or sequence.
- Baseline reference:
common-software-requirements/references/requirements-standards-baseline.md(ships with the skill) - Existing ticket, BRD-lite brief, PRD, SRS/FRS design, implementation plan, task list, walkthrough, UAT signoff, deployment report, release notes, and retro
- Jira, ADO, Zephyr, or other MCP context when already configured
- Changed files and current test status
- Offshore delivery context: business owner, product owner, implementation owners, QA owner, timezone/cadence constraints, environments, release window, and dependency teams
- Requirement trace health:
BRD-OBJ-* -> REQ-* -> AC-* -> SRS-* -> test evidence - SNC tier per
common-task-complexity-routingor the scoutSNC:line; label as inference until scouted.
- User request; infer
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.
- 11d ago Changed · +5 lines 6f4e28999cd5
- 12d ago Changed · -17 lines 1027381dd82d
- 18d ago Changed f1f0748a8781
- 19d ago Changed · -2 lines 5cbb468d15be
- 27d ago Changed · +1 lines 9ef05d3c29fb
- 1mo ago Changed · -1 lines 5b9bafb0335b
- 1mo ago Changed 9eee1f0072ca
- 1mo ago Changed · +2 lines 9e271ae230e9
- 1mo ago Changed · +1 lines 59d92a3fc2c5
- 1mo ago First seen · 113 lines · 22 tokens per session scan A 9ebb258e0544
sdlc is a skill published in the GitHub repository HoangNguyen0403/agent-skills-standard (583 stars, last pushed today), licensed MIT. It adds 22 tokens to every session and 1,966 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
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.