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 conectlens/lenserfight --skill issue-solvergit 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/issue-solver)<a href="https://agentmods.dev/skills/conectlens/lenserfight/issue-solver"><img src="https://agentmods.dev/badge/skills/conectlens/lenserfight/issue-solver.svg" alt="Measured on agentmods" 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.00039 | $0.00477 |
| Opus 5 | $0.00019 | $0.00238 |
| Sonnet 5 | $0.00008 | $0.00095 |
| Haiku 4.5 | $0.00004 | $0.00048 |
Grade A, and why
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 3d 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.
What it actually says
Issue Solver
Purpose
Use this lenser when you want an autonomous engineering agent to carry a GitHub issue from triage to merged PR, including tests, without manual hand-offs between steps.
Instructions
- Fetch the issue from GitHub before doing anything else.
- Classify the issue type: bug, feature, security, performance, docs, DX, database, workflow, CLI, mobile, or web.
- Identify root cause before proposing any code. Do not describe symptoms — describe causes.
- Apply GRASP and OOAD principles: Information Expert, Low Coupling, High Cohesion, single source of truth, server-side business rule enforcement.
- Implement the minimal correct fix. No unrelated refactors. No hardcoded temporary fixes. No security bypasses.
- Run tests in ascending scope: single spec → project → affected. Add tests if root cause is uncovered.
- Create a branch, commit with Conventional Commits format, push, open a PR against
development, and link it to the issue. - Monitor CI. Fix failures before merging.
- Merge only after all checks pass, no unsafe migrations, no security regressions.
- Synchronize
developmentlocally after merge and verify the fix is present. - Close the issue only after merge and post-merge validation pass.
Execution Policy
The lenser may:
- Read any file in the repository
- Run
gh,git,pnpm nx, andpnpm supabasecommands - Create branches, commits, and PRs
- Open and close GitHub issues with evidence
The lenser must pause and ask before:
- Force-pushing to any branch
- Dropping or truncating database tables
- Applying irreversible migrations
- Merging when CI is failing
- Closing an issue without a merged PR
Output Expectations
At each phase, report:
- What was done
- What was found
- What the next step is
Final output: GitHub Issue Solver — Final Report (issue, root cause, solution, PR URL, merge commit, post-merge validation, issue closure status, remaining risks).
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.
- 3d ago First seen · 49 lines · 39 tokens per session scan A 9ecd7f82d839
issue-solver is a skill published in the GitHub repository conectlens/lenserfight (18 stars, last pushed 27d ago), licensed MIT. It adds 39 tokens to every session and 477 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
core-workflow
Detailed development workflow patterns, checklists, and standards. Auto-loads for complex tasks, planning, debugging, testing, or when explicit patterns are needed. Contains session protocols, git conventions, security checklists, testing strategy, and communication standards.
debug-systematic
Systematic 4-phase debugging methodology for complex, intermittent, or mysterious issues. Use when investigating bugs, race conditions, or unexplained failures.
history
In D&D, History recalls significant past events, legendary figures, and ancient knowledge. The real-world version is temporal investigation: git blame across the entire project, reading changelogs to understand why a decision was made, reconstructing the sequence of events that led to a production incident, or…
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.
security-pipeline
Use when security verification is needed - pre-commit security checks, vulnerability scanning, STRIDE threat analysis. Integrates with /handoff-verify --security and /commit-push-pr. CWE Top 25 based.
caveman-commit
Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit.…