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 timwukp/agent-skills-best-practice --skill ai-native-sdlcgit clone --depth 1 https://github.com/timwukp/agent-skills-best-practiceWrote 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/timwukp/agent-skills-best-practice/ai-native-sdlc)<a href="https://agentmods.dev/skills/timwukp/agent-skills-best-practice/ai-native-sdlc"><img src="https://agentmods.dev/badge/skills/timwukp/agent-skills-best-practice/ai-native-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/timwukp/agent-skills-best-practice/ai-native-sdlc"><img src="https://agentmods.dev/badge/skills/timwukp/agent-skills-best-practice/ai-native-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.00172 | $0.03149 |
| Opus 5 | $0.00086 | $0.01574 |
| Sonnet 5 | $0.00034 | $0.00630 |
| Haiku 4.5 | $0.00017 | $0.00315 |
Grade A, and why
ai-native-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 2d 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 — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI-Native SDLC
Take a change from idea to production as a loop around the agent, not a linear human relay. Each stage ends by committing one machine-readable artifact, and the next stage begins by reading it. The chain of commits becomes the audit trail: who asked for what, what the agent produced, and who approved it.
Plan -> intent.md
Design -> spec.md
Build -> plan.md -> diff + tests
Test -> a verification target + evals/
Deploy -> PR + REVIEW.md findings -> gated release
Maintain -> bands.yaml breach -> writes a new intent.md (loop closes)
Instructions
- Identify the stage. Read
.sdlc/activefor the current slug; artifacts live inintent/<slug>/. If there is no active slug, the work starts at Stage 1. - Read the input artifact before producing the output artifact. Never write
spec.mdwithout reading an acceptedintent.md, and never edit source beforeplan.mdis accepted. - Run the gate rather than judging by eye:
python3 scripts/sdlc_gate.py intent/<slug> <design|build|test|deploy> # exit 0 = gate open, exit 2 = gate closed (reason on stderr) - Write the verification target BEFORE the implementation, run it, and confirm it FAILS. A test that has only ever been seen green is not evidence.
- Implement, then re-run it until green. If the implementation departs from
plan.md, updateplan.mdin the same commit. - Commit the artifact at the end of each stage. The commit is what advances the loop.
- Never approve your own work. Acceptance of
intent.md/ sign-off ofspec.mdis a human decision; do not flip a Status field on an artifact you authored.
Stage detail
Stage 1 — Plan → intent/<slug>/intent.md
Interview the originator until the idea is concrete: problem, desired outcome, affected
users and systems, constraints, success criteria, open questions. Copy
templates/intent.md. Gate: the product owner sets Status: accepted.
What ships with it
38 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.
- COMPATIBILITY.md 15 KB
- evals/evals.json 4.3 KB
- evals/trigger_evals.json 2.1 KB
- references/enforcement.md 9.7 KB
- references/enterprise-adoption.md 15 KB
- references/enterprise-roadmap.md 10 KB
- references/limitations.md 11 KB
- references/playbook-mapping.md 2.1 KB
- references/threat-model.md 11 KB
- scripts/build_review_prompt.py 6.2 KB runs code
- scripts/make_sbom.py 5.1 KB runs code
- scripts/mutation_proof.py 26 KB runs code
- scripts/sdlc_ci_gate.py 27 KB runs code
- scripts/sdlc_gate.py 4.8 KB runs code
- scripts/sdlc_pretooluse_hook.py 9.2 KB runs code
- scripts/sync_mutation_count.py 6.1 KB runs code
- scripts/test_ci_gate.py 10 KB runs code
- scripts/test_enterprise_readiness.py 13 KB runs code
- scripts/test_fork_safety.py 7.6 KB runs code
- scripts/test_gate.py 6.4 KB runs code
- scripts/test_hardening.py 10 KB runs code
- scripts/test_hook_config.py 8.8 KB runs code
- scripts/test_polyglot.py 6.8 KB runs code
- scripts/test_pretooluse_hook.py 12 KB runs code
- scripts/test_required_checks.py 8.8 KB runs code
- scripts/test_scale.py 9.8 KB runs code
- scripts/test_supply_chain.py 16 KB runs code
- scripts/test_support_matrix.py 9.4 KB runs code
- scripts/test_sync_mutation_count.py 7.6 KB runs code
- scripts/test_unbound_approval.py 21 KB runs code
- scripts/verify_gate_integrity.sh 4.4 KB runs code
- templates/bands.yaml 843 B
- templates/github-workflows/sdlc-gate.yml 11 KB
- templates/intent.md 768 B
- templates/kiro-hooks/sdlc-gate.json 1.1 KB
- templates/plan.md 1.6 KB
- templates/REVIEW.md 785 B
- templates/spec.md 776 B
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.
- 2d ago Changed · +31 lines abe69e88434e
- 5d ago Changed · +11 lines abd7077bb034
- 7d ago First seen · 184 lines · 172 tokens per session scan A 682444d2140a
ai-native-sdlc is a skill published in the GitHub repository timwukp/agent-skills-best-practice (10 stars, last pushed 2d ago), licensed MIT. It adds 172 tokens to every session and 3,149 once invoked, about $0.0009 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
ec2
AWS EC2 virtual machine management — instances, security groups, key pairs, AMIs, EBS volumes, Auto Scaling Groups, Spot Instances, Session Manager, placement groups, and instance lifecycle automation. Trigger on ANY of these, even when EC2 isn't named explicitly: - Launching or provisioning: "spin up a server"…
bedrock
AWS Bedrock foundation models for generative AI. Use when invoking foundation models, building AI applications, creating embeddings, configuring model access, or implementing RAG patterns.
cloudformation
AWS CloudFormation infrastructure as code for stack management. Use when writing templates, deploying stacks, managing drift, troubleshooting deployments, or organizing infrastructure with nested stacks.
cloudwatch
AWS CloudWatch monitoring for logs, metrics, alarms, and dashboards. Use when setting up monitoring, creating alarms, querying logs with Insights, configuring metric filters, building dashboards, or troubleshooting application issues.
dynamodb
AWS DynamoDB NoSQL database for scalable data storage. Use when designing table schemas, writing queries, configuring indexes, managing capacity, implementing single-table design, or troubleshooting performance issues.
ecs
AWS ECS container orchestration for running Docker containers. Use when deploying containerized applications, configuring task definitions, setting up services, managing clusters, or troubleshooting container issues.