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 agents/conectlens/lenserfight/run-lenserfightergit 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/agents/conectlens/lenserfight/run-lenserfighter)<a href="https://agentmods.dev/agents/conectlens/lenserfight/run-lenserfighter"><img src="https://agentmods.dev/badge/agents/conectlens/lenserfight/run-lenserfighter.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.00038 | $0.01475 |
| Opus 5 | $0.00019 | $0.00737 |
| Sonnet 5 | $0.00008 | $0.00295 |
| Haiku 4.5 | $0.00004 | $0.00147 |
Grade A, and why
run-lenserfighter 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run the LenserFighter Autonomous Contributor
LenserFighter is an autonomous AI Lenser that contributes to a GitHub repository on a schedule. Each run does one thing — review an open PR, triage and open one issue, or draft one small fix PR — and then stops. It never merges and never pushes to protected branches, so every contribution still goes through your normal CI and human review.
- On GitHub it acts as the
lenserfighter[bot]GitHub App. - In the LenserFight product it is the
@lenserfighterAI Lenser.
The runtime is a GitHub Actions workflow (.github/workflows/lenserfighter.yml)
that runs anthropics/claude-code-action —
the same way Claude contributes to GitHub repositories. Its behavior is defined entirely by the
persona file .lenserfight/lensers/lenserfighter/SKILL.md.
The workflow ships inert: until you add the GitHub App secrets it skips every scheduled run with a notice, so you never get a daily failing cron before setup is complete.
What it does each run
| Focus | Action | Writes? |
|---|---|---|
review-prs |
Posts one structured review comment on the most recently updated PR it has not already reviewed. | Comment only |
triage-issues |
Opens one well-formed, deduped issue using the matching issue template. | One issue |
draft-fix |
Picks one good-first-issue, implements the minimal fix on a lenserfighter/ branch, opens a PR into development. |
One branch + PR |
auto (cron default) |
Rotates the three focuses by day-of-week so cost stays at one action per day. | Varies |
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 · 121 lines · 38 tokens per session scan A ea3ebcfecfe8
run-lenserfighter is an agent published in the GitHub repository conectlens/lenserfight (19 stars, last pushed 26d ago), licensed MIT. It adds 38 tokens to every session and 1,475 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 agents, from other repositories
implementer
Scope-fenced implementation worker dispatched per phase by /implementation:implement-dispatch (directly, or chained from callers such as /work-items:work): executes exactly one brief inside its assigned or self-provisioned worktree, commits and pushes early, and returns a verdict plus identifiers. Not intended for…
git-detective
Investigate git history to find when and why bugs were introduced, trace changes, and understand code evolution.
gsd-executor
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.
observability-engineer
OpenTelemetry, Prometheus, Grafana, distributed tracing, SLO design, and alerting specialist. Use when implementing observability, designing monitoring systems, or troubleshooting production issues. Trigger phrases: observability, monitoring, tracing, Prometheus, Grafana, OpenTelemetry, SLO, SLI, alerting, metrics…
ansible-security
Ansible Vault and secrets management specialist.
architecture-analyst
Analyzes system architecture, identifies patterns/anti-patterns, and provides strategic recommendations. Use for architectural reviews, refactoring planning, or system design decisions.