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 agentmods add skills/redhat-vmeperf/agent-tasks-template/sdlc-tasknpx skills add redhat-vmeperf/agent-tasks-template --skill sdlc-taskgit clone --depth 1 https://github.com/redhat-vmeperf/agent-tasks-templateWrote 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/redhat-vmeperf/agent-tasks-template/sdlc-task)<a href="https://agentmods.dev/skills/redhat-vmeperf/agent-tasks-template/sdlc-task"><img src="https://agentmods.dev/badge/skills/redhat-vmeperf/agent-tasks-template/sdlc-task.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.00043 | $0.00523 |
| Opus 5 | $0.00022 | $0.00262 |
| Sonnet 5 | $0.00009 | $0.00105 |
| Haiku 4.5 | $0.00004 | $0.00052 |
Grade A, and why
sdlc-task 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 6d 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.
What it actually says
sdlc-task Skill
Platform-agnostic definition for the autonomous (ungated) SDLC pipeline.
This skill runs the same 7 roles as the standard SDLC pipeline (Architect, Security Architect, Team Lead, Engineer, Code Reviewer, Quality Engineer, Security Auditor) but without human approval gates. All gates are advisory — agents produce their artifacts, surface findings, and self-advance.
When a later gate discovers something that changes architecture, scope, or security posture, the pipeline loops back to Gate 1 to re-evaluate with the new information, then continues forward. This makes the pipeline self-improving, not just advisory.
Behavior
- All 7 roles execute in sequence and produce their standard artifacts
- No gate blocks on human approval — agents self-advance
- Self-correction: discoveries that change architecture, scope, or security posture trigger a loop back to Gate 1 (max 2 re-evaluation cycles to prevent infinite loops)
- Finding mitigation is driven by the invoker's directions — findings within scope are mitigated, findings outside scope are flagged
- Audit trail is mandatory (REQ-2), entries marked as
UNGATED - All common files (CYNEFIN.md, PERSONALITY.md, LESSONS.md, REQUIREMENTS.md) are loaded
Pipeline
See .agents/skills/sdlc-task/PIPELINE.md for the full pipeline process definition.
Invocation Context
This skill may be invoked:
- Directly by a human for lower-ceremony tasks
- By any pipeline that needs autonomous SDLC-quality analysis without blocking
What ships with it
1 file 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.
- 6d ago First seen · 51 lines · 43 tokens per session scan A e789c481b243
sdlc-task is a skill published in the GitHub repository redhat-vmeperf/agent-tasks-template (3 stars, last pushed 4mo ago), licensed Unlicense. It adds 43 tokens to every session and 523 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…