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.
/plugin marketplace add airwallex/airwallex-marketplacenpx agentmods add plugins/airwallex/airwallex-marketplace/airwallex-devgit clone --depth 1 https://github.com/airwallex/airwallex-marketplaceWrote 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/airwallex/airwallex-marketplace/airwallex-dev)<a href="https://agentmods.dev/plugins/airwallex/airwallex-marketplace/airwallex-dev"><img src="https://agentmods.dev/badge/plugins/airwallex/airwallex-marketplace/airwallex-dev.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
airwallex-dev 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 4d 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.
What it actually says
{
"name": "airwallex-dev",
"description": "Airwallex integration skills for Claude. Code-generation workflows that scaffold, configure, and wire Airwallex APIs into your project.",
"version": "0.1.0",
"author": {
"name": "Airwallex",
"url": "https://www.airwallex.com"
},
"homepage": "https://www.airwallex.com/docs",
"repository": "https://github.com/airwallex/airwallex-marketplace.git",
"license": "Apache-2.0",
"keywords": [
"airwallex",
"integration",
"developer",
"sdk",
"code-generation",
"payments",
"checkout"
]
}
What it installs
The manifest is a name and a version. 6 skills travel with it, and installing the plugin installs all of them — 573 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 4d ago First seen · 22 lines scan A fb1375bc4ae3
airwallex-dev is a plugin published in the GitHub repository airwallex/airwallex-marketplace (5 stars, last pushed 10d ago), licensed Apache-2.0. 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-08-30.
Other plugins, from other repositories
shopware-documentation
Documentation-surface structuring for Shopware repositories. Size budgets, one subject per file, splitting oversized surfaces into docs/ siblings, and cross-reference integrity, backed by a measurement script.
claude-ops
Claude Code operations toolkit. Twelve skills: audit-skill-visibility (audit whether each installed skill is actually VISIBLE to the model, and diagnose why most of a fleet never gets used — a skill is invisible when its description is dropped by Claude Code's skill-listing context budget, which sheds descriptions…
autonomy
Governed autonomous agent operation: role-topology, binding-seam, wiring-vs-advisor, telemetry, return-accounting, trigger-dispatch, per-work-class guardrail-matrix, standing-routine-catalog, and design-only runner-charter contracts for climbing the AI-adoption ladder, plus a guided-setup skill that discovers an…
context-budget
Measure a Claude Code session's fixed startup context payload per item, on the consumer's machine at a pinned, version-stamped binary — including per-tool attribution of the built-in tool pools that /context reports only as lump sums, derived live by A/B bare-name-deny differencing with enforced comparability rules…
computer-use
Operating knowledge for Claude Code's built-in computer-use MCP server — the desktop screen-control surface. /computer-use:diagnose resolves a symptom to a cause instead of retrying: why every screenshot is downscaled to a fixed pixel budget and why zoom (not a bigger display) is the way back to detail, how to read a.
coupling
Iteratively reduces coupling in any repository at any altitude — documents, code modules, applications, or repositories: scans for change-transmitting dependencies typed against a coupling model (strength ladder, connascence, volatility weighting), verifies every finding, applies a budgeted batch of safe…