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 Gentleman-Programming/Gentleman-Skills --skill jira-taskgit clone --depth 1 https://github.com/Gentleman-Programming/Gentleman-SkillsWrote 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/gentleman-programming/gentleman-skills/jira-task)<a href="https://agentmods.dev/skills/gentleman-programming/gentleman-skills/jira-task"><img src="https://agentmods.dev/badge/skills/gentleman-programming/gentleman-skills/jira-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/gentleman-programming/gentleman-skills/jira-task"><img src="https://agentmods.dev/badge/skills/gentleman-programming/gentleman-skills/jira-task.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.00030 | $0.02434 |
| Opus 5.5 | $0.00012 | $0.00974 |
| Sonnet 5.5 | $0.00006 | $0.00487 |
| Haiku 4.5 | $0.00003 | $0.00243 |
Grade A, and why
jira-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 2mo 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 — 389 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to Use
Use this skill when creating Jira tasks for:
- Bug reports
- Feature requests
- Refactoring tasks
- Documentation tasks
Multi-Component Work: Split into Multiple Tasks
IMPORTANT: When work requires changes in multiple components (API, UI, SDK), create separate tasks for each component instead of one big task.
Why Split?
- Different developers can work in parallel
- Easier to review and test
- Better tracking of progress
- API needs to be done before UI (dependency)
Bug vs Feature: Different Structures
For BUGS: Create separate sibling tasks
Bugs are typically urgent fixes, so create independent tasks per component:
Task 1 - API:
- Title:
[BUG] Add aws_region field to AWS provider secrets (API) - Must be done first (UI depends on it)
Task 2 - UI:
- Title:
[BUG] Add region selector to AWS provider connection form (UI) - Blocked by API task
For FEATURES: Create parent + child tasks
Features need business context for stakeholders, so use a parent-child structure:
Parent Task (for PM/Stakeholders):
- Title:
[FEATURE] AWS GovCloud support - Contains: Feature overview, user story, acceptance criteria from USER perspective
- NO technical details
- Links to child tasks
Child Task 1 - API:
- Title:
[FEATURE] AWS GovCloud support (API) - Contains: Technical details, affected files, API-specific acceptance criteria
- Links to parent
Child Task 2 - UI:
- Title:
[FEATURE] AWS GovCloud support (UI) - Contains: Technical details, component paths, UI-specific acceptance criteria
- Links to parent, blocked by API task
Parent Task Template (Features Only)
## Description
{User-facing description of the feature - what problem does it solve?}
## User Story
As a {user type}, I want to {action} so that {benefit}.
## Acceptance Criteria (User Perspective)
- [ ] User can {do something}
- [ ] User sees {something}
- [ ] {Behavior from user's point of view}
## Out of Scope
- {What this feature does NOT include}
## Design
- Figma: {link if available}
- Screenshots/mockups if available
## Child Tasks
- [ ] `[FEATURE] {Feature name} (API)` - Backend implementation
- [ ] `[FEATURE] {Feature name} (UI)` - Frontend implementation
## Priority
{High/Medium/Low} ({business justification})
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.
- 2mo ago First seen · 389 lines · 30 tokens per session scan A 372c38a6296e
jira-task is a skill published in the GitHub repository Gentleman-Programming/Gentleman-Skills (661 stars, last pushed 7mo ago), licensed MIT. It adds 30 tokens to every session and 2,434 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.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…
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,"…