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.
npx skills add hive-intel/hive-sdk --skill hive-security-riskgit clone --depth 1 https://github.com/hive-intel/hive-sdkWrote 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/skills/hive-intel/hive-sdk/hive-security-risk)<a href="https://agentmods.dev/skills/hive-intel/hive-sdk/hive-security-risk"><img src="https://agentmods.dev/badge/skills/hive-intel/hive-sdk/hive-security-risk.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00103 | $0.01363 |
| Opus 5 | $0.00051 | $0.00681 |
| Sonnet 5 | $0.00021 | $0.00273 |
| Haiku 4.5 | $0.00010 | $0.00136 |
Grade A, and why
hive-security-risk 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
hive-security-risk — Security Risk
Assess transaction-time risk — tokens, addresses, approvals, dApps, phishing, simulations — and report severity, evidence, and remediation. Wrong "looks fine" answers here cost users real money, so never conclude safety without a tool-backed check.
Task toolset and identifiers
Toolset: security_risk. Read hive://toolsets/security_risk before
execution; it is authoritative for the current output schema, material-call
budget, phases, fallback condition, and stop conditions.
Required identifiers depend on the risk object: chain plus token contract, wallet address, spender, dApp URL, or transaction payload. Never invent a spender, owner, calldata, or URL — ask for whatever is missing.
Before choosing endpoints, select exactly one matching entry from the exact workflow's routes[]. Follow its ordered steps, use a fallback only under that step's published condition, stop at four material calls, and preserve the selected route_id in the typed result. The broad coverageCatalog is discovery coverage, not an execution plan.
Procedure
- Identify the risk object: token, address, approval, dApp, contract, or transaction payload.
- Call
search_toolsfor the matching security/risk capabilities. - Call
get_api_endpoint_schemafor each endpoint before calling it. - Run the narrowest risk check first; add simulation or approval analysis only when the required payload/owner details exist.
- For Solana, send only the base64 serialized transaction to the GoPlus pre-execution check. Never ask for or forward signing secrets.
- Report severity, evidence, and remediation steps.
- Do not provide signing guidance while a critical risk is unresolved.
Bounded calls
- Keep risk checks scoped to the provided contract, address, or payload.
- Avoid broad scans unless the user explicitly asks for an audit.
- Use severity and evidence rather than unsupported certainty.
Worked example
User: "A dApp wants unlimited approval of my USDC (0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48) on Ethereum to spender 0x… — should I sign?"
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.
- 8d ago First seen · 134 lines · 103 tokens per session scan A eb7a434b270d
hive-security-risk is a skill published in the GitHub repository hive-intel/hive-sdk (18 stars, last pushed yesterday), licensed MIT. It adds 103 tokens to every session and 1,363 once invoked, about $0.0005 per session on Opus 5. 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 skills, from other repositories
palisade-security-scanner
Onchain security scanner on Robinhood Chain — scan token approvals, detect honeypots, analyze contracts for rugpull indicators, check liquidity locks, and score contract safety. Use when a user asks an agent to evaluate, scan, or check a token or wallet before trading, swapping, signing an approval, or investing. 18…
pump-swarm
Coordinated multi-wallet trading on Pump.fun.
trading-solana
Trade tokens on Solana DEXes - Jupiter, Raydium, Orca, Meteora, Pump.fun.
public
For agents: This document explains how to integrate with Clodds APIs.
copy-trading
Automatically copy trades from successful wallets on Polymarket and crypto.
trading-evm
Trade tokens on EVM chains - Uniswap V3, 1inch on Ethereum, Arbitrum, Optimism, Base, Polygon.