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 EricTechPro/startup-claude-skills --skill fix-ticketgit clone --depth 1 https://github.com/EricTechPro/startup-claude-skillsWrote 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/erictechpro/startup-claude-skills/fix-ticket)<a href="https://agentmods.dev/skills/erictechpro/startup-claude-skills/fix-ticket"><img src="https://agentmods.dev/badge/skills/erictechpro/startup-claude-skills/fix-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/erictechpro/startup-claude-skills/fix-ticket"><img src="https://agentmods.dev/badge/skills/erictechpro/startup-claude-skills/fix-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.00115 | $0.08459 |
| Opus 5.5 | $0.00046 | $0.03384 |
| Sonnet 5.5 | $0.00023 | $0.01692 |
| Haiku 4.5 | $0.00012 | $0.00846 |
Grade A, and why
fix-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 — 766 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix Ticket
Automate the full lifecycle of a Jira bug ticket: read the ticket, implement the fix, review changes, commit, transition to QA, assign to QA engineer, and comment with a summary. Zero-touch pipeline from ticket to QA handoff.
Prerequisites
Read CONFIG.md at the start of every run. This file contains project-specific settings (Jira project key, team members, transition IDs, deployment config, QA credentials). If CONFIG.md doesn't exist, warn the user and point them to CONFIG.template.md.
When to Use
- User passes a Jira ticket ID (e.g.,
PROJ-123) and wants it fixed end-to-end - User says "fix this ticket", "resolve this bug", "fix and ship PROJ-XXX"
- Any bug ticket that needs the full fix-review-commit-handoff cycle
Parameters
| Parameter | Default | Description |
|---|---|---|
| (first arg) | required | Jira ticket ID (e.g., PROJ-123) |
branch |
ask |
Branch strategy: ask (default — prompt user to choose), worktree (isolated worktree, auto-merges to main), main (commit directly to main), new (create fix branch) |
skip-review |
false |
Skip the review-team phase |
skip-jira |
false |
Skip Jira transition/assign/comment (just fix and commit) |
assignee |
(from CONFIG.md) | QA assignee: alias from CONFIG.md or a Jira accountId |
auto-commit |
true |
Auto-commit after fix is verified |
skip-deploy |
false |
Skip deployment monitoring |
skip-verify |
false |
Skip pre-fix QA verification (headless browser bug reproduction) |
skip-qa-check |
false |
Skip post-fix QA verification (headless browser fix confirmation) |
Invocation
/fix-ticket PROJ-123 # asks branch strategy first (default)
/fix-ticket PROJ-123 branch=main # urgent fix, commit directly to main
/fix-ticket PROJ-123 branch=new # create fix/PROJ-123 branch
/fix-ticket PROJ-123 branch=worktree # isolated worktree (great for parallel runs)
/fix-ticket PROJ-123 skip-review=true
/fix-ticket PROJ-123 skip-jira=true
/fix-ticket PROJ-123 skip-deploy=true
/fix-ticket PROJ-123 skip-verify=true
/fix-ticket PROJ-123 skip-qa-check=true
What ships with it
1 file 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 · 766 lines · 115 tokens per session scan A 338c93381553
fix-ticket is a skill published in the GitHub repository EricTechPro/startup-claude-skills (60 stars, last pushed 4mo ago), licensed MIT. It adds 115 tokens to every session and 8,459 once invoked, about $0.0005 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-08-30.
Other skills, from other repositories
agent-merge-conflict-arbiter
Neutral arbiter for merge conflicts between two agents.
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
enable-check-includes-strict
Enable and migrate Chromium targets and directories to checkincludesstrict = true, diagnosing and resolving header include violations as part of the checkincludesstrict LSC. Use when adding directories to the allowlist, enabling strict header checks on targets, or resolving CHECKINCLUDESSTRICTUNTRIAGED targets.
resolve-handoff
Emit the complete Resolve handoff with exact modes, outcomes, test evidence, and publication state.
reproduce-and-fix-issues
Reproduce triaged Slack bugs through a configured app-control adapter, verify existing fixes, and open a bounded draft pull request only after before-and-after proof. Use only from the configured Benny repro automation.
cy-orquestrate-issue
Orchestrate GitHub bug resolution through a new CompozyOS managed worktree and Claude Opus 5.5 Medium session per issue. Investigate reported bugs, create missing issues, and dispatch an executor responsible for a detailed PR, green CI, and all CodeRabbit and Greptile feedback. Use when asked to delegate issue…