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 redhat-vmeperf/agent-tasks-template --skill sdlcgit 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)<a href="https://agentmods.dev/skills/redhat-vmeperf/agent-tasks-template/sdlc"><img src="https://agentmods.dev/badge/skills/redhat-vmeperf/agent-tasks-template/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/redhat-vmeperf/agent-tasks-template/sdlc"><img src="https://agentmods.dev/badge/skills/redhat-vmeperf/agent-tasks-template/sdlc.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.00049 | $0.00384 |
| Opus 5.5 | $0.00020 | $0.00154 |
| Sonnet 5.5 | $0.00010 | $0.00077 |
| Haiku 4.5 | $0.00005 | $0.00038 |
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 1mo 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 Skill
This skill runs the 7-gate SDLC pipeline for software engineering tasks. Read .agents/pipelines/SDLC.md for the full pipeline process definition, gate definitions, escalation protocol, and all process rules.
Arguments:
/sdlc <task description>— Start the full pipeline from Gate 1/sdlc resume:<N> <task>— Resume the pipeline at Gate N (e.g., after revisions)/sdlc gate:<name>— Jump to a specific gate (architect, security-arch, team-lead, engineer, review, quality, audit)/sdlc emergency <incident>— Expedited Chaotic-domain path (see Emergency Protocol in pipeline)
SDLC Context
This skill produces code, tests, and inline documentation as its Gate 4 output.
- Gate 3 blocks: No code written until Gate 3 is approved
- Gate 4 output: Implementation (code, tests, inline docs) + Implementation Report
- Gate 4 instruction: Write tests alongside the code, not after
- Gate 7 final action: MERGE / DEPLOY (human-approved)
Security of data and access controls:
- Security steps cannot be skipped.
- No interaction with any service or system may reduce the security posture of data passing through the process (REQ-5).
- External context files must pass a security review before loading (REQ-6). See
.agents/SECURITY_REVIEW_CHECKLIST.md.
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.
- 1mo ago First seen · 32 lines · 49 tokens per session scan A 51c012b3c25b
sdlc is a skill published in the GitHub repository redhat-vmeperf/agent-tasks-template (3 stars, last pushed 5mo ago), licensed Unlicense. It adds 49 tokens to every session and 384 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
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.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…