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 patrickserrano/lacquer --skill github-issue-fix-flowgit clone --depth 1 https://github.com/patrickserrano/lacquerWrote 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/patrickserrano/lacquer/github-issue-fix-flow)<a href="https://agentmods.dev/skills/patrickserrano/lacquer/github-issue-fix-flow"><img src="https://agentmods.dev/badge/skills/patrickserrano/lacquer/github-issue-fix-flow/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/patrickserrano/lacquer/github-issue-fix-flow"><img src="https://agentmods.dev/badge/skills/patrickserrano/lacquer/github-issue-fix-flow.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.00050 | $0.00914 |
| Opus 5.5 | $0.00020 | $0.00366 |
| Sonnet 5.5 | $0.00010 | $0.00183 |
| Haiku 4.5 | $0.00005 | $0.00091 |
Grade A, and why
github-issue-fix-flow 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Issue Fix Flow
Overview
Resolve a GitHub issue from intake through fix, validation, and push using gh CLI, local edits, and git.
Workflow
1) Intake and Issue Context
Get full issue context:
gh issue view <id> --comments
If repo is unclear:
gh repo view --json nameWithOwner
Capture from the issue:
- Reproduction steps
- Expected behavior
- Maintainer notes or labels
- Related issues or PRs
2) Locate the Code Path
Search for relevant code:
# Find files related to the issue
rg -n "keyword from issue"
# Find function definitions
rg -n "func relevantFunction"
# Find type definitions
rg -n "struct|class|enum RelevantType"
Read relevant code paths and understand:
- Entry points
- Data flow
- Existing patterns and conventions
3) Implement the Fix
Guidelines:
- Edit the minimal set of files
- Keep changes aligned with existing architecture and style
- Add tests when behavior changes and coverage is practical
- Follow repo-specific conventions (check CONTRIBUTING.md, AGENTS.md, CLAUDE.md)
4) Build and Test
For Swift/Xcode projects:
# Build
swift build
# or
xcodebuild -scheme MyApp -destination 'platform=macOS' build
# Test
swift test
# or
xcodebuild -scheme MyAppTests -destination 'platform=macOS' test
For other projects, use appropriate build/test commands.
Report warnings or failures - do not hide them.
5) Commit and Push
Check for unrelated changes:
git status --short
git diff
Stage only the fix:
git add <specific files>
Commit with closing message:
git commit -m "Fix: <description>
Closes #<issue number>"
Push:
git push
6) Report Back
Provide summary:
- What changed and where
- Test results (including any failures)
- Follow-ups or blocked items
Quick Reference
| Task | Command |
|---|---|
| View issue | gh issue view <id> --comments |
| List issues | gh issue list |
| View repo | gh repo view --json nameWithOwner |
| Create branch | git checkout -b fix/issue-<id> |
| Stage files | git add <files> |
| Commit | git commit -m "Fix: ... Closes #<id>" |
| Push | git push -u origin HEAD |
| Create PR | gh pr create --fill |
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 · 178 lines · 50 tokens per session scan A e7be49fce19d
github-issue-fix-flow is a skill published in the GitHub repository patrickserrano/lacquer (4 stars, last pushed 2d ago), licensed MIT. It adds 50 tokens to every session and 914 once invoked, about $0.0002 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-31.
Other skills, from other repositories
gh-skill
Manage agent skills with gh skill. Use this skill to discover, preview, install, update, and publish Agent Skills so an agent can self-manage the skills available in its environment.
gh
Patterns for invoking the GitHub CLI (gh) from agents. Covers structured output, pagination, repo targeting, search vs list, gh api fallback.
release
Prepare code for release (version bumps, changelog, README updates) and create an annotated tag to trigger the GoReleaser workflow.
commit-msg
You receive a git diff of staged changes via stdin. Generate a commit message.
vhs-e2e-gif
Record a test run, a TUI session, or any terminal command as a GIF with VHS and attach it to a GitHub PR as a release-hosted asset, never a repo commit. Use when asked to record an e2e run, demo a fix on a PR, attach a GIF or screen recording to a pull request, show a test passing visually, or produce a terminal…
check-linters-before-commit
Before any commit, run linters, vet, tests, and build verification; do not commit until checks pass.