agentmods.dev

mp-test-setup

mp-test-setup is a skill for Claude Code from mercadopago/mercadopago-claude-marketplace. It costs 75 tokens per session (2,530 once invoked), scanned A, original, Apache-2.0.

A helper for creating Mercado Pago test users and adding test money to their accounts. Mercado Pago is a payments platform, and its test environment uses different credential types for different APIs.

In plain words
What is it for?
Use it during payment integration setup to confirm account and credential readiness, create test users, and fund them for end-to-end tests.
Why use it?
It reduces confusion about which test credentials and dashboard steps are needed before testing a payment integration.

Skill for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable. Also seen: names the AskUserQuestion tool; mentions Claude Code.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the mercadopago plugin — 4 skills, 4 commands, 1 agent, 2 hooks, 1 MCP server shipped together

not rated 26repo 8d ago A scan 75 tokens original Apache-2.0

Good fit Use it during payment integration setup to confirm account and credential readiness, create test users, and fund them for end-to-end tests.

Compare 6 skills from other repositories ↓
View source ↗ mercadopago/mercadopago-claude-marketplace
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add mercadopago/mercadopago-claude-marketplace
Claude Code
/plugin install mercadopago

Made for: Claude Code.

Or install mercadopago, the plugin that ships this one along with the rest of its 4 skills, 4 commands, 1 agent, 2 hooks, 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 mp-test-setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/mercadopago/mercadopago-claude-marketplace/mp-test-setup/github.svg)](https://agentmods.dev/skills/mercadopago/mercadopago-claude-marketplace/mp-test-setup)
Your own site
<a href="https://agentmods.dev/skills/mercadopago/mercadopago-claude-marketplace/mp-test-setup"><img src="https://agentmods.dev/badge/skills/mercadopago/mercadopago-claude-marketplace/mp-test-setup/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 mp-test-setup

Your own site · 80×15
<a href="https://agentmods.dev/skills/mercadopago/mercadopago-claude-marketplace/mp-test-setup"><img src="https://agentmods.dev/badge/skills/mercadopago/mercadopago-claude-marketplace/mp-test-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 75 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,530 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.00075 $0.02530
Opus 5 $0.00037 $0.01265
Sonnet 5 $0.00015 $0.00506
Haiku 4.5 $0.00007 $0.00253

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

Security

Grade A, and why

mp-test-setup 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 12d 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.

plugins/mercadopago/skills/mp-test-setup/SKILL.md · 184 lines

How it starts

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

mp-test-setup

This skill is the only place test users get created. It exists because the testing model is a frequent source of confusion — there are two distinct types of test credentials with different prefixes.

Pre-check — confirm readiness before creating test users

You are at step 4 of 7 in the integration journey: 1. Create app · 2. Get TEST creds · 3. Scaffold · 4. Create test user ← here · 5. E2E · 6. /mp-review · 7. Prod

Before creating test users, confirm the basics via AskUserQuestion (up to 3 questions — skip any already in .mp-integrate-progress.md):

  1. Account — Skip if already confirmed in .mp-integrate-progress.md. Otherwise: "Do you have a Mercado Pago developer account?" → Yes / No
  2. Credentials — "Do you have your APP_USR- access token?" → Yes / No
  3. Credential type — "Are you using TEST credentials — from the {test_tab}?" → Yes, test credentials / No, production credentials / I don't know

  • No account → point to the dashboard for the country (Chile: https://www.mercadopago.cl/developers — no .com; others https://www.mercadopago.com.{cc}/developers).

  • No credentials → if the developer chooses to import them: apply the on-demand procedure in Step 0 immediately before application_list, ask via AskUserQuestion "Which app do you want to use?", then call mcp__plugin_mercadopago_mcp__get_credentials with the chosen application_id and display credentials inline. Never write to file or commit. Manual dashboard guidance requires no MCP.

  • Credential type — No, production credentials OR I don't know → show this BLOCKING WARNING and do NOT create a test user:

    ⛔ WARNING — Production credentials detected A real card charge may occur if you test against production. Switch to the {test_tab} tab in the Developer Dashboard first. 👉 https://{DOMAIN}/developers/panel/app → Credentials → {test_tab} tab

    Re-show question 3 until the developer confirms "Yes, test credentials". This gate has no Skip option — do not proceed to Step 2 (test user creation) otherwise.

Read the full file on GitHub · 184 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 · 184 lines · 75 tokens per session scan A 64f02bed4842

Subscribe to this mod's changes

mp-test-setup is a skill published in the GitHub repository mercadopago/mercadopago-claude-marketplace (26 stars, last pushed 8d ago), licensed Apache-2.0. It adds 75 tokens to every session and 2,530 once invoked, about $0.0004 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.

Testing
Related

Other skills, from other repositories

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

neuron-evaluation-engineer

Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…

neuron-core/neuron-ai · 77 tokens

jetson-validate-image

Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.

NVIDIA/skills · 50 tokens

atmos-validation

Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.

cloudposse/atmos · 31 tokens

skill-benchmark

Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.

HoangNguyen0403/agent-skills-standard · 16 tokens