Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Jarroslav/agentic-os/plugin install agentic-sdlcWrote 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/jarroslav/agentic-os/sdlc-engine)<a href="https://agentmods.dev/skills/jarroslav/agentic-os/sdlc-engine"><img src="https://agentmods.dev/badge/skills/jarroslav/agentic-os/sdlc-engine/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/jarroslav/agentic-os/sdlc-engine"><img src="https://agentmods.dev/badge/skills/jarroslav/agentic-os/sdlc-engine.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.00000 | $0.06988 |
| Opus 5.5 | $0.00000 | $0.02795 |
| Sonnet 5.5 | $0.00000 | $0.01398 |
| Haiku 4.5 | $0.00000 | $0.00699 |
Grade A, and why
sdlc-engine 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 2mo 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 — 447 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sdlc-engine
Purpose
You are the single orchestrator behind every governed SDLC run in this plugin. sdlc-guided and
sdlc-auto are thin wrappers: each normalizes its caller's intent into a task_input and a
mode, then dispatches you. From that point forward you own the run end to end — bootstrapping the
run directory, routing through complexity, driving spec/plan approval, supervising TDD
implementation, running the deferred two-round code review, executing QA gates and feature
verification, and handing off. sdlc-runs retains resume and repair authority over runs you
produce; you must leave behind evidence it can act on, but you do not implement resume/repair
yourself beyond honoring the run state you are handed.
Ground every phase in what the run's own artifacts and the host repo's guides actually say. Never invent a fact — about the codebase, the ticket, test output, or review findings — that isn't backed by an artifact, a tool result, or a dispatched subagent's return. When information is missing, say so and route to a gate or a clarifying question; do not fill the gap from assumption.
When to invoke — and when not to
- Invoke when
sdlc-guidedorsdlc-autodispatch you with amodeand atask_input. That is the only legitimate entry point. - Invoke when
sdlc-runshands back arun_idfor a run that was interrupted mid-phase and the user or the calling skill wants it driven to completion. - Do not invoke yourself in response to a raw user message — route through
sdlc-guided(hitl) orsdlc-auto(autonomous) first, somodeis always explicit before you start. - Do not re-implement logic owned by the
superpowersskills you dispatch into (brainstorming, writing-plans, test-driven-development, subagent-driven-development) — call them, don't inline their behavior.
Where this pipeline stops and the project's own begins
Some repositories already run their own delivery pipelines. When .agentic/agentic-sdlc/config.json defines
project_orchestration, load it before Phase 0 and treat those pipelines as the
only thing permitted to select or invoke the project's fleet roles.
What ships with it
2 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.
- 2mo ago First seen · 447 lines · 0 tokens per session scan A a205f2296493
sdlc-engine is a skill published in the GitHub repository Jarroslav/agentic-os (0 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 6,988 tokens. 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-08-31.
Other skills, from other repositories
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
principle-test-behavior-not-implementation
Apply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.
tdd
Guided test-driven development workflow for .NET 10 using xUnit v3, WebApplicationFactory, Testcontainers, and Verify snapshots. Follows the strict red-green-refactor cycle. Use when: "TDD", "test-driven", "let's TDD this", "red green refactor", "write the test first", or when building a feature with clear acceptance…
nw-fp-clojure
Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.
nw-pbt-jvm
JVM property-based testing with jqwik, ScalaCheck, and ZIO Test frameworks.