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/dependency-injectionnpx skills add snk-devcenter/addon-studio --skill dependency-injectiongit clone --depth 1 https://github.com/snk-devcenter/addon-studioWhat 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.00200 | $0.04003 |
| Opus 5 | $0.00100 | $0.02001 |
| Sonnet 5 | $0.00040 | $0.00801 |
| Haiku 4.5 | $0.00020 | $0.00400 |
Grade A, and why
dependency-injection 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 2d 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 — 437 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Injeção de Dependência (Guice) — Addon Studio 2.0
Addon Studio 2.0 usa Google Guice como container DI. Anotações estereótipo customizadas fazem auto-scan. Doc descreve regras, padrões, boas práticas DI.
1. Regra de Ouro
Sempre injeção via construtor com @Inject de com.google.inject.Inject.
import com.google.inject.Inject;
@Component
public class MeuService {
private final MeuRepository repository;
private final MeuGateway gateway;
@Inject
public MeuService(MeuRepository repository, MeuGateway gateway) {
this.repository = repository;
this.gateway = gateway;
}
}
NUNCA
@Injectdejavax.inject. Semprecom.google.inject.Inject.
2. Estereótipos (Anotações de Auto-Scanning)
Framework scaneia e registra classes com:
| Anotação | Pacote | Gerenciamento | Uso |
|---|---|---|---|
@Controller |
br.com.sankhya.studio.annotations |
Automático — NÃO adicionar @Component |
Entrypoints REST |
@Repository |
br.com.sankhya.studio.stereotypes |
Automático — NÃO adicionar @Component |
Interfaces de acesso a dados (JapeRepository) |
@Component |
br.com.sankhya.studio.stereotypes |
Automático | Classes gerais: Services, Adapters, Gateways, Mappers auxiliares |
@ControllerAdvice |
br.com.sankhya.studio.web |
Automático | Tratamento global de exceções |
@CustomModule |
br.com.sankhya.studio.stereotypes |
Automático | Módulos Guice customizados (equivale a AbstractModule) |
Quando usar cada estereótipo
@Controller -> Entrypoints REST (serviceName obrigatório com sufixo "SP")
@Repository -> Interfaces JapeRepository (NÃO crie implementação manual)
@Component -> Todo o resto que precisa ser injetado
@CustomModule -> Módulos de configuração Guice (bindings manuais)
@ControllerAdvice -> Handler global de exceções
3. Classes por Estereótipo
3.1 @Controller — Entrypoints REST
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.
- 2d ago First seen · 437 lines · 200 tokens per session scan A 88bc5b57c0e1
dependency-injection is a skill published in the GitHub repository snk-devcenter/addon-studio (5 stars, last pushed 2d ago), licensed MIT. It adds 200 tokens to every session and 4,003 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…