Borrowing it
Nothing to install: this file belongs to nick-pape/grackle. 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/nick-pape/grackle/main/.claude/skills/open-ticket/SKILL.mdgit clone --depth 1 https://github.com/nick-pape/grackleWrote 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/nick-pape/grackle/open-ticket)<a href="https://agentmods.dev/skills/nick-pape/grackle/open-ticket"><img src="https://agentmods.dev/badge/skills/nick-pape/grackle/open-ticket.svg" alt="Measured on agentmods" 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.00036 | $0.00817 |
| Opus 5 | $0.00018 | $0.00409 |
| Sonnet 5 | $0.00007 | $0.00163 |
| Haiku 4.5 | $0.00004 | $0.00082 |
Grade A, and why
open-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 8d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Open Ticket — Issue Creation with Spec
This skill creates a new GitHub issue with proper labels and epic assignment, then automatically runs the /write-spec skill to post a requirements specification as a comment.
Step 0: Gather Information
If a title was provided as an argument, use it. Otherwise, ask the user for:
- Title: Short, descriptive issue title
- Description: What is this feature/bug/refactor? (can be brief — the spec will expand it)
REPO="nick-pape/grackle"
Step 1: Fetch Available Labels
Fetch the repository's labels to select the right ones:
gh label list -R $REPO --limit 100 --json name --jq '.[].name'
Step 2: Fetch Open Epics
Fetch the current epic issues to find the right parent:
gh issue list -R $REPO --state open --search "Epic:" --json number,title --jq '.[] | "\(.number): \(.title)"'
Key epics to know:
- #270 — Epic: Orchestration (multi-agent coordination, swarming, reconciliation, escalation)
- #272 — Epic: Web UI features (all frontend/UX work)
- #271 — Epic: Code quality and refactoring
- #273 — Epic: Rushstack tooling adoption (build infra)
Step 3: Classify the Issue
Based on the title and description, determine:
Labels (select all that apply):
- Type:
feature,bug,refactor,infra - Packages:
web,server,cli,powerline,common(based on which packages are affected) - Domain:
orchestration(if related to multi-agent, swarming, task lifecycle, reconciliation, escalation) - Priority:
priority:critical,priority:high,priority:low(if the user specifies, otherwise omit)
Parent Epic:
- Web/UX features → #272
- Orchestration/multi-agent → #270
- Refactoring/code quality → #271
- Build/tooling → #273
- If unclear, ask the user
Step 4: Create the Issue
gh issue create -R $REPO \
--title "<TITLE>" \
--label "<LABELS>" \
--body "$(cat <<'EOF'
## Summary
<User's description, expanded into 2-3 sentences explaining what and why>
## Related
<List any related issues discovered during classification>
EOF
)"
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.
- 8d ago First seen · 103 lines · 36 tokens per session scan A c970e9dd059d
open-ticket is a skill published in the GitHub repository nick-pape/grackle (21 stars, last pushed 2mo ago), licensed MIT. It adds 36 tokens to every session and 817 once invoked, about $0.0002 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-30.
Other skills, from other repositories
create-issue
Draft and submit a GitHub issue from a user idea or bug description, with bilingual body and correct labels.
gh-assign-issues
Use to assign GitHub issues to a milestone and/or owners in bulk, verifying each.
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
github-sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
issue-tracking
Track beads as git-backed issues with persistent attribution, supporting Gas Town's bead lifecycle and convoy progress monitoring.
github-operations
GitHub CLI operations for issues, PRs, milestones, and Projects v2. Covers gh commands, REST API patterns, and automation scripts. Use when managing GitHub issues, PRs, milestones, or Projects with gh.