tray-pagamentos

tray-pagamentos is a skill for Claude Code from tray-tecnologia/tray-api-ai-plugin. It costs 176 tokens per session (12,029 once invoked), scanned A, original, MIT.

Uma integração com a API de pagamentos da Tray, uma plataforma de comércio eletrónico. Permite gerir pagamentos e consultar as opções e configurações de pagamento da loja.

In plain words
What is it for?
Serve para listar, consultar, criar, atualizar e excluir pagamentos, além de consultar opções ativas e configurações de pagamento.
Why use it?
Evita implementar separadamente operações sobre pagamentos, métodos disponíveis e definições globais da loja.

Skill for Claude Code

Written for Claude Code: when-to-use in frontmatter. Also seen: mentions Claude Code.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is node skills/tray-dev/scripts/search_docs.mjs --topic=pagamentos "<termo da pergunta>".

Part of the tray-api plugin — 36 skills, 3 commands, 5 agents, 1 MCP server shipped together

Good fit Serve para listar, consultar, criar, atualizar e excluir pagamentos, além de consultar opções ativas e configurações de pagamento.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/tray-tecnologia/tray-api-ai-plugin
agentmods
npx agentmods add skills/tray-tecnologia/tray-api-ai-plugin/pagamentos

Made for: Claude Code.

Or install tray-api, the plugin that ships this one along with the rest of its 36 skills, 3 commands, 5 agents, 1 MCP server.

Wrote 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.

agentmods badge for tray-pagamentos

