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/jobnpx skills add snk-devcenter/addon-studio --skill jobgit 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.00163 | $0.03718 |
| Opus 5 | $0.00081 | $0.01859 |
| Sonnet 5 | $0.00033 | $0.00744 |
| Haiku 4.5 | $0.00016 | $0.00372 |
Grade A, and why
job 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 — 316 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jobs Agendados (@Job) — Addon Studio 2.0
@Job substitui a configuracao via mgeschedule.xml por abordagem declarativa diretamente na classe Java. Jobs sao gerenciados pelo SDK e suportam injecao de dependencias.
1. Anatomia de um @Job
import br.com.sankhya.studio.annotations.Job;
import br.com.sankhya.studio.persistence.Transactional;
import br.com.sankhya.studio.stereotypes.IJob;
import com.google.inject.Inject;
@Job(
serviceName = "ProcessadorDeFilaSP", // Obrigatorio — convencao: terminar com "SP"
frequency = "0 0/5 * * * ?" // Opcional (default "&60000") — CRON e SEM "&"
)
public class ProcessadorDeFilaJob extends IJob { // IJob e CLASSE ABSTRATA — use extends
private final FilaService filaService;
@Inject
public ProcessadorDeFilaJob(FilaService filaService) {
this.filaService = filaService;
}
@Override
@Transactional
public void onSchedule() {
filaService.processarItens(); // Logica delegada ao Service
}
}
Imports criticos (assinaturas reais do SDK):
@Job→br.com.sankhya.studio.annotations.Job(naostereotypes.Job)@Transactional→br.com.sankhya.studio.persistence.Transactional(naotransaction.Transactional)IJob→br.com.sankhya.studio.stereotypes.IJob(classe abstrata →extends)EJBTransactionType→br.com.sankhya.studio.annotations.enums.EJBTransactionType
2. Atributos da anotacao @Job
| Atributo | Obrigatorio | Descricao | Exemplo |
|---|---|---|---|
serviceName |
Sim | Nome unico do job (sem default). Convencao: terminar com "SP". | "SincronizadorSP" |
frequency |
Nao | Frequencia padrao. Default "&60000" (60s). ms usa prefixo &; CRON e SEM &. |
"0 0 2 * * ?" / "&60000" |
transactionType |
Nao | Comportamento transacional (EJBTransactionType). Default: Supports. |
EJBTransactionType.NotSupported |
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 · 316 lines · 163 tokens per session scan A 44a8265a578f
job is a skill published in the GitHub repository snk-devcenter/addon-studio (5 stars, last pushed 2d ago), licensed MIT. It adds 163 tokens to every session and 3,718 once invoked, about $0.0008 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…