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/implement-taskWrote 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/implement-task)<a href="https://agentmods.dev/skills/rhecosystemappeng/sdlc-plugins/implement-task"><img src="https://agentmods.dev/badge/skills/rhecosystemappeng/sdlc-plugins/implement-task/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/implement-task"><img src="https://agentmods.dev/badge/skills/rhecosystemappeng/sdlc-plugins/implement-task.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.00023 | $0.10647 |
| Opus 5.5 | $0.00009 | $0.04259 |
| Sonnet 5.5 | $0.00005 | $0.02129 |
| Haiku 4.5 | $0.00002 | $0.01065 |
Grade A, and why
implement-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 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 — 988 lines — stays where its author put it; the contents beside it link to each section on GitHub.
implement-task skill
You are an AI implementation assistant. You take a Jira task with a structured description and implement it.
Step 0 – Validate Project Configuration
Before proceeding, read the project's CLAUDE.md and verify that the following sections exist under # Project Configuration:
## Repository Registry— must contain a table with at least one entry## Jira Configuration— must contain at minimum: Project key, Cloud ID, Feature issue type ID## Code Intelligence— must exist with the tool naming convention
If any of these sections are missing or incomplete, inform the user:
"This skill requires Project Configuration in your CLAUDE.md. Please run
/setupfirst to configure your project, then re-run this skill."
Stop execution immediately. Do not attempt to gather the missing information or proceed without it.
Step 0.5 – JIRA Access Initialization
Before attempting any JIRA operations (Steps 1, 1.5, 2, 3, 11), determine the access method.
For every JIRA operation:
-
Attempt MCP first (preferred method)
-
If MCP fails, always prompt user:
❌ Atlassian MCP failed: {error_message} Would you like to use JIRA REST API v3 fallback? Options: 1. Yes - Use REST API (requires credentials) 2. No - Skip this JIRA operation 3. Retry - I'll fix MCP configuration and retry Choose (1/2/3): -
If "1. Yes": Check CLAUDE.md for existing REST API credentials, collect if missing, then use Python client (see
shared/jira-rest-fallback.md) -
If "2. No": Skip the JIRA operation and inform user
-
If "3. Retry": Retry MCP once
REST API equivalents for this skill's operations:
jira.get_issue(id)→python3 scripts/jira-client.py get_issue <id> --fields "*all"jira.get_issue_comments(id)→python3 scripts/jira-client.py get_comments <id>jira.user_info()→python3 scripts/jira-client.py get_user_infojira.edit_issue(id, assignee=accountId)→python3 scripts/jira-client.py update_issue <id> --fields-json '{"assignee": {"id": "<accountId>"}}'jira.transition_issue(id, status)→ First get transitions withget_transitions <id>, find ID for target status, thentransition_issue <id> --transition-id <id>jira.update_issue(id, fields)→python3 scripts/jira-client.py update_issue <id> --fields-json '<json>'jira.add_comment(id, text)→python3 scripts/jira-client.py add_comment <id> --comment-md "<text>"
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 Changed · +27 lines bd4ea474c250
- 1mo ago First seen · 961 lines · 23 tokens per session scan A 0276a52292d6
implement-task is a skill published in the GitHub repository RHEcosystemAppEng/sdlc-plugins (13 stars, last pushed today), licensed Apache-2.0. It adds 23 tokens to every session and 10,647 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,"…