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 infohata/mind-vault --skill extjs-frontendgit clone --depth 1 https://github.com/infohata/mind-vaultWrote 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/infohata/mind-vault/extjs-frontend)<a href="https://agentmods.dev/skills/infohata/mind-vault/extjs-frontend"><img src="https://agentmods.dev/badge/skills/infohata/mind-vault/extjs-frontend.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.1 | $0.00000 | $0.05196 |
| Opus 5 | $0.00000 | $0.02598 |
| Sonnet 5 | $0.00000 | $0.01039 |
| Haiku 4.5 | $0.00000 | $0.00520 |
Grade A, and why
extjs-frontend 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 3d 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 — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
extjs-frontend
Production patterns for a Sencha ExtJS 7.x Modern-toolkit SPA (Material theme) built by
webpack + @sencha/ext-webpack-plugin + Sencha Cmd, usually with two build profiles
(desktop + phone) sharing an app/shared/ layer, and talking to a remote backend over
REST (/api/* JSON envelopes) + optional WAMP/WebSocket for live updates. Philosophy: the
ViewModel is the state, the ViewController is the only imperative layer, writes go through a
promise service layer, and every claim about framework behavior is proven against the
installed toolkit — the Modern widgets repeatedly do less than their names imply.
Not covered: the Classic toolkit (different component/layout API), Sencha Architect projects, and the backend itself. Pairs with whichever backend skill the API belongs to — the frontend contract is REST + optional WAMP; nothing here assumes a backend framework.
When to use
Precondition — the gate for every trigger below: the repo actually builds a Sencha ExtJS
app (app.json "framework": "ext", @sencha/ext*, or Ext.define( under app/**; see
Stack resolution below). Without that signal none of the triggers fire, however familiar the
symptom sounds.
TRIGGER when: editing Ext.define(...) classes under app/** (views, ViewControllers,
ViewModels, stores, util/service singletons, overrides); adding a dialog, grid, form field
or ui; touching app.json, workspace.json, webpack.config.js, build.xml, .jdk*; writing or
debugging Jest tests against an Ext stub or Playwright specs that drive Ext.ComponentQuery;
seeing a raw <prefix>_* translation key on screen; a "works in dev, dies in the production
build / deployed image" report; a Sencha dev-server that hangs at wait until bundle finished.
SKIP for: ExtJS Classic-only code (Ext.grid.Panel, Ext.window.Window, renderTo
layouts); React/Vue/HTMX frontends (their own stack skills); backend-only work; native
mobile clients; any repo with no ExtJS signal at all — a shared
Jest/Playwright/webpack toolchain on its own is not a trigger, and neither is the word
"SPA".
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/I18N_KEY_SWEEP.md 5.0 KB
- references/JEST_EXT_STUB_HARNESS.md 9.6 KB
- references/MODERN_COMPONENT_FOOTGUNS.md 29 KB
- references/PLAYWRIGHT_COMPONENTQUERY_E2E.md 19 KB
- references/REFACTOR_CONTRACT_PINNING.md 3.3 KB
- references/SENCHA_TOOLCHAIN_AND_BUILD.md 15 KB
- references/SERVICE_LAYER.md 9.2 KB
- VERSION 4 B
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.
- 3d ago Changed e101fdb23692
- 7d ago First seen · 251 lines · 0 tokens per session scan A 13ebcce588f6
extjs-frontend is a skill published in the GitHub repository infohata/mind-vault (2 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 5,196 tokens. 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
menu-transitions-rtl
Animate react-horizontal-scrolling-menu scrolling and build right-to-left menus: noPolyfill defaults to true since v8, so transitionDuration (default 500), a custom-easing-function transitionBehavior, and per-call ScrollOptions { duration, boundary } on scrollToItem/scrollNext/scrollPrev are silently ignored unless…
vite
Vite build tool configuration, plugin API, SSR, and Vite 8 Rolldown migration. Use when working with Vite projects, vite.config.ts, Vite plugins, or building libraries/SSR apps with Vite.