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/moornpx skills add partikularwaters/Banka --skill moorgit 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/moor)<a href="https://agentmods.dev/skills/partikularwaters/banka/moor"><img src="https://agentmods.dev/badge/skills/partikularwaters/banka/moor.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.00056 | $0.02000 |
| Opus 5 | $0.00028 | $0.01000 |
| Sonnet 5 | $0.00011 | $0.00400 |
| Haiku 4.5 | $0.00006 | $0.00200 |
Grade A, and why
moor 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 5d 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context Contract
Required: the component file(s) or engineering outcome being captured · the resolved destination file for the tier and capture type (see Step 1).
Conditional: every existing UI component file in the project — audit
mode only, to build the whole-codebase baseline · evidence that survey
has passed this build, before capturing a UI pattern or an
invariant/token change (not a general outcome/decision capture) — audit
mode is exempt.
Excluded by default: width/height, layout mechanics, positioning, animation/transition timing, and responsive breakpoint variants — Step 2 lists these as deliberately not extracted.
Outputs: a registry or session-state entry (single-capture mode), or a proposed baseline plus a deviation list (audit mode) — audit mode's baseline is written only after developer confirmation.
Write authority: the one resolved destination file for the capture type (UI registry or session-state file, by tier), append/update in place — never a file outside that resolved destination.
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.
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.
- 5d ago First seen · 164 lines · 56 tokens per session scan A 5f49e8dddaf4
moor is a skill published in the GitHub repository partikularwaters/Banka (3 stars, last pushed today), licensed MIT. It adds 56 tokens to every session and 2,000 once invoked, about $0.0003 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
project-context-steward
Use when / 当用户进入一个新项目或跨仓库工作区，需要扫描产品、用户、业务工作流、技术架构、仓库边界、领域语言、阅读入口和历史踩坑，并生成或持续维护全局 PROJECTCONTEXT.md。适合用户说“先完整看下项目并沉淀上下文”“给这个项目建上下文文档”“把这次踩坑更新到项目上下文”。不用于单个 PRD 起草、纯目录治理或一次性代码实现。.
memory-hygiene
Manual memory tiering — classify Hot/Warm/Cold, review candidates, and migrate MEMORY.md index + memory files. Use when the session-start advisory fires, MEMORY.md Hot grows past 15 entries, or you want a periodic cleanup. Trigger "memory-hygiene", "整理記憶", "memory 降級", "/memory-hygiene", "decay scan", "tier memory".…
cm-continuity
Working memory protocol — maintains context across sessions via CONTINUITY.md. Inspired by Loki Mode. Read at turn start, update at turn end. Captures mistakes and learnings to prevent repeating errors.
cm-notebooklm
Sync high-value dev knowledge (skills, decisions, lessons) into Google NotebookLM for cloud recall, podcasts, and flashcards. Pairs with Dockit/deep-search. Use for NotebookLM, nlm, knowledge base, skill sync, or cross-machine AI memory.
cm-continuity
Working memory protocol — maintains context across sessions via CONTINUITY.md. Inspired by Loki Mode. Read at turn start, update at turn end. Captures mistakes and learnings to prevent repeating errors.
cm-continuity
Working memory protocol — maintains context across sessions via CONTINUITY.md. Inspired by Loki Mode. Read at turn start, update at turn end. Captures mistakes and learnings to prevent repeating errors.