Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add postindustria-tech/agentic-toolkit/plugin install pm-practicesWrote 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/postindustria-tech/agentic-toolkit/jira-ticket-quality-audit)<a href="https://agentmods.dev/skills/postindustria-tech/agentic-toolkit/jira-ticket-quality-audit"><img src="https://agentmods.dev/badge/skills/postindustria-tech/agentic-toolkit/jira-ticket-quality-audit/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/postindustria-tech/agentic-toolkit/jira-ticket-quality-audit"><img src="https://agentmods.dev/badge/skills/postindustria-tech/agentic-toolkit/jira-ticket-quality-audit.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.00068 | $0.02233 |
| Opus 5.5 | $0.00027 | $0.00893 |
| Sonnet 5.5 | $0.00014 | $0.00447 |
| Haiku 4.5 | $0.00007 | $0.00223 |
Grade A, and why
jira-ticket-quality-audit 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 10d 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jira ticket quality audit
Assess whether existing tickets can be built and verified from. Read references/rubric.md before scoring. Report defects and fix directions; never edit Jira, create tickets, rewrite descriptions, assign points, or run a whole-requirements coverage audit.
Inputs and scope
Accept ordinary language or invocation arguments; these are interpretation conventions, not an executable CLI. No project config file is required:
--jql QUERY,--filter ID, or--keys KEYS: authorized live ticket scope.--export PATH: ACLI search JSON or Jira REST v3 search response, repeatable for pages and companion full issue details; accept snapshot/provenance notes.--sources PATH: controlling requirements, approved designs, decisions, or other relevant context, repeatable. Ask when source precedence is ambiguous.--exclude-statuses NAMES: completed and QA-accepted workflow states.--repo PATH --base REF: optional repository and team base branch for code claims.--previous PATH: optional previous assessment for a rerun comparison.--output DIR: optional persistent private directory. Without it, write to a new timestamped directory under the system temporary directory and say that it is temporary. Honor a user-chosen directory only after checking it is not tracked or exposed to version control; do not modify ignore rules to make it so.
Resolve the project/filter/keys and workflow semantics before filtering. Assess tickets whose text can still change development or acceptance: include active QA, QA-rejected and On Hold work; exclude Done and QA-accepted work. Do not hardcode another project's status names or equate all QA states with acceptance. Use supplied workflow evidence or ask about ambiguous states; record unresolved eligibility separately instead of silently dropping it. Explicit requests to audit closed tickets override this default and must be stated in the snapshot.
Closed or out-of-query parents, dependencies, and decisions may be read as context without becoming scored tickets. Do not broaden the assessed set without agreement.
What ships with it
10 files 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.
- evals/evals.json 3.4 KB
- evals/fixtures/previous.md 881 B
- evals/fixtures/rerun-page.json 4.6 KB
- evals/fixtures/rerun-snapshot.md 720 B
- evals/fixtures/rules.md 612 B
- evals/fixtures/snapshot.md 1.2 KB
- evals/fixtures/tickets.json 14 KB
- evals/procedure.md 2.8 KB
- evals/results.md 6.1 KB
- references/rubric.md 7.8 KB
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.
- 10d ago First seen · 183 lines · 68 tokens per session scan A 5e7144845976
jira-ticket-quality-audit is a skill published in the GitHub repository postindustria-tech/agentic-toolkit (2 stars, last pushed 11d ago), licensed MIT. It adds 68 tokens to every session and 2,233 once invoked, about $0.0003 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-10-06.
Other skills, from other repositories
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
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.
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…
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…