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/drafthq/draft/jiranpx skills add drafthq/draft --skill jiragit clone --depth 1 https://github.com/drafthq/draftWhat 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.00020 | $0.05311 |
| Opus 5 | $0.00010 | $0.02655 |
| Sonnet 5 | $0.00004 | $0.01062 |
| Haiku 4.5 | $0.00002 | $0.00531 |
Grade A, and why
jira 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 — 598 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jira
Single entry point for all Jira workflows: preview Draft tracks as Jira issues, create them via MCP (default = 1 Story per track; --epic = 1 Epic + 1-3 Stories), and review any Jira ticket (epic, story, bug, sub-task) end-to-end.
Subcommand Routing
Parse $ARGUMENTS and dispatch:
| User Intent | Subcommand | Behavior |
|---|---|---|
(no args), preview, preview <track-id> |
preview (default) | Generate jira-export-<timestamp>.md — one Story containing all phases/tasks |
preview --epic ... |
preview --epic | Generate rich export: 1 Epic + 1–3 Stories (max) |
create, create <track-id> |
create | Create 1 Story (default) via MCP |
review <JIRA_ID> |
review | Full qualification review of any Jira ticket — delegates to references/review.md |
previewis the default when no subcommand is supplied.reviewrequires a Jira ID as the next argument. Validate format<PROJECT>-<NUMBER>(e.g.,ENG-446236). If numeric-only, prompt for project prefix — do NOT assume.
Jira Configuration (Shared)
All subcommands read project-level Jira configuration from draft/workflow.md under a ## Jira section:
## Jira
Project Key: <KEY>
Integration: jira-mcp
Team: <team-name>
Component: <component-name>
Swimlane: <swimlane-name>
Assignee Display Name: <assignee-name>
- Project Key — required for
create. If missing, prompt and persist. - Integration — informational; defaults to
jira-mcpif absent. - Team / Component / Swimlane / Assignee Display Name — applied as defaults to every issue created by
create. Empty values are skipped (Jira ignores blank fields).
If a value is missing when needed:
- Prompt the user for it.
- Append to (or create) the
## Jirasection indraft/workflow.mdso subsequent runs reuse it.
Jira Content Hygiene (Mandatory)
When writing any text that will go into Jira (descriptions, summaries, bug details):
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 598 lines · 20 tokens per session scan A 5978f7975fa2
jira is a skill published in the GitHub repository drafthq/draft (40 stars, last pushed 14d ago), licensed MIT. It adds 20 tokens to every session and 5,311 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
memorix-memory
Use when prior workspace context, past decisions, solved bugs, handoff state, or durable project knowledge would help a coding task.
memorix
Use when Claude Code needs Memorix shared memory, reasoning, Git Memory, mini-skills, session handoff, orchestration coordination, or integration troubleshooting.
memorix-mini-skills
Use when durable project knowledge, gotchas, workflows, or repeated fixes should become reusable agent guidance instead of ordinary memory.
memorix-orchestrate
Use when a main agent needs Memorix to coordinate explicit subagent work through tasks, handoffs, messages, file locks, or the orchestrate CLI.
memorix-reasoning
Use when a technical decision, trade-off, rejected alternative, architecture rationale, or design risk should be recorded or recovered.
memorix-sessions
Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether sessionstart is useful.