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 partikularwaters/Banka --skill scalegit clone --depth 1 https://github.com/partikularwaters/BankaWrote 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/partikularwaters/banka/scale)<a href="https://agentmods.dev/skills/partikularwaters/banka/scale"><img src="https://agentmods.dev/badge/skills/partikularwaters/banka/scale/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.
<a href="https://agentmods.dev/skills/partikularwaters/banka/scale"><img src="https://agentmods.dev/badge/skills/partikularwaters/banka/scale.svg" alt="Reviewed on agentmods" width="80" 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.00059 | $0.02732 |
| Opus 5.5 | $0.00024 | $0.01093 |
| Sonnet 5.5 | $0.00012 | $0.00546 |
| Haiku 4.5 | $0.00006 | $0.00273 |
Grade A, and why
scale 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CRITICAL: Do not execute a promotion unless the user explicitly requested this command, OR one of the current tier's thresholds is actually met (see below). Always promote exactly one tier at a time — even if it looks like both tiers' thresholds are already met, promote to the next tier up, confirm it's correct, then separately re-check whether a second promotion is also warranted. Never jump from Minimal straight to Standard in one pass.
Note: this skill's "promotion" is tier-level (Minimal→Core→Standard) only.
remember and moor use a separate, within-tier "promotion check": moving a
durable fact from session-state to the file that owns it. That is not a tier
promotion and this skill has no role in it.
Context Contract
Required: the current tier's complete state (the Banka-owned AGENTS.md
block, or every /core/ or /context/ file) · the relevant threshold
figures (word/character counts, registry entry count).
Excluded by default: the next tier beyond the one promotion step being performed — scale never previews a Core→Standard split while executing Minimal→Core.
Outputs: the proposed destination files in full, and the proposed
replacement AGENTS.md block, shown before anything is finalized.
Write authority: the marked AGENTS.md block, plus the tier's target
directory and files — only after the user confirms the shown mapping, and
only for the single tier step being promoted. A promoted project must still
pass the Cold Agent Test once the write completes: a fresh session must recover
the tier, original scope, current state, governing rules, and next action from
disk alone.
Resolve Banka state first
Before reading or writing project state, inspect AGENTS.md, the complete
contents of CLAUDE.md, /core/, /context/, and the required tier files.
Active schema 2 requires one complete Banka block in AGENTS.md containing
these exact comments exactly once and in this order: <!-- BANKA:START -->,
<!-- BANKA:STATE-SCHEMA: 2 -->, exactly one of
<!-- BANKA:TIER: Minimal -->, <!-- BANKA:TIER: Core -->, or
<!-- BANKA:TIER: Standard -->, then <!-- BANKA:END -->. The declared tier
must match the filesystem shape and required files. CLAUDE.md must be exactly
@AGENTS.md; if it is missing, schema 2 is still
active for a runtime that discovers AGENTS.md directly, but report that
Claude Code compatibility is unavailable.
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.
- 1mo ago Changed · +76 lines 7e2874261490
- 1mo ago Changed · +7 lines d64484b434a7
- 1mo ago First seen · 132 lines · 59 tokens per session scan A 963e67190af9
scale is a skill published in the GitHub repository partikularwaters/Banka (3 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 2,732 once invoked, about $0.0002 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.
Other skills, from other repositories
tastemaker
Generate genuinely beautiful, on-brand UI instead of generic "AI slop" — use whenever the user asks to build, design, style, or improve a UI, landing page, dashboard, app screen, or component, whenever a PRD/spec needs a design pass before implementation, whenever the user pastes reference images/Pinterest/Dribbble…
fde
Keeps the engagement record for client work. Use when they name a client or stakeholder. Use when they debrief a meeting or paste notes. Use when they ask what was agreed. Use when they run a POC, change the client's codebase, prove it on their staging, go live, or need evals before a model acts. Use when they prep a…
board-memo
Draft a board or executive summary of an engagement using outcomes, risks and investment decisions. Use when the sponsor needs to brief senior leadership.
brief
Clarify a new customer brief, desired outcome, constraints and evidence gaps. Use for kickoff or a first meeting; do not repeat discovery already supplied.
business-case
Develop a business case for an initiative using costs, benefits, risks and evidence. Use when a sponsor needs budget or timeline justification.
earn-trust
Plan how to earn customer trust and appropriate access. Use when credibility, permissions or AI policy constrain the engagement.