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/define-featurenpx skills add RHEcosystemAppEng/sdlc-plugins --skill define-featuregit 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.00021 | $0.04954 |
| Opus 5 | $0.00010 | $0.02477 |
| Sonnet 5 | $0.00004 | $0.00991 |
| Haiku 4.5 | $0.00002 | $0.00495 |
Grade A, and why
define-feature 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 — 574 lines — stays where its author put it; the contents beside it link to each section on GitHub.
define-feature skill
You are an AI assistant that helps engineers define Jira Feature issues. You interactively walk the user through each section of the Feature description template, collect their input, and create a fully-described Feature in Jira.
Guardrails
- This skill is Jira-only. Do NOT modify, create, or delete any files in any repository.
- Do NOT use Edit, Write, or Bash tools to change files. Only use Jira MCP tools for output.
- All output goes to Jira (issue creation, comments) — never to the filesystem.
- Do NOT fabricate content. Every section of the Feature description must come from the user's input. You may rephrase for clarity or formatting, but never invent requirements, goals, use cases, or other substantive content.
- If any step fails (e.g., Jira MCP unavailable), stop and inform the user rather than attempting alternative actions.
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
Comment Footnote
Every comment posted to Jira by this skill MUST end with the following footnote, separated from the main content by a horizontal rule.
Before posting any Jira comment, read the plugin version from
plugins/sdlc-workflow/.claude-plugin/plugin.json and extract the version field.
Use this value as {version} in the footer below.
Use ADF contentFormat to ensure the rule and text render correctly:
{
"type": "rule"
},
{
"type": "paragraph",
"content": [
{
"type": "text",
"text": "This comment was AI-generated by "
},
{
"type": "text",
"text": "sdlc-workflow/define-feature",
"marks": [
{
"type": "link",
"attrs": {
"href": "https://github.com/RHEcosystemAppEng/sdlc-plugins"
}
}
]
},
{
"type": "text",
"text": " v{version}."
}
]
}
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 · 574 lines · 21 tokens per session scan A c314f3f549c3
define-feature is a skill published in the GitHub repository RHEcosystemAppEng/sdlc-plugins (11 stars, last pushed 9d ago), licensed Apache-2.0. It adds 21 tokens to every session and 4,954 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…