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 Jarroslav/agentic-os --skill sdlc-autogit clone --depth 1 https://github.com/Jarroslav/agentic-osWrote 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-auto)<a href="https://agentmods.dev/skills/jarroslav/agentic-os/sdlc-auto"><img src="https://agentmods.dev/badge/skills/jarroslav/agentic-os/sdlc-auto.svg" alt="Measured on agentmods" 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.00143 | $0.01566 |
| Opus 5 | $0.00072 | $0.00783 |
| Sonnet 5 | $0.00029 | $0.00313 |
| Haiku 4.5 | $0.00014 | $0.00157 |
Grade A, and why
sdlc-auto 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 7d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sdlc-auto
Skill-based entry point for autonomous-mode SDLC runs, for hosts (for example Codex) that
expose skills but not custom slash commands. Everything this skill does is intent
normalization and delegation — it holds zero workflow, QA, review, or git logic itself. All
phase execution lives in sdlc-engine; all gate resolution lives in gate-arbiter.
Treat this skill as a thin adapter in front of the legacy sdlc:autonomous command, mirroring
whatever human-in-the-loop entry point exists alongside it in the same skill family.
When to invoke
- The user says "run autonomously", "factory mode", or "ship this without asking".
- The user asks for the legacy
sdlc:autonomouscommand on a host that has no slash-command support.
What this skill does not do
- Does not implement any SDLC phase, QA check, code review, or test logic.
- Does not create branches, commits, or open an MR/PR — autonomous mode never auto-merges and never opens an MR/PR by itself; the delegated pipeline halts after its branch-ready phase and hand-off to an MR/PR tool is a separate, manual step.
- Does not resolve judgment gates directly — every gate routes through
gate-arbiter. - Does not generate missing guide files, bypass the branch-guard, or auto-stash / hard-reset / force-push a dirty working tree absent explicit project policy allowing it.
When the project owns implementation
Read .agentic/agentic-sdlc/config.json before delegating. A configured project orchestrator stays the sole
coordinator of its fleet even here — unattended mode changes who answers the
gates, not who owns the work. Hand it one bounded implementation request, consume
only summaries and serialized gate results, and stop at every human gate the
project declares.
Running unattended never relaxes a restriction: commit, push, migration, release and production limits apply exactly as they do with someone watching.
Inputs
| Field | Type | Default | Notes |
|---|---|---|---|
raw_input |
string | — | Task text, work-item reference, story path, or greenfield idea |
mode_flag |
string/enum | none | Only --greenfield is recognized |
escalate_on |
string[] | ["security", "breaking-change"] |
CSV or list-style input |
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.
- 7d ago First seen · 119 lines · 0 tokens per session scan A 6d40990c51f6
sdlc-auto is a skill published in the GitHub repository Jarroslav/agentic-os (0 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 143 tokens to every session and 1,566 once invoked, about $0.0007 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-08-31.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.