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/rhecosystemappeng/sdlc-plugins/setupnpx skills add RHEcosystemAppEng/sdlc-plugins --skill setupgit clone --depth 1 https://github.com/RHEcosystemAppEng/sdlc-pluginsWhat 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 | $0.00025 | $0.07132 |
| Opus 5 | $0.00013 | $0.03566 |
| Sonnet 5 | $0.00005 | $0.01426 |
| Haiku 4.5 | $0.00003 | $0.00713 |
Grade A, and why
setup 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 — 623 lines — stays where its author put it; the contents beside it link to each section on GitHub.
setup skill
You are an AI setup assistant. You configure a project's CLAUDE.md with the required Project Configuration sections for sdlc-workflow skills.
Behavior
This skill is idempotent and incremental:
- Running it multiple times on an already-configured project produces no changes.
- If new MCP servers (Serena instances, Atlassian) have been added since the last run, only the new entries are added.
- Existing configuration entries are never removed or overwritten.
Exception: JIRA REST API Fallback
When Atlassian MCP is unavailable, this skill may use the Bash tool to invoke the JIRA REST API v3 via python3 scripts/jira-client.py. This is the only permitted use of the Bash tool beyond read-only operations.
- ✅ Allowed:
bash -c "python3 scripts/jira-client.py <command>" - ❌ Forbidden: any other Bash file modification commands
Template
Read the file project-config.template.md in this skill's directory. Use it as the structural reference for generating the # Project Configuration section. Replace the {{placeholder}} markers with actual values gathered during the steps below. Preserve the exact headings, table format, and section order from the template.
Step 1 – Read Existing Configuration
Read the project's CLAUDE.md file. If it exists, parse it for:
# Project Configurationheading## Repository Registrytable — record each Repository name already listed## Jira Configurationlist — record which fields already have values### Jira Field Defaultssubsection under Jira Configuration — record whether it exists and which fields are populated## Code Intelligencesection — record which Serena instances are already documented## Bug Configurationsection — record whether it exists and which fields are populated## Security Configurationsection — record whether it exists and which fields are populated## Hierarchy Configurationsection — record whether it exists and which fields are populated
If the file doesn't exist, note that everything needs to be created.
What ships with it
4 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.
- 2d ago First seen · 623 lines · 25 tokens per session scan A a9d4a55fc351
setup is a skill published in the GitHub repository RHEcosystemAppEng/sdlc-plugins (11 stars, last pushed 8d ago), licensed Apache-2.0. It adds 25 tokens to every session and 7,132 once invoked, about $0.0001 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…