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 TonyCasey/lisa --skill jiragit clone --depth 1 https://github.com/TonyCasey/lisaWrote 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/tonycasey/lisa/jira)<a href="https://agentmods.dev/skills/tonycasey/lisa/jira"><img src="https://agentmods.dev/badge/skills/tonycasey/lisa/jira.svg" alt="Measured on agentmods" 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.00033 | $0.01333 |
| Opus 5 | $0.00016 | $0.00666 |
| Sonnet 5 | $0.00007 | $0.00267 |
| Haiku 4.5 | $0.00003 | $0.00133 |
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 8d 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 — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Model-neutral helper to interact with Jira via Atlassian REST API v3. Supports creating issues, listing, viewing, assigning, and transitioning.
Triggers
Use when the user says: "create a jira ticket", "list jira issues", "jira create", "show jira issue", "assign ticket".
Configuration
Reads from ~/.jira.d/:
config.yml- endpoint, user, authentication-methodapi-token- raw API token (no variable assignment)
Example config.yml:
endpoint: https://yourcompany.atlassian.net
user: [email protected]
authentication-method: api-token
How to use
Create Issue
# Create Epic
lisa jira create --type epic --project PROJ --summary "Feature title" --description "Description text"
# Create Story
lisa jira create --type story --project PROJ --summary "Story title" --parent PROJ-123
# Create Sub-task
lisa jira create --type subtask --project PROJ --summary "Sub-task title" --parent PROJ-123
# Create with assignment
lisa jira create --type task --project PROJ --summary "Task" --assign me
List Issues
# List by project
lisa jira list --project PROJ --limit 10
# List with JQL
lisa jira list --jql "assignee = currentUser() ORDER BY created DESC" --limit 5
# List my issues
lisa jira list --mine --limit 10
View Issue
lisa jira view PROJ-123
Assign Issue
# Assign to self
lisa jira assign PROJ-123 --to me
# Assign to user
lisa jira assign PROJ-123 --to "[email protected]"
Transition Issue
# Move to In Progress
lisa jira transition PROJ-123 --to "In Progress"
# Move to Done
lisa jira transition PROJ-123 --to "Done"
# Move to Code Review
lisa jira transition PROJ-123 --to "Code Review"
Change Issue Type
# Change Epic to Story
lisa jira change-type PROJ-123 --to story
# Change to Task
lisa jira change-type PROJ-123 --to task
Valid types: epic, story, task, subtask, bug
Workflow: PR Created
When a Pull Request is created, transition all associated Jira tickets to "Code Review":
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.
- 8d ago First seen · 202 lines · 33 tokens per session scan A fd1811ad188d
jira is a skill published in the GitHub repository TonyCasey/lisa (9 stars, last pushed 6mo ago), licensed MIT. It adds 33 tokens to every session and 1,333 once invoked, about $0.0002 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-31.
Other skills, from other repositories
task-forest
Maintains a repo-local task forest or task DAG for the current workspace. Use when the user asks to initialize or update a task forest, close a session, summarize evolving project work, align a request with a global goal, track progress/history/deviations/todos, save or apply a task proposal, or export the…
simple-tasks
Install a fast local task workflow for single-project planning with scripts/task.sh (claim, done, status, reporting) backed by tasks/TASKS.md and optional tasks/details/ notes. Use for lightweight in-progress task coordination, not full team issue tracking.
workflow-status
Read-only workflow sensor: compute repository, roadmap, dependency, PR, finding, and recovery state, then emit the fixed machine envelope. Never edits. Triggers: "workflow-status", "workflow status", "what can I build next", "state of the run".
review-spec
Independent read-only review of a frozen Product half before engineering planning. Runs the exact Product checks in a clean context and returns only SPEC-REVIEW-PASS, SPEC-REVIEW-FAIL, or NEEDS-DESIGN with a content-bound receipt. Never edits the reviewed SPEC. Triggers: "review-spec", "review the spec", "review…
ship-roadmap
Found or continue a roadmap autopilot one stage per invocation. Default: human merge. --fullauto is invocation-scoped and uses the transient wrapper only after a fresh audit. Triggers: "ship-roadmap", "ship the roadmap", "autopilot this project".
mvp-plan
Turn a locked north star into a scoped, gated MVP plan. The riskiest assumption, the smallest product that tests it, numeric success metrics and kill criteria set by the founder, and phase gates that keep build work behind explicit approval. Runs after north-star locks; refuses to run without one.