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 speedscale/speedy-template --skill jira-ticketsgit clone --depth 1 https://github.com/speedscale/speedy-templateWrote 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/speedscale/speedy-template/jira-tickets)<a href="https://agentmods.dev/skills/speedscale/speedy-template/jira-tickets"><img src="https://agentmods.dev/badge/skills/speedscale/speedy-template/jira-tickets/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/speedscale/speedy-template/jira-tickets"><img src="https://agentmods.dev/badge/skills/speedscale/speedy-template/jira-tickets.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.00084 | $0.00814 |
| Opus 5 | $0.00042 | $0.00407 |
| Sonnet 5 | $0.00017 | $0.00163 |
| Haiku 4.5 | $0.00008 | $0.00081 |
Grade A, and why
jira-tickets 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 9d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jira Tickets
Customization: Replace
SPDwith your Jira project prefix throughout this file.
Manage Jira tickets using acli jira. The project prefix is SPD.
Key Commands
View a ticket
acli jira workitem view SPD-1234
Search tickets (JQL)
# By assignee
acli jira workitem search --jql "project = SPD AND assignee = currentUser() AND status != Done" --limit 20
# By status
acli jira workitem search --jql "project = SPD AND status = 'In Progress'" --limit 20
# By text
acli jira workitem search --jql "project = SPD AND text ~ 'search term'" --limit 20
# Custom fields output
acli jira workitem search --jql "project = SPD" --fields "key,summary,status,assignee" --csv
Transition status
acli jira workitem transition --key SPD-1234 --status "In Progress" --yes
acli jira workitem transition --key SPD-1234 --status "Done" --yes
Add a comment
IMPORTANT: All bot comments MUST start with === bot === on its own line. The agent uses your personal credentials, so this prefix distinguishes bot actions from human actions. This is critical for auditability.
acli jira workitem comment create --key SPD-1234 --body "=== bot ===
your actual comment text here"
Edit a ticket
acli jira workitem edit --key SPD-1234 --summary "New title" --yes
acli jira workitem edit --key SPD-1234 --description "New description" --yes
acli jira workitem edit --key SPD-1234 --assignee "[email protected]" --yes
acli jira workitem edit --key SPD-1234 --labels "label1,label2" --yes
Create a ticket
acli jira workitem create # interactive prompt
List comments
acli jira workitem comment list --key SPD-1234
Assign
acli jira workitem assign --key SPD-1234 --assignee "[email protected]"
acli jira workitem assign --key SPD-1234 --assignee "@me"
Conventions
- "Ticket" means Jira ticket
- Strings matching
SPD-\d+are ticket keys (change prefix to match your project) - Always use
--yesflag on transitions and edits to skip confirmation prompts - Use
--jsonflag when structured output is needed for further processing - ALL comments MUST start with
=== bot ===on its own line — this is a shared-credential safety measure
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.
- 9d ago First seen · 94 lines · 84 tokens per session scan A 2fd6b7f9225e
jira-tickets is a skill published in the GitHub repository speedscale/speedy-template (5 stars, last pushed 6mo ago), licensed MIT. It adds 84 tokens to every session and 814 once invoked, about $0.0004 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
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.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
remove
Remove a deployed framework or addon from the current workspace.