Borrowing it
Nothing to install: this file belongs to conectlens/lenserfight. 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/conectlens/lenserfight/main/.agents/skills/github-issue-solver/SKILL.mdgit clone --depth 1 https://github.com/conectlens/lenserfightWrote 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/conectlens/lenserfight/github-issue-solver)<a href="https://agentmods.dev/skills/conectlens/lenserfight/github-issue-solver"><img src="https://agentmods.dev/badge/skills/conectlens/lenserfight/github-issue-solver/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/conectlens/lenserfight/github-issue-solver"><img src="https://agentmods.dev/badge/skills/conectlens/lenserfight/github-issue-solver.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00069 | $0.02949 |
| Opus 5.5 | $0.00028 | $0.01180 |
| Sonnet 5.5 | $0.00014 | $0.00590 |
| Haiku 4.5 | $0.00007 | $0.00295 |
Grade A, and why
github-issue-solver 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 — 432 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Issue Solver
Solve GitHub issues end-to-end: triage → explore → design → implement → test → PR → merge → close.
Never guess architecture. Never close an issue before the PR is merged.
Activation Criteria
Invoke this skill when:
- User says
/github-issue-solveror/solve-issue - User says "solve issue #N", "fix GitHub issue #N", "work on issue #N"
- User pastes a GitHub issue URL
- User asks to process open issues from the repository
Workflow
Step 1 — Fetch Issue Metadata
gh issue view <number> --json title,body,labels,milestone,assignees,comments,url,state,linkedBranches
Capture and record:
- Title and full body
- Labels (bug, feature, security, docs, performance, DX, auth, database, workflow, battle, CLI, mobile, web)
- Milestone and due date
- All comments (may contain constraints or partial solutions)
- Linked PRs or branches
If no issue number is provided, ask the user which issue(s) to target.
Step 2 — Check for Duplicates and Related Work
gh issue list --state all --search "<key terms from title>"
gh pr list --state all --search "<key terms>"
If a duplicate exists: comment on the issue linking the canonical one, then stop.
Step 3 — Repository Exploration
Do not assume architecture. Explore:
apps/* — entry points and composition roots
libs/domain/* — business concepts, invariants, core types
libs/api/* — contracts and DTOs
libs/data/* — repositories, Supabase integration
libs/features/* — feature slices and orchestration
libs/infra/* — analytics, moderation, storage adapters
libs/ui/* — UI components, forms, layout, tokens
libs/utils/* — low-level shared utilities
supabase/ — schema, migrations, RLS policies, SQL functions
.github/workflows/ — CI/CD pipelines and test commands
apps/cli/ — CLI if issue is CLI-related
apps/mobile/ — mobile app if issue is mobile-related
package.json / pnpm-workspace.yaml — test and build commands
CLAUDE.md / CONTRIBUTING.md — coding standards and rules
.claude/skills/ — available AI agent skills
What ships with it
4 files 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 · 432 lines · 69 tokens per session scan A 2621f58a9c35
github-issue-solver is a skill published in the GitHub repository conectlens/lenserfight (18 stars, last pushed 1mo ago), licensed MIT. It adds 69 tokens to every session and 2,949 once invoked, about $0.0003 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
potpie-graph
Use when the task can read or write the project-memory graph through the potpie CLI: discover the contract with graph catalog, read named views with graph read, resolve entity identity with graph search-entities, create validated plans with graph propose, commit plans with graph commit --verify, inspect quality with…
pipeline-conductor
Operating procedure for the kirocrew-pipeline-conductor agent. Use when a pipeline conductor session is seeded, inspected or debugged. You MANAGE one issue/PR pipeline on one repo: two columns per item (session working? item solved?), send intent, never re-derive a red yourself.
commit-messages
Write git commit messages and pull request titles in the WARP format used by the swarms repo.
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.
create-milestone
Create a GitHub milestone for an upcoming release. Suggests the next version based on the latest release, gathers all merged PRs and closed issues since that release, presents a draft with two tables (Issues and PRs) for user approval, then creates the milestone and assigns all approved items.
github-monitor
Watch your GitHub repos across four views - a combined urgency monitor (stale PRs, new issues, releases), a new-issue triage queue, a release upgrade digest, or your own opened-PR tracker.