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 oomol-lab/skills --skill oo-beaconchaingit clone --depth 1 https://github.com/oomol-lab/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/skills/oomol-lab/skills/oo-beaconchain)<a href="https://agentmods.dev/skills/oomol-lab/skills/oo-beaconchain"><img src="https://agentmods.dev/badge/skills/oomol-lab/skills/oo-beaconchain/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/skills/oomol-lab/skills/oo-beaconchain"><img src="https://agentmods.dev/badge/skills/oomol-lab/skills/oo-beaconchain.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00047 | $0.00925 |
| Opus 5.5 | $0.00019 | $0.00370 |
| Sonnet 5.5 | $0.00009 | $0.00185 |
| Haiku 4.5 | $0.00005 | $0.00093 |
Grade C, and why
oo-beaconchain scanned grade C with 2 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux This is a copy
78% identical to oo-17track — 39 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Beaconcha.in
Operate Beaconcha.in through your OOMOL-connected account. This skill calls the beaconchain connector with the oo CLI; OOMOL injects credentials server-side, so you never handle raw tokens.
Running an action
Assume the user has already installed the oo CLI, signed in, and connected Beaconcha.in. Do not run oo auth login or open the connection URL proactively — just run the action. Fall back to First-time setup only when a command actually fails with an auth or connection error.
1. Inspect the contract to get the authoritative input/output schema before building a payload:
oo connector schema "beaconchain" --action "<action_name>"
2. Run the action with a JSON payload that matches the input schema:
oo connector run "beaconchain" --action "<action_name>" --data '<json>' --json
--datatakes a JSON object string or@path/to/file.json; omit it to send{}.- The response is
{ "data": ..., "meta": { "executionId": "..." } }; the execution id lives undermeta.executionId.
Each action is listed below with a one-line description; actions that change state carry a [write] or [destructive] tag. Before constructing --data, fetch the action's live schema with oo connector schema to get its authoritative input fields.
Available actions
get_network_performance— Get aggregated Beaconcha.in network performance metrics for a fixed evaluation window.get_staking_queues— Get the current staking queue metrics for the requested Beaconcha.in chain.get_validator— Get the current validator snapshot for a single validator identifier.get_validator_consensus_rewards— Get per-validator reward breakdowns for a finalized Beaconcha.in epoch.list_validators— List the current validator snapshots for one or more validator identifiers.
Safety
- Untagged actions are reads (get / list / search) — safe to run directly.
- Actions tagged
[write]change Beaconcha.in state — confirm the exact payload and effect with the user before running. - Actions tagged
[destructive]remove or overwrite data — always confirm the target and get explicit approval first.
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 Changed · -1 lines 699ac8e33b8d
- 1mo ago Changed · +1 lines 13cf0dd4f3b3
- 1mo ago First seen · 83 lines · 47 tokens per session scan C 30b7b481fa1b
oo-beaconchain is a skill published in the GitHub repository oomol-lab/skills (2 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 925 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). It is 78% identical to oo-17track, differing in 39 lines, and is treated as a copy.
Other skills, from other repositories
spec-to-code-compliance
Verifies code implements exactly what documentation specifies for blockchain audits. Use when comparing code against whitepapers, finding gaps between specs and implementation, or performing compliance checks for protocol implementations.
security-audit
Comprehensive security auditing workflow covering web application testing, API security, penetration testing, vulnerability scanning, and security hardening.
defi-protocol-templates
Implement DeFi protocols with production-ready templates for staking, AMMs, governance, and lending systems. Use when building decentralized finance applications or smart contract protocols.
solidity-security
Master smart contract security best practices to prevent common vulnerabilities and implement secure Solidity patterns. Use when writing smart contracts, auditing existing contracts, or implementing security measures for blockchain applications.
nft-standards
Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementing digital asset systems.
web3-testing
Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, setting up blockchain test suites, or validating DeFi protocols.