lazy-no-selector

A test for a lazy-loaded tool: a tool that becomes available after the agent starts must still be found and usable.

In plain words
What is it for?
Use it to verify that tools registered during a session-start event remain available after the tool loader refreshes.
Why use it?
It catches a setup bug where tools added later are missed permanently.

Agent

Install

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.

agentmods
npx agentmods add agents/tintinweb/pi-subagents/lazy-no-selector
Clone the repo
git clone --depth 1 https://github.com/tintinweb/pi-subagents
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 94 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00013 $0.00094
Opus 5 $0.00006 $0.00047
Sonnet 5 $0.00003 $0.00019
Haiku 4.5 $0.00001 $0.00009

Measured yesterday against content hash 842dbbe6172f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

lazy-no-selector scanned grade B with 1 finding 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 yesterday.

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.

Unrestricted tool accessmediumExcessive agency

A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.

tools: "*"
test/fixtures/.pi/agents/lazy-no-selector.md · 10 lines

What it actually says

e2e template: ext-lazy registers lazy_tool from session_start, i.e. AFTER loader.reload() has already run. Any scoping that snapshots the tool set at construction drops it permanently — this asserts it survives.

Changes

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.

  1. yesterday First seen · 10 lines · 13 tokens per session scan B 842dbbe6172f

Subscribe to this mod's changes

lazy-no-selector is an agent published in the GitHub repository tintinweb/pi-subagents (1,022 stars, last pushed 3d ago), licensed MIT. It adds 13 tokens to every session and 94 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.