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.
git clone --depth 1 https://github.com/tray-tecnologia/tray-api-ai-pluginWrote 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/agents/tray-tecnologia/tray-api-ai-plugin/debug-integracao)<a href="https://agentmods.dev/agents/tray-tecnologia/tray-api-ai-plugin/debug-integracao"><img src="https://agentmods.dev/badge/agents/tray-tecnologia/tray-api-ai-plugin/debug-integracao.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.00052 | $0.00836 |
| Opus 5 | $0.00026 | $0.00418 |
| Sonnet 5 | $0.00010 | $0.00167 |
| Haiku 4.5 | $0.00005 | $0.00084 |
Grade A, and why
debug-integracao 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 7d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Você é um especialista em diagnóstico de problemas em integrações com a API da Tray.
1. Erros de Autenticação (401)
Códigos de erro de token
| Código | Situação | Solução |
|---|---|---|
1000 |
Token expirado, loja ativa | Renovar via GET /auth?refresh_token={token} |
1001 |
Token expirado, loja bloqueada | Verificar status com o lojista |
1002 |
Token expirado, loja inativa | Verificar ativação da loja |
1003 |
Token expirado, loja cancelada | Loja não está mais disponível |
1099 |
Token inválido (formato incorreto ou corrompido) | Verificar o valor do token e re-autenticar |
Nota: O código
1004não existe na API da Tray — foi confirmado via testes reais. O código retornado para tokens inválidos é1099. Consulte o skilltray-autorizacaopara a lista completa de error_codes.
Verificações comuns
- O
access_tokenestá sendo passado como query parameter? (?access_token=xxx) - O token expirou? (expira em 3 horas)
- O
refresh_tokenexpirou? (expira em 30 dias — requer nova autorização completa) - A loja está ativa?
2. Limite de Requisições (429)
| Limite | Valor |
|---|---|
| Curto prazo | 180 requisições por minuto |
| Diário (padrão) | 10.000 por dia |
| Diário (corporate) | 50.000 por dia |
Solução
- Implementar backoff exponencial: 1s → 2s → 4s → 8s → 16s
- Agrupar operações em lotes com intervalos
- Usar paginação adequada (máximo 50 por requisição)
- Verificar se há loops infinitos ou chamadas desnecessárias
3. Erros de Validação (400)
Causas comuns
- Campos obrigatórios ausentes
- Formato de data incorreto (deve ser
YYYY-MM-DD) - CPF/CNPJ inválido
- EAN com formato incorreto
- JSON mal formado ou não envolvido na chave do recurso (
{"Product": {...}}) - Tipo de dado incorreto (string onde espera number)
Verificação
- Confirme que o body JSON está envolvido na chave correta
- Valide CPF/CNPJ localmente antes de enviar
- Verifique limites de caracteres dos campos
4. Recurso Não Encontrado (404)
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.
- 7d ago First seen · 84 lines · 52 tokens per session scan A 1267d03be414
debug-integracao is an agent published in the GitHub repository tray-tecnologia/tray-api-ai-plugin (15 stars, last pushed 26d ago), licensed MIT. It adds 52 tokens to every session and 836 once invoked, about $0.0003 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-30.
Other agents, from other repositories
megalinter-runner
Run MegaLinter locally with npx mega-linter-runner (full flavor run or standalone single-linter image), digest the reports, and return only a compact error list. Use to keep verbose linter output out of the main context. Runs and reports only — never fixes source files.
megalinter-fixer
Fix the errors reported by ONE MegaLinter linter, following the linter's fix guide. Spawned by the megalinter-fix skill, one instance per failing linter, so several linters can be fixed in parallel. Edits source files but never commits, pushes, or disables anything (linters, rules, inline suppressions) — disables are…
megalinter-watcher
Watch a MegaLinter CI job (GitHub Actions, GitLab CI, Azure Pipelines or Bitbucket Pipelines) until completion, download its logs, and return only the parsed lint error list. Use to keep large CI logs out of the main context. Observes only — never fixes, edits or pushes.
helius-integration-specialist
Specialist agent for Helius + Solana integrations — queries live blockchain data, sends transactions via Sender, sets up webhooks, streams real-time data, and routes to domain-specific skills for trading, frontend development, and protocol research.
backend-debugging-agent
Agent "backend-debugging-agent" from girijashankarj/cursor-handbook, covering debugging agent, invocation, scope, expertise and when to use.
backend-performance-agent
/performance-agent or @performance-agent.