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-epicgit 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-epic)<a href="https://agentmods.dev/skills/gentleman-programming/gentleman-skills/jira-epic"><img src="https://agentmods.dev/badge/skills/gentleman-programming/gentleman-skills/jira-epic/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-epic"><img src="https://agentmods.dev/badge/skills/gentleman-programming/gentleman-skills/jira-epic.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.00038 | $0.02001 |
| Opus 5.5 | $0.00015 | $0.00800 |
| Sonnet 5.5 | $0.00008 | $0.00400 |
| Haiku 4.5 | $0.00004 | $0.00200 |
Grade A, and why
jira-epic 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 — 313 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 epics for:
- Large features spanning multiple components
- New views/pages in the application
- Major refactoring initiatives
- Features requiring API + UI + SDK work
Epic Template
# {Epic Title}
**Figma:** {figma link if available}
## Feature Overview
{2-3 paragraph description of what this feature does and why it's needed}
## Requirements
### {Section 1: Major Functionality Area}
#### {Subsection}
- Requirement 1
- Requirement 2
- Requirement 3
#### {Another Subsection}
- Requirement 1
- Requirement 2
### {Section 2: Another Major Area}
#### {Subsection}
- Requirement 1
- Requirement 2
## Technical Considerations
### Performance
- {Performance requirement 1}
- {Performance requirement 2}
### Data Integration
- {Data source}
- {Integration points}
### UI Components
- {Component 1}
- {Component 2}
## Implementation Checklist
- [ ] {Major deliverable 1}
- [ ] {Major deliverable 2}
- [ ] {Major deliverable 3}
## Diagrams
{Mermaid diagrams for architecture, flow, data model, etc.}
Epic Title Conventions
Format: [EPIC] Feature Name
Examples:
[EPIC] Findings View[EPIC] Multi-tenant Support[EPIC] Compliance Dashboard Redesign[EPIC] GovCloud Support
Required Sections
1. Feature Overview
Brief but complete description of:
- What the feature does
- Who uses it
- Why it's needed
2. Requirements
Organized by functional area:
- Group related requirements together
- Use clear headers and subheaders
- Be specific and testable
3. Technical Considerations
Always include:
- Performance: Large dataset handling, pagination, caching
- Data Integration: Data sources, APIs, relationships
- UI Components: Reusable components, design system usage
4. Implementation Checklist
High-level deliverables that will become individual tasks:
- Each checkbox = potential Jira task
- Order by dependency (API before UI)
- Include testing milestones
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 · 313 lines · 38 tokens per session scan A 9a7f0c558131
jira-epic is a skill published in the GitHub repository Gentleman-Programming/Gentleman-Skills (661 stars, last pushed 7mo ago), licensed MIT. It adds 38 tokens to every session and 2,001 once invoked, about $0.0002 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,"…