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/snk-devcenter/addon-studio/before-load-listenernpx skills add snk-devcenter/addon-studio --skill before-load-listenergit clone --depth 1 https://github.com/snk-devcenter/addon-studioWrote 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/snk-devcenter/addon-studio/before-load-listener)<a href="https://agentmods.dev/skills/snk-devcenter/addon-studio/before-load-listener"><img src="https://agentmods.dev/badge/skills/snk-devcenter/addon-studio/before-load-listener.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.00192 | $0.03104 |
| Opus 5 | $0.00096 | $0.01552 |
| Sonnet 5 | $0.00038 | $0.00621 |
| Haiku 4.5 | $0.00019 | $0.00310 |
Grade A, and why
before-load-listener 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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Interceptador de Buscas (@BeforeLoadListener) — Addon Studio 2.0
@BeforeLoadListener executa lógica personalizada sempre que uma entidade é carregada ou pesquisada via JAPE. Intercepta a execução do Finder — permite adicionar filtros, ordenações ou validar parâmetros de busca antes da query chegar ao banco. A anotação automatiza o atributo finder-listener no XML da entidade — sem edição manual de XML.
⚠️
@BeforeLoadListener≠@Listener. São mecanismos distintos:@BeforeLoadListenerintercepta leitura (busca/carregamento, viaFinderListener) e só funciona em instâncias do próprio add-on;@Listenerreage a escrita (insert/update/delete, viaPersistenceEventAdapter) e aceita também instâncias nativas. Tarefa de gravação/exclusão → skilllistener.
1. Quando usar — @BeforeLoadListener vs @Criteria vs @Listener vs @BusinessRule
| Mecanismo | Escopo | Quando usar |
|---|---|---|
@BeforeLoadListener |
Toda busca/carregamento de UMA entidade (transversal) | Filtro transversal aplicado a toda leitura da entidade, independente de quem consulta (segurança, multi-tenant, soft-delete). |
@Criteria (repository) |
Uma query específica | Filtro pontual em um método de busca declarado no repository. |
@Listener |
CRUD (insert/update/delete) de qualquer entidade | Validar/modificar campos ao gravar/excluir. |
@BusinessRule |
Confirmação/faturamento de notas (saída, mov. interna) | Regras transacionais comerciais com barramento de regras. |
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 · 221 lines · 192 tokens per session scan A 2ebeef0dd908
before-load-listener is a skill published in the GitHub repository snk-devcenter/addon-studio (5 stars, last pushed today), licensed MIT. It adds 192 tokens to every session and 3,104 once invoked, about $0.0010 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…