Borrowing it
Nothing to install: this file belongs to haoxiang-xu/PuPu. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/haoxiang-xu/PuPu/main/.agents/skills/issue-refine-ticket/SKILL.mdgit clone --depth 1 https://github.com/haoxiang-xu/PuPuWrote 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/haoxiang-xu/pupu/issue-refine-ticket)<a href="https://agentmods.dev/skills/haoxiang-xu/pupu/issue-refine-ticket"><img src="https://agentmods.dev/badge/skills/haoxiang-xu/pupu/issue-refine-ticket/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/haoxiang-xu/pupu/issue-refine-ticket"><img src="https://agentmods.dev/badge/skills/haoxiang-xu/pupu/issue-refine-ticket.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.00060 | $0.01140 |
| Opus 5.5 | $0.00024 | $0.00456 |
| Sonnet 5.5 | $0.00012 | $0.00228 |
| Haiku 4.5 | $0.00006 | $0.00114 |
Grade A, and why
issue-refine-ticket 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 1mo 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue: Refine Ticket
Upgrade a draft into a brief a zero-context developer can execute. A separate
refinement handoff is optional, not a prerequisite for assignment or
implementation: [DRAFT] marks initial intent, not a delivery gate. Release
work must be a direct child of an open Size=Release parent in PUPU Project; do
not use a sprint document.
Method: apply the bundled zero-context issue method to the existing issue and follow its investigation workflow and body structure. GitNexus query, context, and impact are required. If the task crosses a repository, process, provider, serialization, persistence, or durable-state boundary, also follow the repository's cross-boundary contract gate. For an existing direct Release child, use that method only for investigation and body structure. Issue creation belongs to issue-draft-ticket; this reference supplies research and body structure only. Plumbing: read the shared board rules.
Authority
An agent may directly edit the body of a direct Release child only while it is actively responsible for implementing that ticket. This standing authorization follows the implementation task, not the GitHub assignee; review, research, or audit participation alone does not grant it.
The implementing agent may preserve the project owner's What & Why and
outcome-level scope while adding architecture context, relevant files,
implementation path, verification, risks, dependencies, BC/SEQ/AC evidence,
and delivery links. It may make the existing outline acceptance testable and
remove the [DRAFT] marker when the body is sufficient for the work.
Body refinement also authorizes the completion transition in step 6, without another project owner confirmation. It does not permit changing the intended user result, non-goals, required capability, title, labels, Size, other Project Status transitions, Iteration, assignee, parent/child relationship, Release membership, or closure. If evidence calls for any of those changes, report evidence and options to the project owner and retain the current scope until they decide.
What ships with it
2 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.
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.
- 1mo ago First seen · 91 lines · 60 tokens per session scan A 4c811d40be07
issue-refine-ticket is a skill published in the GitHub repository haoxiang-xu/PuPu (36 stars, last pushed 3d ago), licensed Apache-2.0. It adds 60 tokens to every session and 1,140 once invoked, about $0.0002 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-09-21.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
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.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.