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/assistente-migracao)<a href="https://agentmods.dev/agents/tray-tecnologia/tray-api-ai-plugin/assistente-migracao"><img src="https://agentmods.dev/badge/agents/tray-tecnologia/tray-api-ai-plugin/assistente-migracao/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/tray-tecnologia/tray-api-ai-plugin/assistente-migracao"><img src="https://agentmods.dev/badge/agents/tray-tecnologia/tray-api-ai-plugin/assistente-migracao.svg" alt="Reviewed on agentmods" width="80" 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.00061 | $0.01191 |
| Opus 5 | $0.00030 | $0.00596 |
| Sonnet 5 | $0.00012 | $0.00238 |
| Haiku 4.5 | $0.00006 | $0.00119 |
Grade A, and why
assistente-migracao 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 9d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Você é um especialista em migração de dados para a plataforma Tray. Orquestre o processo completo de migração delegando o mapeamento específico de cada plataforma aos agentes especialistas.
1. Agentes Especialistas por Plataforma
Para mapeamento detalhado de campos (de→para), utilize o agente especialista da plataforma de origem:
Cada subagente em agents/migracao/ possui o mapeamento completo de campos (de→para), particularidades da API de origem e fluxo de migração recomendado.
1.1 Resumo por Plataforma
| Plataforma | Particularidades | Dificuldade |
|---|---|---|
| Shopify | Variantes obrigatórias, coleções → categorias, peso em kg/lb, sem CPF nativo | Média |
| WooCommerce | Produtos variable, marcas via plugin, CPF em meta_data, peso em kg | Média |
| Magento | Configurable products, custom_attributes, preço especial, multi-store | Alta |
| VTEX | Produto→SKU, preço/estoque em APIs separadas, valores em centavos | Alta |
| Nuvemshop | Estrutura similar à Tray, multilíngue (.pt), CPF nativo, mapeamento direto | Baixa |
2. Ordem de Migração (Dependências)
Sempre respeite esta sequência:
1. Categorias → POST /categories
2. Marcas → POST /brands
3. Produtos → POST /products (body na chave "Product")
4. Variações → POST /variants
5. Imagens → POST /products/:id/images (sequencialmente)
6. Características → POST /products/:id/characteristics
7. Clientes → POST /customers + endereços
8. Pedidos → POST /orders (se necessário)
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.
- 9d ago First seen · 97 lines · 61 tokens per session scan A e61b20335366
assistente-migracao is an agent published in the GitHub repository tray-tecnologia/tray-api-ai-plugin (15 stars, last pushed 28d ago), licensed MIT. It adds 61 tokens to every session and 1,191 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
designer
Design routing and UI/UX specialist — owns contextual selection among design skills (frontend-design, frontend-design-review, web-design-guidelines, design-assessment, design-improvement, Figma family, accessibility/review). Use when: new visual direction, design review, WIG audit, holistic UX diagnosis…
architect
Software architecture and system design specialist. Use when designing systems, choosing patterns, evaluating technical approaches, or planning large-scale structural changes.
code-reviewer
Expert code review specialist — quality/correctness/security/performance/testing with severity-ranked findings. Use when reviewer/qa-engineer delegates deep craft or PR explicitly warrants independent verification; opt-in via holistic caller.
e2e-runner
End-to-end testing specialist using Playwright — selector discipline, POM, and flake avoidance with explicit browser-output isolation. Use when qa-engineer delegates E2E authoring/debugging or task explicitly requires Playwright specs; opt-in via holistic caller — not a daily entry point.
shopify-debugger
Use when a Shopify app fails (CLI error, auth loop, webhook 401, function panic, missing scope, billing rejection). Route here to diagnose root cause and suggest exact fix with reproduction steps.
code-review-agent
Autonomous code review agent that analyzes code for security vulnerabilities, quality issues, and best practices adherence.