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/ihint/merchant-contextWrote 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/plugins/ihint/merchant-context/gemini-cli)<a href="https://agentmods.dev/plugins/ihint/merchant-context/gemini-cli"><img src="https://agentmods.dev/badge/plugins/ihint/merchant-context/gemini-cli/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/plugins/ihint/merchant-context/gemini-cli"><img src="https://agentmods.dev/badge/plugins/ihint/merchant-context/gemini-cli.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
merchant-context 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 yesterday.
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.
What it actually says
{
"name": "merchant-context",
"version": "0.3.0",
"description": "Resolve sourced merchant facts before agent commerce actions",
"mcpServers": {
"merchant-context": {
"httpUrl": "https://api.merchant.atomandbits.com/mcp",
"includeTools": [
"resolve_merchant",
"search_merchants",
"compare_offers",
"get_safe_actions",
"preflight"
],
"timeout": 10000
}
},
"contextFileName": "GEMINI.md"
}
What ships with it
3 files beside gemini-extension.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 20 lines scan A 623c02bec520
merchant-context is a plugin published in the GitHub repository ihint/merchant-context (0 stars, last pushed 2d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-09-08.
Other plugins, from other repositories
samedaydesk-extract
Self-contained Claude Code plugin that binds the canonical SameDayDesk MCP, one web-extract skill for single-page GET or bounded 1–5 URL batch POST, and one offline explicit-record skill. Unpaid discovery only. Mapping does not fetch or pay. No wallet, no second paywall, no installer.
internet-court
Entry point for Internet Court — the trust layer for agent-to-agent commerce. Use whenever an agent needs to transact with another agent or a paid service, or a user mentions agent payments, paid APIs (HTTP 402/x402), wallet custody or trust concerns, spending mandates, delegated permissions (ERC-7710/7715), escrow…
medusa-cloud
Skills for managing Medusa Cloud resources through the Cloud CLI (mcloud). Covers setup, deployments, debugging, local build reproduction, environment variable management, environment management, organizations, projects, logs, and authentication.
ecommerce-storefront
Comprehensive skills for building ecommerce storefronts with best practices for UI/UX, SEO, and mobile responsiveness.
learn-medusa
Interactive guided tutorial for learning Medusa development. Teaches you to build custom features step-by-step with a brands example.
medusa-dev
Comprehensive skills for building Medusa applications: backend (modules, workflows, API routes), admin UI (widgets, forms, tables), and storefronts (SDK integration, React Query).