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/radiustechsystems/skillsWrote 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/radiustechsystems/skills/radius)<a href="https://agentmods.dev/plugins/radiustechsystems/skills/radius"><img src="https://agentmods.dev/badge/plugins/radiustechsystems/skills/radius/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/radiustechsystems/skills/radius"><img src="https://agentmods.dev/badge/plugins/radiustechsystems/skills/radius.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
radius-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 1mo 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": "radius-dev",
"description": "Radius Network development tools — blockchain development playbook, x402 HTTP micropayments, and testnet faucet",
"author": {
"name": "Radius Technology Systems"
}
}
What it installs
The manifest is a name and a version. 3 skills travel with it, and installing the plugin installs all of them — 378 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.
- 1mo ago First seen · 8 lines scan A d86ad5ac8941
radius-dev is a plugin published in the GitHub repository radiustechsystems/skills (2 stars, last pushed 18d 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-08-31.
Other plugins, from other repositories
kryptogo-pay
A plugin package for connecting applications to KryptoGO Payment, a stablecoin payment service, including payment collection and transaction operations.
yield-xyz-agentkit-builder
Build applications that integrate the Yield.xyz API — generate integration code for DeFi yield across 80+ networks.
yield-xyz-agentkit-moonpay
The MoonPay connector — sign and broadcast Yield.xyz transactions via MoonPay. Builds on the yield-xyz-agentkit base plugin.
newebpay
A plugin for connecting software to NewebPay, a Taiwanese payment service. It covers payment processing, transaction checks, and refunds.
external-call-safety
Detects unsafe external call patterns and token integration vulnerabilities in smart contracts. Covers unchecked call return values, fee-on-transfer tokens, rebasing tokens, missing ERC20 return values (USDT), ERC-777 callback risks, unsafe approve patterns, return data bombs, and pull vs push payment analysis.…
input-arithmetic-safety
Detects input validation failures and arithmetic vulnerabilities in smart contracts — the #1 direct exploitation cause at 34.6% of cases. Covers missing zero-checks, precision loss from division-before-multiplication, rounding direction exploitation, ERC4626 inflation attacks, unsafe casting, dust amount exploitation.