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/elisymlabs/elisymWrote 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/elisymlabs/elisym/plugin)<a href="https://agentmods.dev/plugins/elisymlabs/elisym/plugin"><img src="https://agentmods.dev/badge/plugins/elisymlabs/elisym/plugin/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/elisymlabs/elisym/plugin"><img src="https://agentmods.dev/badge/plugins/elisymlabs/elisym/plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
elisym 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": "elisym",
"description": "Discover, hire, and pay AI agents on the Nostr-based elisym marketplace - no platform, no middleman",
"version": "0.1.0",
"author": {
"name": "elisym labs"
},
"homepage": "https://www.elisym.network",
"repository": "https://github.com/elisymlabs/elisym",
"license": "MIT"
}
What it installs
The manifest is a name and a version. 1 command, 1 MCP server travel with it, and installing the plugin installs all of them — 13 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 · 12 lines scan A b27c3b6c40d5
elisym is a plugin published in the GitHub repository elisymlabs/elisym (18 stars, last pushed yesterday), 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-30.
Other plugins, from other repositories
uniswap-cca
Configure and deploy Continuous Clearing Auction (CCA) smart contracts for token distribution.
pandects
Executable credit laws with broken specimens and reduced counterexamples.
aerodrome-amm-plugin
Swap tokens and provide liquidity on Aerodrome AMM (volatile/stable pools) on Base.
radius-dev
Radius Network development tools — blockchain development playbook, x402 HTTP micropayments, and testnet faucet.
dexpaprika
Access comprehensive DeFi data from DexPaprika: DEXes, liquidity pools, tokens, and trading across 36 blockchains. No API key needed to start.
decipher-gas-optimizoor
Analyzes Solidity smart contracts for gas inefficiencies. Detects storage packing gaps, loop anti-patterns, custom error opportunities, visibility mismatches, unchecked arithmetic, calldata vs memory decisions, and deployment cost issues. Enforces gas regression detection on every file save via forge integration.