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-network-infrastructuregit 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-network-infrastructure)<a href="https://agentmods.dev/skills/hive-intel/hive-sdk/hive-network-infrastructure"><img src="https://agentmods.dev/badge/skills/hive-intel/hive-sdk/hive-network-infrastructure.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.00081 | $0.01210 |
| Opus 5 | $0.00041 | $0.00605 |
| Sonnet 5 | $0.00016 | $0.00242 |
| Haiku 4.5 | $0.00008 | $0.00121 |
Grade A, and why
hive-network-infrastructure 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 7d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
hive-network-infrastructure — Network Infrastructure
Read chain state — gas, blocks, receipts, logs, transaction status, supported networks — and run RPC diagnostics with auditable, timestamped evidence.
Task toolset and identifiers
Toolset: network_infrastructure. Read
hive://toolsets/network_infrastructure before execution; it is authoritative
for the current output schema, material-call budget, phases, fallback
condition, and stop conditions.
- Required: chain/network.
- Optional: block number/hash, transaction hash, contract address, log filter, account address, time window.
Ask for the exact chain plus transaction/block identifiers before status checks — a transaction hash is not globally unique without chain context.
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
- Confirm the chain/network id.
- Use
filter_networkswhen comparing chains by current liquidity, transactions, or volume. Otherwise callsearch_toolsfor gas, block, transaction, receipt, log, supported-network, or RPC-diagnostic capabilities. - Call
get_api_endpoint_schemafor each endpoint before calling it. - Use current-state tools for gas and block questions; use transaction/receipt/log tools only with exact identifiers.
- Report the block/slot/fetched time so the answer is auditable.
Bounded calls
- Bound log queries by block range and topics.
- Do not run broad chain scans for a single transaction question.
- Retry transient RPC failures once when appropriate.
Worked example
User: "Did my transaction go through? Hash is 0x… — I think it was on Base."
- Confirm the chain (Base) and the exact hash.
search_tools→{"query": "transaction receipt status base", "limit": 5}get_api_endpoint_schemafor the receipt/status endpoint returned, theninvoke_api_endpointwith schema-valid arguments.- Report status, block number, gas used, and the fetched time. If the receipt is missing, say whether that means pending, dropped, or wrong chain — do not guess success.
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.
- 7d ago First seen · 130 lines · 81 tokens per session scan A 1ec12274d044
hive-network-infrastructure is a skill published in the GitHub repository hive-intel/hive-sdk (18 stars, last pushed 4d ago), licensed MIT. It adds 81 tokens to every session and 1,210 once invoked, about $0.0004 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
aomi-build
Scaffold new Aomi apps and plugins from API docs, OpenAPI/Swagger specs, or SDK references. aomi-build generates production-ready Rust SDK crates (lib.rs, client.rs, tool.rs) with tool schemas, preambles, host-interop flows, and validation — turning a vendor's API surface into AI-agent-callable tools. It covers the…
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…
emblem-ai
One-shot user management for apps, multi-chain wallet authentication, an AI-powered assistant, and AI app introspection. Use when the user wants to let website users sign in with wallets, email/password, or social login and give each user a wallet-enabled account, then embed EmblemAI chat surfaces, connect plugins, or…
add-tool
Scaffold a new MCP tool definition. Use when the user asks to add a tool, create a new tool, or implement a new capability for the server.
api-context
Canonical reference for the unified Context object passed to every tool and resource handler in @cyanheads/mcp-ts-core. Covers the full interface, its RequestContext base, all sub-APIs (ctx.log, ctx.state, ctx.requestInput, ctx.inputs, ctx.enrich, ctx.content), and when to use each.
api-errors
McpError constructor, JsonRpcErrorCode reference, and error handling patterns for @cyanheads/mcp-ts-core. Use when looking up error codes, understanding where errors should be thrown vs. caught, or using ErrorHandler.tryCatch in services.