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-start-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-start-ticket)<a href="https://agentmods.dev/skills/haoxiang-xu/pupu/issue-start-ticket"><img src="https://agentmods.dev/badge/skills/haoxiang-xu/pupu/issue-start-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-start-ticket"><img src="https://agentmods.dev/badge/skills/haoxiang-xu/pupu/issue-start-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.00100 | $0.02522 |
| Opus 5.5 | $0.00040 | $0.01009 |
| Sonnet 5.5 | $0.00020 | $0.00504 |
| Haiku 4.5 | $0.00010 | $0.00252 |
Grade A, and why
issue-start-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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue: Start Ticket
The user supplies one or more PuPu ticket URLs. Own implementation, with GitHub
comments recording every meaningful update. Complete implementation and necessary
tests, then wait for the user's close instruction. This skill coordinates
delivery; it does not independently pronounce acceptance. Invoke
issue-feature-audit only on close or an explicit audit request.
Lifecycle: read → clone/research → refine if needed → formal ticket →
implementation with any planned checkpoints → implementation-ready → wait for
close → PR to dev → feature audit → safe cleanup.
Shared contracts
- Read board-api.md before Project operations. Discover IDs, verify membership and the direct Release parent, and read back mutations. A view, assignee or iteration is not membership.
- Read the clone's applicable
AGENTS.md,CLAUDE.mdand rules. Use GitNexus query/context to investigate and upstream impact before symbol edits. Report callers, processes and risk; warn before HIGH/CRITICAL edits and corroborate UNKNOWN with other evidence. Index this clone, not the original checkout. - Apply the repository's cross-boundary contract gate where relevant, including both repositories' impact and BC/SEQ/AC evidence in the issue or direct plan. Do not revive retired court or owner-confirmation workflows.
- Start authorizes scope-preserving refinement, implementation, progress comments and factual Project Status updates. It does not authorize changing title, labels, Size, assignee, release membership or outcome-level scope.
closeauthorizes commits and push necessary for the requested PR, the audit and safe removal of this workflow's clone. This is the user's specific exception to the generic no-commit convention, limited to these delivery changes in the isolated clone. Do not commit during start or alter the original checkout to make the PR. Never auto-merge or bypass branch protection.
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 · 184 lines · 100 tokens per session scan A 413bf10a2514
issue-start-ticket is a skill published in the GitHub repository haoxiang-xu/PuPu (36 stars, last pushed 3d ago), licensed Apache-2.0. It adds 100 tokens to every session and 2,522 once invoked, about $0.0004 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.