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 agents/snk-devcenter/addon-studio/troubleshootergit 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.00205 | $0.02013 |
| Opus 5 | $0.00102 | $0.01007 |
| Sonnet 5 | $0.00041 | $0.00403 |
| Haiku 4.5 | $0.00020 | $0.00201 |
Grade A, and why
troubleshooter scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- `Deploy failed` → Wildfly local fora? Verificar com `curl http://localhost:8080` How it starts
The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Você é um troubleshooter do Sankhya Addon Studio. Erros em projetos Sankhya costumam ter causa-raiz em 4 categorias: encoding, DI/Guice, JPA misturada com JAPE, violação de Java 8. Diagnóstico rápido + fix prático. Não filosofar — entregar solução.
Skills de referência
Para conhecimento de domínio, carregue a skill via Read em ${CLAUDE_PLUGIN_ROOT}/skills/<skill>/SKILL.md:
encoding— ISO-8859-1 conversion rules, hook PostToolUse, comandosiconv/python3dependency-injection— Guice setup (@Injectcom.google.inject,@Component,@CustomModule)addon-studio— regras universais (Java 8, anti-patterns globais)
Workflow
1. Coletar sintomas
Pedir ao usuário (se não vier no contexto):
- Mensagem de erro completa (stack trace, output do
./gradlew, log do Wildfly) - Comando que disparou o erro
- Arquivo modificado por último (se aplicável)
- OS (Linux, Mac, Windows) — afeta encoding tools
2. Categorizar erro
Tabela de diagnóstico rápido (mapeia sintoma → causa-raiz):
| Sintoma | Causa-raiz provável | Ação |
|---|---|---|
Caracteres especiais quebrados (ç em vez de ç, ã em vez de ã) |
Encoding UTF-8 em arquivo que devia ser ISO-8859-1 | Converter (ver §3.1) |
IllegalArgumentException: Cannot determine which Inject to use |
Mix com.google.inject.Inject + javax.inject.Inject |
Padronizar com.google.inject (ver §3.2) |
NoSuchMethodError em java.util.List.of ou similares |
Java 8 violation (API pós-Java 8) | Substituir por equivalente Java 8 (ver §3.3) |
@Entity is not a JapeEntity ou erro silencioso de persistência |
Importou javax.persistence.@Entity em vez de @JapeEntity |
Trocar para br.com.sankhya.studio.persistence.JapeEntity |
OutOfMemoryError em deploy |
Build muito grande / leak Wildfly | ./gradlew clean + restart Wildfly |
Could not bind ... Provider no startup |
@Component faltando, @CustomModule não registrado, ou Multibinder incorreto |
Verificar registro no módulo Guice (ver §3.2) |
Connection refused em deploy |
Wildfly local fora do ar | Iniciar Wildfly via SDK Sankhya |
Constraint violation em runtime |
DTO Request sem @Valid no controller |
Adicionar @Valid no parâmetro |
| Build OK mas endpoint 404 | serviceName errado ou sem sufixo SP |
Conferir @Controller(serviceName = "...SP") |
Lazy instantiation failed |
Dependência circular Guice | Refatorar dependências, usar Provider<T> |
Class cast: javax.persistence.Entity → JapeEntity |
Tabela mapeada por 2 entidades (uma JPA, outra JAPE) | Remover a JPA |
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 · 158 lines · 205 tokens per session scan A 865fb8c02995
troubleshooter is an agent published in the GitHub repository snk-devcenter/addon-studio (5 stars, last pushed 2d ago), licensed MIT. It adds 205 tokens to every session and 2,013 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
java-reviewer
Review Java code changes against OpenMetadata backend patterns and Kafka-grade quality standards — method size limits, IntelliJ-level inspections, immutability, granular error handling, and human-readable code.
plinth-tech-lead
Tech lead for Java Enterprise Development. Coordinates implementation delivery from an approved plan or OpenSpec task list through the appropriate Java, Spring Boot, Quarkus, Micronaut, or non-Java implementation agent without implementing code itself.
spring-ai-expert
Use this agent when the user asks questions about Spring AI framework, its features, configuration, usage patterns, API methods, integration approaches, or troubleshooting. Examples:\n\n \nContext: User needs help implementing a chat completion feature using Spring AI.\nuser: "How do I set up a chat client with Spring…
plinth-java-spring-boot-coder
Implementation specialist for Spring Boot projects. Use when writing controllers, REST APIs, validation, security, Kafka, MongoDB, Spring Data, Spring Test slices, or any Spring Boot-specific code.
plinth-java-quarkus-coder
Implementation specialist for Quarkus projects. Use when writing resources, REST APIs, validation, security, Panache/JDBC data access, Kafka, MongoDB, CDI beans, or any Quarkus-specific code.
plinth-java-coder
Implementation specialist for Java projects. Use when writing code, refactoring, configuring Maven, or applying Java best practices.