What is tiered-plan-limits?

A billing guide for choosing different caps, quotas, limits, storage amounts, or compute sizes across pricing plans. It derives the values from the existing relationship between plan prices and credits.

Use it when adding or changing a tier-specific limit, such as automation counts, storage, rate limits, feature quotas, or runtime resources.

Arbitrary per-plan numbers can break the pricing structure, especially when tiers are meant to scale by a consistent ratio.

tiered-plan-limits — Skill for Claude Code and Codex by companion-inc

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.

Any agent

npx skills add companion-inc/introspect --skill tiered-plan-limits

Clone the repo

git clone --depth 1 https://github.com/companion-inc/introspect

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/companion-inc/introspect/tiered-plan-limits/github.svg)](https://agentmods.dev/skills/companion-inc/introspect/tiered-plan-limits)

Your own site

<a href="https://agentmods.dev/skills/companion-inc/introspect/tiered-plan-limits"><img src="https://agentmods.dev/badge/skills/companion-inc/introspect/tiered-plan-limits/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/companion-inc/introspect/tiered-plan-limits"><img src="https://agentmods.dev/badge/skills/companion-inc/introspect/tiered-plan-limits.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 111 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,256 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00111	$0.01256
Opus 5.5	$0.00044	$0.00502
Sonnet 5.5	$0.00022	$0.00251
Haiku 4.5	$0.00011	$0.00126

Measured 2mo ago against content hash 74c198651b7e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

tiered-plan-limits 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 2mo 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.

skills/tiered-plan-limits/SKILL.md · 83 lines

How it starts

The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Tiered plan limits

Problem this handles

When you add a per-tier quantity to a pricing system (a cap, quota, or limit that differs by plan), the tiers already encode a ratio in their price and credits. Inventing round numbers (10 / 25 / 100) that look reasonable but break that ratio is a real, observed failure: shipping maxAutomations at Plus 10 / Pro 25 / Max 100 drew "did u not see pricing for each plan why is the multiple off" — because every other field scales 5× then 2×, but 25 is 2.5× of 10. The value was corrected to Pro 50 to restore the ladder.

Activation boundary

Load when: adding or changing a field in PLAN_TIERS or COMPUTER_RUNTIME_TIERS (src/lib/billing/constants.ts); building a plan gate; picking a per-plan cap, quota, storage size, rate limit, feature count, or compute/runtime size (vCPU, RAM, sandbox/E2B template per plan); reviewing such a change.

Near-misses (do not load): a single non-tiered constant; pricing copy with no quantitative tier ladder; a flat limit that is identical across all plans.

Procedure

Open src/lib/billing/constants.ts and read PLAN_TIERS. Add the new limit as a sibling field on PlanTierSpec, in the same source of truth as monthlyDollars / includedCredits — not a separate parallel constant.
Compute the existing ladder from the fields that already scale with value — monthlyDollars and includedCredits. As of writing: Plus $20 / 2000cr, Pro $100 / 10000cr, Max $200 / 20000cr → Plus→Pro = 5×, Pro→Max = 2×. Re-derive these from the file each time; don't trust this snapshot.
Set the new field to follow that ladder unless there is a stated product reason not to. If the limit should follow a different curve (flat cap, diminishing returns, a hard technical ceiling like Max's storage), say so explicitly and confirm the curve with the user before shipping — do not silently pick round numbers.
Enforce at the single choke point, mirroring maxAutomationsForPlan → scheduleTaskForCurrentChat, so both creation paths pass through one gate.
In your report, state the multiple you used (e.g. "5×/2×, matching price and credits") so the user can sanity-check the ratio at a glance.

Read the full file on GitHub · 83 lines

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.

2mo ago First seen · 83 lines · 111 tokens per session scan A 74c198651b7e

Subscribe to this mod's changes

tiered-plan-limits is a skill published in the GitHub repository companion-inc/introspect (10 stars, last pushed 2mo ago), licensed MIT. It adds 111 tokens to every session and 1,256 once invoked, about $0.0004 per session on Opus 5.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-08-31.

Finance and fintech

tiered-plan-limits next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
tiered-plan-limitscompanion-inc/introspect	Skill	10	2mo ago	MIT	A	111	Claude Code, Codex
sector-rotationHKUDS/Vibe-Trading	Skill	38k	yesterday	MIT	A	39	Claude Code, Codex
twitter-readerhimself65/finance-skills	Skill	3.5k	2d ago	MIT	A	110	Claude Code
strategy-pivot-designertradermonty/claude-trading-skills	Skill	3.7k	2d ago	MIT	A	28	Claude Code, Codex
energy-procurementhashgraph-online/awesome-codex-plugins	Skill	1.5k	yesterday	Apache-2.0	A	93	Claude Code, Codex
airdrop-hunting-guidenirholas/three.ws	Skill	269	yesterday	Apache-2.0	A	54	Claude Code, Codex
multi-expert-analyzerdigoal/blog	Skill	8.6k	2d ago	GPL-2.0	A	292	Codex