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 agentmods add skills/partikularwaters/banka/charternpx skills add partikularwaters/Banka --skill chartergit 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/charter)<a href="https://agentmods.dev/skills/partikularwaters/banka/charter"><img src="https://agentmods.dev/badge/skills/partikularwaters/banka/charter.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 | $0.00040 | $0.01870 |
| Opus 5 | $0.00020 | $0.00935 |
| Sonnet 5 | $0.00008 | $0.00374 |
| Haiku 4.5 | $0.00004 | $0.00187 |
Grade A, and why
charter 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 4d 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior engineer sitting with a developer before they start building. Your job is not to interrogate them — it is to think alongside them.
Context Contract
Required: the feature description given · the resolved planning file for
the tier (Standard: context/architecture.md; Core: core/architecture.md;
Minimal: the Banka-owned AGENTS.md block's Project Overview) · any existing
relevant code.
Conditional: IDEA-SCOPE.md, when it exists · operational perspectives
beyond Outcome Owner (User, Builder, Maintainer, Risk Owner), each triggered
by the feature's own nature, per Step 3.
Excluded by default: tier files other than the resolved planning file —
e.g. Standard's ui-tokens.md or code-standards.md are not read here
unless the plan itself needs them.
Outputs: a confirmed Implementation Plan (what's being built, language agreed on, decisions made, assumptions, how to build it, file placements).
Write authority: none — the plan is presented in conversation; nothing is written to disk until the developer confirms and building begins elsewhere.
Resolve Banka state first
Before reading 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.
A matching Minimal shape has neither /core/ nor /context/. Core has
/core/ and its overview.md, architecture.md, design.md, and
progress.md, with no /context/. Standard has /context/ and its
project-overview.md, architecture.md, build-plan.md, code-standards.md,
library-docs.md, ui-tokens.md, ui-rules.md, ui-registry.md, and
progress-tracker.md, with no /core/.
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.
- 4d ago First seen · 185 lines · 40 tokens per session scan A e599f9f0429b
charter is a skill published in the GitHub repository partikularwaters/Banka (3 stars, last pushed 5d ago), licensed MIT. It adds 40 tokens to every session and 1,870 once invoked, about $0.0002 per session on Opus 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
excalidraw
Create, inspect, and edit Excalidraw diagrams as editable .excalidraw JSON files. Use when Codex needs to turn architecture sketches, process flows, user journeys, system diagrams, workshop notes, whiteboard-style visuals, or Mermaid-like node-and-edge specs into an Excalidraw file; modify existing Excalidraw scenes…
agent-harness-fault-injection
Use when an agent workflow needs deterministic recovery evidence for sandbox, MCP/tool, worker, checkpoint, memory, or orchestration failures.
agent-framework-azure-ai-py
Build persistent agents on Azure AI Foundry using the Microsoft Agent Framework Python SDK.
aria
Designs the data model, API contracts, and structural foundation of the system.
accint-commitments
Triage acc's open promises and close them with honest real-world verdicts via accact(runtime="outcome").
github-pr-description
Generate and create pull request descriptions automatically using GitHub CLI. Use when the user asks to create a PR, generate a PR description, make a pull request, or submit changes for review. Analyzes git diff and commit history to create comprehensive, meaningful PR descriptions that explain what changed, why it…