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 agentmods add commands/parkerm2/create-claude-workflow/link-ticketgit clone --depth 1 https://github.com/ParkerM2/create-claude-workflowWhat 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 | $0.00017 | $0.02369 |
| Opus 5 | $0.00009 | $0.01184 |
| Sonnet 5 | $0.00003 | $0.00474 |
| Haiku 4.5 | $0.00002 | $0.00237 |
Grade A, and why
link-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 3d 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 — 292 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Link Ticket Workflow
Auto-sync GitHub PRs to Jira tickets with intelligent status transitions based on branch patterns, PR state, and ticket availability.
Integration Points
- Jira MCP:
jira_get_issue,jira_change_issue_status,jira_get_transitions,jira_add_comment - GitHub MCP: Current branch detection, PR URL parsing
- Memory: Project key storage, recent linkages
- Anthropic Engineering Plugin: Deployment status updates (via status transitions)
Workflow Phases
Phase 1: Detection (Branch & Ticket Extraction)
Extract ticket identifiers from current context:
-
Branch Pattern Parsing
- Support patterns:
feature/DEV-1234-description→DEV-1234fix/PROJ-567/bug-title→PROJ-567DEV-1234/description→DEV-1234DEV-1234→DEV-1234- Commits with
[DEV-1234]→DEV-1234
- Regex:
([A-Z][A-Z0-9]+-\d+) - Extract all matches, prioritize first occurrence
- Support patterns:
-
Current Context Resolution
- Try: current git branch → git commit message → provided argument
- Command:
git rev-parse --abbrev-ref HEAD - If no branch pattern, prompt user for ticket key or PR URL
-
Project Key Inference
- Extract from ticket (e.g.,
DEV-1234→DEV) - Check memory for cached project keys
- If new project, store in
memory/project-keys.yaml
- Extract from ticket (e.g.,
Verification Checklist:
- Ticket key matches pattern
[A-Z]+-\d+ - Project key cached or inferrable
- No ambiguous matches (e.g., two different projects in branch name)
Phase 2: Validation (Jira & GitHub)
Verify that ticket and (if applicable) PR exist:
-
Jira Ticket Validation
- Call
jira_get_issuewith extracted ticket key - If not found: Graceful degradation — log warning, ask user to create ticket or correct key
- Extract ticket metadata: summary, status, type, assignee, current transitions
- Store full issue data for Phase 4
- Call
-
GitHub PR Detection (if applicable)
- If user provides PR URL: validate format and existence
- If linking existing PR: verify branch matches ticket pattern
- Call GitHub API to get PR state (open/closed/merged)
- Extract PR number, branch, creator
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.
- 3d ago First seen · 292 lines · 17 tokens per session scan A acb809947b6a
link-ticket is a command published in the GitHub repository ParkerM2/create-claude-workflow (4 stars, last pushed 5mo ago), licensed MIT. It adds 17 tokens to every session and 2,369 once invoked, about $0.0001 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-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.