README.md
[![agentmods](https://agentmods.dev/badge/skills/tray-tecnologia/tray-api-ai-plugin/pagamentos/github.svg)](https://agentmods.dev/skills/tray-tecnologia/tray-api-ai-plugin/pagamentos)
Your own site
<a href="https://agentmods.dev/skills/tray-tecnologia/tray-api-ai-plugin/pagamentos"><img src="https://agentmods.dev/badge/skills/tray-tecnologia/tray-api-ai-plugin/pagamentos/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.

agentmods 80×15 button for tray-pagamentos

Your own site · 80×15
<a href="https://agentmods.dev/skills/tray-tecnologia/tray-api-ai-plugin/pagamentos"><img src="https://agentmods.dev/badge/skills/tray-tecnologia/tray-api-ai-plugin/pagamentos.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 176 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 12,029 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 13 findings, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high Tool Misuse · line 19
    Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
    Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
  • high Tool Misuse · line 416
    Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
    Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
  • high Tool Misuse · line 686
    Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
    Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
  • medium Agent Snooping · line 45
    Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
    Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
  • medium Server-Side Request Forgery · line 195
    Request target host is built from a dynamic or untrusted value. If the host is attacker-influenced, this enables SSRF to arbitrary internal or metadata endpoints.
    Fix: Do not build request URLs from untrusted input. Validate the host against an allowlist and reject internal/metadata addresses before issuing the request.
  • medium Server-Side Request Forgery · line 321
    Request target host is built from a dynamic or untrusted value. If the host is attacker-influenced, this enables SSRF to arbitrary internal or metadata endpoints.
    Fix: Do not build request URLs from untrusted input. Validate the host against an allowlist and reject internal/metadata addresses before issuing the request.
  • medium Server-Side Request Forgery · line 247
    Request target host is built from a dynamic or untrusted value. If the host is attacker-influenced, this enables SSRF to arbitrary internal or metadata endpoints.
    Fix: Do not build request URLs from untrusted input. Validate the host against an allowlist and reject internal/metadata addresses before issuing the request.
  • medium Server-Side Request Forgery · line 392
    Request target host is built from a dynamic or untrusted value. If the host is attacker-influenced, this enables SSRF to arbitrary internal or metadata endpoints.
    Fix: Do not build request URLs from untrusted input. Validate the host against an allowlist and reject internal/metadata addresses before issuing the request.
  • medium Server-Side Request Forgery · line 450
    Request target host is built from a dynamic or untrusted value. If the host is attacker-influenced, this enables SSRF to arbitrary internal or metadata endpoints.
    Fix: Do not build request URLs from untrusted input. Validate the host against an allowlist and reject internal/metadata addresses before issuing the request.
  • medium Server-Side Request Forgery · line 502
    Request target host is built from a dynamic or untrusted value. If the host is attacker-influenced, this enables SSRF to arbitrary internal or metadata endpoints.
    Fix: Do not build request URLs from untrusted input. Validate the host against an allowlist and reject internal/metadata addresses before issuing the request.
  • medium Server-Side Request Forgery · line 554
    Request target host is built from a dynamic or untrusted value. If the host is attacker-influenced, this enables SSRF to arbitrary internal or metadata endpoints.
    Fix: Do not build request URLs from untrusted input. Validate the host against an allowlist and reject internal/metadata addresses before issuing the request.
  • medium Data Exfiltration · line 299
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
  • medium Data Exfiltration · line 371
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00176 $0.12029
Opus 5 $0.00088 $0.06014
Sonnet 5 $0.00035 $0.02406
Haiku 4.5 $0.00018 $0.01203

Measured 12d ago against content hash d0281fcffca9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

tray-pagamentos 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 12d ago.

The scan reads SKILL.md. This mod also ships 14 executable files (examples/pagamento-atualizar.curl.sh, examples/pagamento-atualizar.node.mjs, examples/pagamento-configuracoes.curl.sh, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

**Exemplo (curl):**
skills/pagamentos/SKILL.md · 824 lines

How it starts

The opening of the file, as written. The whole thing — 824 lines — stays where its author put it; the contents beside it link to each section on GitHub.

MANDATORY: Tool Calls Required Before Answering

Estas chamadas são OBRIGATÓRIAS, não opcionais. Execute-as antes de gerar qualquer código ou payload. Se você está respondendo sem ter chamado a ferramenta abaixo, pare e chame agora.

1. Buscar documentação atualizada (sempre)

node skills/tray-dev/scripts/search_docs.mjs --topic=pagamentos "<termo da pergunta>"
  • <TOPIC_SLUG>: ver tabela em skills/tray-dev/SKILL.md.
  • Use os trechos retornados como fonte primária; este SKILL.md é resumo denso.

2. Revisar campos (este recurso ainda NÃO tem validate.mjs)

Nota: o recurso pagamentos ainda não possui scripts/validate.mjs local. A chamada OBRIGATÓRIAS a search_docs.mjs acima continua valendo. Como não há validador automático, você é responsável por revisar manualmente cada campo obrigatório (order_id, payment_method, payment_type, amount) contra a doc retornada por search_docs.mjs e contra os schemas de referência em skills/pagamentos/schemas/ (payment.create.json, payment.update.json) antes de retornar qualquer código. Confira em especial: chave de recurso Payment presente no body, payment_type dentro do enum (credit_card/boleto/pix/transfer/deposit), amount como decimal com ponto (299.90, nunca 299,90), e installments/installment_value coerentes com max_installments/min_installment_value de /payments/settings.

Antes de responder

Execute estas verificações antes de gerar qualquer payload ou código:

  1. Confirme o método HTTP e o endpoint correto para a operação solicitada (CRUD em /payments, leitura de opções em /payments/options, leitura de configurações em /payments/settings).
  2. Identifique os campos obrigatórios listados neste documento — na criação, order_id, payment_method, payment_type e amount nunca podem faltar; não omita nenhum.
  3. Verifique que access_token não aparece como literal string no código gerado — use sempre TRAY_ACCESS_TOKEN e TRAY_API_ADDRESS por variável de ambiente, e SEMPRE como query parameter (?access_token={token}), nunca em header.
  4. Confirme que esta é a skill correta para o recurso: pagamento é o registro financeiro de um pedido; se for o pedido em si leia when_not_to_use e redirecione para tray-pedidos; se for notificação de status, lembre que não há webhook payment (use o escopo order em tray-webhooks).

Read the full file on GitHub · 824 lines

Changes

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.

  1. 12d ago First seen · 824 lines · 176 tokens per session scan A d0281fcffca9

Subscribe to this mod's changes

tray-pagamentos is a skill published in the GitHub repository tray-tecnologia/tray-api-ai-plugin (15 stars, last pushed 1mo ago), licensed MIT. It adds 176 tokens to every session and 12,029 once invoked, about $0.0009 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-30.