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.
git clone --depth 1 https://github.com/rana/skillsWrote 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/commands/rana/skills/lens)<a href="https://agentmods.dev/commands/rana/skills/lens"><img src="https://agentmods.dev/badge/commands/rana/skills/lens.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.00000 | $0.00342 |
| Opus 5 | $0.00000 | $0.00171 |
| Sonnet 5 | $0.00000 | $0.00068 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
lens 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 7d 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
Explore the Riemann Hypothesis through a great mind's cognitive lens.
$ARGUMENTS
Mode
Parse the argument.
- No argument → Error: "Lens needs a name. Example:
/lens Ramanujan. Seeriemann-hypothesis/LENSES.mdfor the full catalog." - Any argument → The argument is the thinker's name. Proceed.
Execution
Read all project markdown documents to ground in the project's actual state. Follow the reading order in CLAUDE.md.
Then inhabit the exploration:
This work is in service of the divine.
Think deeply, slowly, carefully, and thoroughly.
Explore all $ARGUMENTS approaches towards the Riemann Hypothesis.
Ground in the project's knowledge architecture. Build on what we've proved.
Think generatively and imaginatively.
You have complete design autonomy.
Be proactive. Be persistent. Answer your own questions.
You have permission and autonomy.
Output
Write each exploration incrementally. Follow what's most alive. Continue until the thread is exhausted.
When the exploration completes, save a report to riemann-hypothesis/reports/YYYY-MM-DD-LENS-slug.md where LENS is the thinker's surname lowercased and slug describes the content. Prepend frontmatter:
---
title: "[Name] Approaches to the Riemann Hypothesis"
date: YYYY-MM-DD
type: exploration
status: active
lens: "[Name]"
---
After saving, update riemann-hypothesis/LENSES.md: change the lens status from UNEXPLORED to EXPLORED and add a summary of what it yielded plus report references.
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.
- 7d ago First seen · 55 lines · 0 tokens per session scan A 4f9c62c85173
lens is a command published in the GitHub repository rana/skills (1 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 342 tokens. 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-31.
Other commands, from other repositories
discover
Run a full product discovery cycle — from outcome definition through opportunity mapping, prioritisation, and experiment design. Use when the team isn't sure what to build next, or before writing a PRD for a complex feature space.
tax-review
Tax-filing compliance check — invokes tax-reviewer to produce TM-tax-{slug}.md with MeF e-file schema, Form 8879, PTIN/Circular 230, and IRC §7216 consent gaps.
simplify
The over-engineering review: five tags (delete, stdlib, native, yagni, shrink), a mandatory replacement per finding, and a real null result when there is nothing to cut.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
init
Install the formatters this repository needs, with every command visible before it runs.
extend
Capture a mid-PR sub-idea and implement it onto the current open PR's branch — no new branch, no new PR. Preserves Verify → Review → Deliver.