data-onchain

data-onchain is an agent for Claude Code from golemfoundation/octant-council-builder. It costs 14 tokens per session (720 once invoked), scanned A, original, MIT.

A research helper that looks for public blockchain data about a project, such as where its contracts are deployed and how people use them. Blockchain data records transactions and activity on public networks.

In plain words
What is it for?
Use it to find contract addresses, supported blockchains, total value locked in DeFi projects, transactions, users, developer activity, fees, and revenue.
Why use it?
It gathers usage evidence from several public data sources instead of requiring someone to search each one manually. It also notes when a project has no blockchain component.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the council plugin — 11 skills, 10 agents shipped together

Good fit Use it to find contract addresses, supported blockchains, total value locked in DeFi projects, transactions, users, developer activity, fees, and revenue.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/golemfoundation/octant-council-builder/data-onchain
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.

Clone the repo
git clone --depth 1 https://github.com/golemfoundation/octant-council-builder

Made for: Claude Code.

Or install council, the plugin that ships this one along with the rest of its 11 skills, 10 agents.

Wrote 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.

agentmods badge for data-onchain

README.md
[![agentmods](https://agentmods.dev/badge/agents/golemfoundation/octant-council-builder/data-onchain/github.svg)](https://agentmods.dev/agents/golemfoundation/octant-council-builder/data-onchain)
Your own site
<a href="https://agentmods.dev/agents/golemfoundation/octant-council-builder/data-onchain"><img src="https://agentmods.dev/badge/agents/golemfoundation/octant-council-builder/data-onchain/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.

agentmods 80×15 button for data-onchain

Your own site · 80×15
<a href="https://agentmods.dev/agents/golemfoundation/octant-council-builder/data-onchain"><img src="https://agentmods.dev/badge/agents/golemfoundation/octant-council-builder/data-onchain.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 720 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00014 $0.00720
Opus 5 $0.00007 $0.00360
Sonnet 5 $0.00003 $0.00144
Haiku 4.5 $0.00001 $0.00072

Measured 10d ago against content hash 233f09613d06, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

data-onchain 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 10d 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.

agents/data-onchain.md · 81 lines

How it starts

The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Data Gatherer: On-Chain Activity

You are a data-gathering agent on a public goods evaluation council. Your job is to find on-chain usage data for the project being evaluated.

Input

You receive $PROJECT (a project name or URL) and $OUTPUT_DIR (where to write your findings).

Process

  1. TaskUpdate: claim your task (status="in_progress")
  2. Determine if on-chain relevant: Not all public goods have on-chain components. Infrastructure tools, research, education projects may have none — note this and still search.
  3. Search for on-chain data:
    • DefiLlama: WebSearch "$PROJECT" site:defillama.com — TVL, protocol metrics
    • Dune Analytics: WebSearch "$PROJECT" site:dune.com — dashboards with usage data
    • Block explorers: WebSearch "$PROJECT" etherscan or "$PROJECT" contract address
    • L2Beat: WebSearch "$PROJECT" site:l2beat.com — if it's an L2/rollup
    • Electric Capital: WebSearch "$PROJECT" developer report — developer metrics
  4. Extract what's available:
    • Contract addresses and chains deployed on
    • TVL (if DeFi)
    • Transaction count / unique users
    • Developer count (from Electric Capital or similar)
    • Protocol revenue / fees generated
  5. Write output: Write structured markdown to $OUTPUT_DIR/onchain.md
  6. TaskUpdate: complete task (status="completed")
  7. SendMessage: send 2-line summary to team lead

Output Format

Write $OUTPUT_DIR/onchain.md with this structure:

# On-Chain Activity: $PROJECT

**Fetched:** YYYY-MM-DD

## Deployment

| Chain | Contract | Type |
|-------|----------|------|
| Ethereum | 0x... | Core protocol |
| Optimism | 0x... | Bridge |
| ... | ... | ... |

(Write "No on-chain contracts found" if not applicable — this is valid for infrastructure/research projects)

## Usage Metrics (if available)

| Metric | Value | Source |
|--------|-------|--------|
| TVL | $X | DefiLlama |
| Monthly active users | N | Dune |
| Total transactions | N | Etherscan |
| Protocol revenue (30d) | $X | DefiLlama |

## Developer Activity (if available)

| Metric | Value | Source |
|--------|-------|--------|
| Monthly active devs | N | Electric Capital |
| Total devs (all time) | N | Electric Capital |

## Multi-chain Presence

- **Chains:** [list]
- **Primary chain:** [chain]

## Raw Notes

[Context — is this an infrastructure project with no direct on-chain presence? Is on-chain activity meaningful for what they do? Any notable on-chain events (hacks, migrations, governance votes)?]

Read the full file on GitHub · 81 lines

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.

  1. 10d ago First seen · 81 lines · 14 tokens per session scan A 233f09613d06

Subscribe to this mod's changes

data-onchain is an agent published in the GitHub repository golemfoundation/octant-council-builder (3 stars, last pushed 5mo ago), licensed MIT. It adds 14 tokens to every session and 720 once invoked, about $0.0001 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-31.

Related

Other agents, from other repositories

project-auditor

Use for /audit or when no PROJECT.md exists. Auditor + Architect hybrid — stack detection, vulnerability analysis, outdated dependency scan, architectural debt, and a concrete refactoring plan.

avelikiy/great_cto · 41 tokens

edtech-reviewer

Education-technology specialist pre-implementation reviewer for edtech archetype. Specialises in COPPA verifiable parental consent, FERPA student-data handling, GDPR-K (digital age of consent), Section 508 + WCAG 2.2 AA accessibility, child-safety content moderation (CSAM hash, NCMEC reporting), and US state…

avelikiy/great_cto · 112 tokens

adtech-privacy-reviewer

US adtech / web-tracking privacy-litigation pre-implementation reviewer. Outputs threat model TM-adtech-{slug}.md and signs off the tracking-consent gate before senior-dev claims tasks.

avelikiy/great_cto · 46 tokens

geo-routing-engineer

Geospatial and routing specialist for Product-Builder products with maps, scheduling-by-location, or vehicle routing (route-optimization in logistics, dispatch in home services, field-booking). Owns the routing contract — geocoding, the VRP/routing model (constraints, objective), maps/distance-matrix provider…

avelikiy/great_cto · 112 tokens

cms-reviewer

CMS / content-platform pre-implementation reviewer. Outputs threat model TM-{slug}.md and signs off SEO + a11y + content-policy decisions before senior-dev claims tasks.

avelikiy/great_cto · 39 tokens

senior-dev

Use to implement tasks from Beads backlog. Claims a task, implements with TDD, closes when done. Can run in parallel.

avelikiy/great_cto · 31 tokens