position-manager-skill marketplace

Install

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.

Security

Grade A, and why

position-manager-skill marketplace 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 2d 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.

.claude-plugin/marketplace.json · 31 lines

What it actually says

{
  "name": "position-manager-skill",
  "owner": {
    "name": "Alexandre Bandarra"
  },
  "homepage": "https://github.com/solanabr/position-manager-skill",
  "metadata": {
    "upstream": "solanabr/position-manager-skill (seed; LICENSE retained)"
  },
  "plugins": [
    {
      "name": "position-manager-skill",
      "source": "./",
      "description": "CLMM/LP lifecycle command center: realtime gRPC/websocket out-of-range alerts, IL-vs-HODL + fee-APR backtesting, cross-DEX yield routing, simulate-first human-confirm rebalance, and tax-lot ledger across Orca Whirlpools, Raydium CLMM, Meteora DLMM/DAMM v2, and Kamino vaults.",
      "version": "0.1.0",
      "license": "MIT",
      "keywords": [
        "clmm",
        "liquidity",
        "solana",
        "orca",
        "raydium",
        "meteora",
        "kamino",
        "defi",
        "rebalance"
      ]
    }
  ]
}

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.

Related

Other plugins, from other repositories