exclude-beta

An agent configuration example with two extensions, where one named beta is explicitly excluded. The alpha extension remains available while beta's tools are not registered.

In plain words
What is it for?
Use it to test extension filtering and confirm that an excluded agent or tool does not load.
Why use it?
It demonstrates how to remove a specific extension even when it is part of the included set.

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/exclude-beta
Clone the repo
git clone --depth 1 https://github.com/tintinweb/pi-subagents
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 120 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.00011 $0.00120
Opus 5 $0.00005 $0.00060
Sonnet 5 $0.00002 $0.00024
Haiku 4.5 $0.00001 $0.00012

Measured 2d ago against content hash f49fadd27785, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

exclude-beta 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 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.

Unrestricted tool accessmediumExcessive agency

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

tools: "*"
test/fixtures/.pi/agents/exclude-beta.md · 13 lines

What it actually says

e2e template: exclude_extensions removes an extension after the include set is computed — alpha surfaces normally, beta's tools never register. (Excluding a name that the extensions: list also loads warns "in both — exclude wins"; the exclusion still applies.)

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. 2d ago First seen · 13 lines · 11 tokens per session scan B f49fadd27785

Subscribe to this mod's changes

exclude-beta is an agent published in the GitHub repository tintinweb/pi-subagents (1,047 stars, last pushed 4d ago), licensed MIT. It adds 11 tokens to every session and 120 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.