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 skills/conectlens/lenserfight/github-issue-solvernpx skills add conectlens/lenserfight --skill github-issue-solvergit clone --depth 1 https://github.com/conectlens/lenserfightWhat 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.00069 | $0.02949 |
| Opus 5 | $0.00034 | $0.01474 |
| Sonnet 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 2d 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.
- 2d 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 (19 stars, last pushed 22d ago), licensed MIT. It adds 69 tokens to every session and 2,949 once invoked, about $0.0003 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-30.
Other skills, from other repositories
managed-pentesting-with-strix
Run a managed pentest of a web app, API, repository, or local workspace on the app.strix.ai platform with the strix cloud CLI or REST API — no local Docker or LLM key needed. Safely review and upload local source, register assets, launch and poll scans, triage vulnerabilities, export SARIF, download compliance…
api-security-testing
Security-test a REST, GraphQL, or gRPC API with Strix — autonomous agents that enumerate endpoints from an OpenAPI/GraphQL schema (or by crawling), then actually exploit the API-specific vulnerability classes in the OWASP API Security Top 10 (2023) — broken object-level authorization (BOLA/IDOR), broken object…
fix-security-vulnerabilities-with-strix
Fix security vulnerabilities found by a Strix pentest (open-source CLI or app.strix.ai cloud) — triage by severity, patch the root cause rather than the symptom, and re-run Strix to prove each fix actually closes the exploit. Handles injection, XSS, SSRF, broken access control, IDOR, and other validated findings. Use…
owasp-top-10-testing
Test an application against the OWASP Top 10 with Strix — autonomous AI agents that attempt real exploits for each category of the current OWASP Top 10:2025 (broken access control including SSRF, security misconfiguration, software supply chain failures, cryptographic failures, injection, insecure design…
find-security-vulnerabilities-in-code
Find security vulnerabilities in a codebase or repository with Strix — a white-box AI security review that reads your source, reasons about the actual data flow and authorization model, then exploits what it finds in a live sandbox so every reported issue has a working proof-of-concept instead of a noisy…
web-app-penetration-testing
Pentest a web app or website end to end — black-box testing of a live URL, staging environment, or local dev server that finds and exploits real vulnerabilities (auth bypass, broken access control, IDOR, injection, XSS, SSRF, business logic) and proves each one with a working proof-of-concept instead of a signature…