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 pantheon-org/tekhne --skill jira-ticket-readyupgit clone --depth 1 https://github.com/pantheon-org/tekhneWrote 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/pantheon-org/tekhne/jira-ticket-readyup)<a href="https://agentmods.dev/skills/pantheon-org/tekhne/jira-ticket-readyup"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/jira-ticket-readyup/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/pantheon-org/tekhne/jira-ticket-readyup"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/jira-ticket-readyup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00105 | $0.03576 |
| Opus 5 | $0.00053 | $0.01788 |
| Sonnet 5 | $0.00021 | $0.00715 |
| Haiku 4.5 | $0.00011 | $0.00358 |
Grade A, and why
jira-ticket-readyup 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 — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
jira-ticket-readyup
Turn a sparse Jira backlog ticket — or a brand-new item with no key yet — into a fully-structured "ready for refinement" document by gathering incident context (or interviewing the user when no source material answers a required question), applying the standard template, and validating the output against both the schema and gap-detection heuristics.
When to Use This Skill
Use jira-ticket-readyup when:
- User asks to "ready up" or "prepare for refinement" one or more Jira tickets
- A ticket exists but lacks Context, Conditions of Satisfaction, or Acceptance Criteria
- User wants to promote a follow-up ticket (spawned from an incident) into a proper backlog item
- User wants to draft a brand-new backlog ticket that has no Jira key yet (set
ticket.new_ticket: true— see Step 2a)
Do NOT use for:
- Tickets that are already in "Ready for Refinement" status with full descriptions
What a Good Ticket Looks Like
A ticket is "ready for refinement" when it has all four sections:
| Section | Purpose |
|---|---|
| Context | Background on the service, current behaviour, and why it matters |
| Conditions of Satisfaction | MUST / SHOULD / COULD requirements |
| Acceptance Criteria | Specific, testable conditions that define "done" |
| Supporting Information | Links to repos, files, and related tickets |
The reference example ticket should be supplied by the user when invoking this skill (a ticket already in "Ready for Refinement" status in their Jira project).
Step-by-Step Workflow
Step 1 — Read the YAML template
MANDATORY before generating any output:
# Always read this first — it defines the required fields and comments
skills/project-mgmt/issue-tracker-toolkit/jira-ticket-readyup/assets/templates/ready-for-refinement.yaml
Do NOT generate a ticket data file without loading this template.
Step 2 — Gather context
For an existing ticket (has a Jira key):
- Fetch the ticket itself:
jira_get_issue(issue_key="PROJ-NNN", fields="summary,description,status,issuetype,issuelinks")
What ships with it
15 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.
- assets/schemas/ready-for-refinement.schema.json 4.6 KB
- assets/templates/ready-for-refinement.yaml 2.0 KB
- evals/instructions.json 3.2 KB
- evals/scenario-01/capability.txt 221 B
- evals/scenario-01/criteria.json 1.6 KB
- evals/scenario-01/task.md 802 B
- evals/scenario-02/capability.txt 205 B
- evals/scenario-02/criteria.json 2.0 KB
- evals/scenario-02/task.md 647 B
- evals/scenario-03/capability.txt 296 B
- evals/scenario-03/criteria.json 2.1 KB
- evals/scenario-03/task.md 865 B
- evals/summary.json 345 B
- references/yaml-field-guide.md 4.1 KB
- scripts/validate-ticket.ts 9.6 KB runs code
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 Changed · +53 lines · +5 tokens per session 6fa44620f468
- 7d ago First seen · 211 lines · 100 tokens per session scan A 4763593ae4f1
jira-ticket-readyup is a skill published in the GitHub repository pantheon-org/tekhne (10 stars, last pushed today), licensed MIT. It adds 105 tokens to every session and 3,576 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
aw
Ships autonomous, end-to-end coding work — implement a feature or fix, all the way to a tested draft PR — from a single opt-in entry point. Detects the task tier (Micro / Lite / Full) and routes: Micro/Lite run single-pass in this context; Full hands off to the aw-planner → aw-executor agents. Use when the user asks…
contract-testing-flywheel
Generate a structured onboarding backlog — in Jira, GitHub Issues/Projects, Azure DevOps, or as a manual markdown export — that drives a development team from zero to publishing both consumer and provider contract tests. Use when the user invokes /contract-testing-flywheel or asks to "kick off contract testing for a…
ai-team-orchestration
Bootstrap and run a multi-agent AI development team. Use when: starting a new software project with AI agents, setting up parallel dev/QA teams, creating sprint plans, writing brainstorm prompts with distinct agent voices, recovering a project workflow, or planning sprints.
openspec-implementation
A workflow for implementing an approved technical specification one task at a time. It reads the proposal, makes the changes, runs tests, and validates the result.
multi-role-quality-synthesis
Use this skill when multiple role reports for one quality stage must be combined into a traceable synthesis; triggers include multi-role quality synthesis, role report consolidation, disagreement summary..
project-delivery-perspective
Use this skill when project delivery constraints or action tracking are needed for test strategy, test strategy review, or test report review; triggers include project delivery perspective, delivery planning, schedule and capacity..