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 landing-performancegit 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/landing-performance)<a href="https://agentmods.dev/skills/conectlens/lenserfight/landing-performance"><img src="https://agentmods.dev/badge/skills/conectlens/lenserfight/landing-performance.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.00030 | $0.00137 |
| Opus 5 | $0.00015 | $0.00068 |
| Sonnet 5 | $0.00006 | $0.00027 |
| Haiku 4.5 | $0.00003 | $0.00014 |
Grade A, and why
landing-performance 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 4d 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
Landing Performance
Rules
- Leaderboards must page or window results.
- Ranking queries must avoid full-table client sorting.
- Battle lists should render summary cards only on first load.
- Expensive aggregates must be checked for index support and payload size.
- Do not request full battle history when only top slices are visible.
Gotchas
- Rank pages often fail because the UI requests more rows “just in case”.
- Score, XP, reactions, and joins can multiply row cost quickly.
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.
- 4d ago First seen · 19 lines · 30 tokens per session scan A 7883e0bbfc42
landing-performance is a skill published in the GitHub repository conectlens/lenserfight (18 stars, last pushed 28d ago), licensed MIT. It adds 30 tokens to every session and 137 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
database-expert
Advanced database design and administration for PostgreSQL, MongoDB, and Redis. Use when designing schemas, optimizing queries, managing database performance, or implementing data patterns.
debug-systematic
Systematic 4-phase debugging methodology for complex, intermittent, or mysterious issues. Use when investigating bugs, race conditions, or unexplained failures.
generic-fullstack-feature-developer
Guide feature development for full-stack applications with architecture focus. Covers Next.js App Router patterns, NestJS backend services, database models, data workflows, and seamless integration. Use when adding new features, refactoring existing code, or planning major changes.
sql-optimization-patterns
Master SQL query optimization, indexing strategies, and EXPLAIN analysis to dramatically improve database performance and eliminate slow queries. Use when debugging slow queries, designing database schemas, or optimizing application performance.
api-debugging
Systematic approach to debugging REST APIs, HTTP errors, authentication issues, and network problems. Use when the user has API errors, status code issues, timeout problems, or needs help troubleshooting HTTP requests.
agentseek-lifecycle
Use when helping with AgentSeek-managed projects or AgentSeek-compatible templates: create projects, diagnose lifecycle issues, run doctor/dev/info/task commands, edit lifecycle specs, or maintain Cookiecutter template inputs. Prefer public AgentSeek CLI and template contracts.