Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/RHEcosystemAppEng/sdlc-pluginsnpx agentmods add skills/rhecosystemappeng/sdlc-plugins/define-featureWrote 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/rhecosystemappeng/sdlc-plugins/define-feature)<a href="https://agentmods.dev/skills/rhecosystemappeng/sdlc-plugins/define-feature"><img src="https://agentmods.dev/badge/skills/rhecosystemappeng/sdlc-plugins/define-feature/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/rhecosystemappeng/sdlc-plugins/define-feature"><img src="https://agentmods.dev/badge/skills/rhecosystemappeng/sdlc-plugins/define-feature.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00021 | $0.04954 |
| Opus 5.5 | $0.00008 | $0.01982 |
| Sonnet 5.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 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.
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.
- 1mo 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 (13 stars, last pushed today), licensed Apache-2.0. It adds 21 tokens to every session and 4,954 once invoked, about $0.0001 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-30.
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,"…