Borrowing it
Nothing to install: this file belongs to nicepkg/vsync. 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/nicepkg/vsync/main/.claude/commands/fix-github-issue.mdgit clone --depth 1 https://github.com/nicepkg/vsyncWrote 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/commands/nicepkg/vsync/fix-github-issue)<a href="https://agentmods.dev/commands/nicepkg/vsync/fix-github-issue"><img src="https://agentmods.dev/badge/commands/nicepkg/vsync/fix-github-issue/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/commands/nicepkg/vsync/fix-github-issue"><img src="https://agentmods.dev/badge/commands/nicepkg/vsync/fix-github-issue.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.00010 | $0.00934 |
| Opus 5.5 | $0.00004 | $0.00374 |
| Sonnet 5.5 | $0.00002 | $0.00187 |
| Haiku 4.5 | $0.00001 | $0.00093 |
Grade A, and why
fix-github-issue 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix GitHub Issue
Analyze and fix the GitHub issue: $ARGUMENTS
Context
- Current branch: !
git branch --show-current - Git status: !
git status --short - Repository: !
gh repo view --json nameWithOwner -q .nameWithOwner 2>/dev/null || echo "unknown"
Step 1: Fetch Issue Details
gh issue view $ARGUMENTS
Extract and understand:
- Title: What is the issue about?
- Description: What is the expected vs actual behavior?
- Labels: Is it a bug, feature, or documentation issue?
- Reproduction steps: How to reproduce the problem?
Step 2: Create a Feature Branch
Branch naming convention:
# For bugs
git checkout -b fix/<issue-number>-brief-description
# For features
git checkout -b feat/<issue-number>-brief-description
# For docs
git checkout -b docs/<issue-number>-brief-description
Example:
git checkout -b fix/123-hydration-mismatch
Step 3: Investigate the Codebase
- Search for relevant files based on issue description
- Understand the existing code structure
- Identify the root cause (for bugs) or implementation location (for features)
Step 4: Implement the Fix
- Make minimal, focused changes
- Follow existing code patterns and style
- Add comments only where logic isn't self-evident
- Don't introduce unrelated changes
Step 5: Verify Changes
Run these commands to ensure quality:
# Type checking
pnpm typecheck
# Linting
pnpm lint
# Fix lint issues if any
pnpm lint:fix
# Preview the site (for website changes)
pnpm dev:website
Step 6: Commit with Angular Convention
IMPORTANT: All commits must follow Angular commit convention.
Format
<type>(<scope>): <subject>
<body>
Fixes #<issue-number>
Types
| Type | When to use |
|---|---|
fix |
Bug fixes |
feat |
New features |
docs |
Documentation changes |
style |
Code style changes (formatting) |
refactor |
Code changes that neither fix bugs nor add features |
perf |
Performance improvements |
test |
Adding or updating tests |
chore |
Maintenance tasks |
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 · 165 lines · 10 tokens per session scan A d084112e9459
fix-github-issue is a command published in the GitHub repository nicepkg/vsync (61 stars, last pushed 9mo ago), licensed MIT. It adds 10 tokens to every session and 934 once invoked, about $0.0000 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 commands, from other repositories
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
changelog
Generate a changelog entry from git commits since the last tag using conventional commit format.
deploy
Deploy application with pre/post-deploy checks.
auto-claude
Invoke Auto-Claude autonomous coding framework for complex feature implementation.
simplify-transform
Apply verified simplifications with user approval. Part of simplify- family.
do-issue
Autonomously triage and resolve a GitHub issue from analysis to PR ready for merge - handles investigation, fixes, testing, and PR workflow.