regen-compute: Instructions file for Claude Code

CLAUDE.md

regen-compute CLAUDE.md is an instructions file for Claude Code from regen-network/regen-compute. It costs 2,124 tokens per session, scanned A, original, Apache-2.0.

Project instructions for Regen Compute, an MCP server that connects AI-computing usage with verified ecological credit retirement on Regen Network. They describe the project’s purpose, technology, structure, and data sources.

In plain words
What is it for?
Use them when developing or reviewing Regen Compute, including its TypeScript and Node.js code, MCP integration, Regen Ledger and Indexer connections, ecological-footprint estimates, credit browsing, and credit retirement.
Why use it?
They give an AI coding assistant the context needed to work consistently on the project and accurately describe it as funding ecological regeneration rather than claiming carbon neutrality.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md; mentions Claude Code.

This is regen-network/regen-compute's own configuration. It tells Claude Code how to work on regen-compute itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything regen-compute configures →

Reuse

Borrowing it

Nothing to install: this file belongs to regen-network/regen-compute. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/regen-network/regen-compute/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/regen-network/regen-compute

Made for: Claude Code.

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 regen-compute CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/regen-network/regen-compute/claude-md/github.svg)](https://agentmods.dev/instructions/regen-network/regen-compute/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/regen-network/regen-compute/claude-md"><img src="https://agentmods.dev/badge/instructions/regen-network/regen-compute/claude-md/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 regen-compute CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/regen-network/regen-compute/claude-md"><img src="https://agentmods.dev/badge/instructions/regen-network/regen-compute/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,124 This file is loaded in full into every session.
When invoked 2,124 The same file — it is already loaded in full.
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.02124 $0.02124
Opus 5.5 $0.00850 $0.00850
Sonnet 5.5 $0.00425 $0.00425
Haiku 4.5 $0.00212 $0.00212

Measured 2mo ago against content hash 226ed6b3715a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

regen-compute CLAUDE.md 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 2mo 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.

CLAUDE.md · 134 lines

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.

CLAUDE.md — Regen Compute

This file provides context to Claude Code when working on this project.

Project Overview

Regen Compute is an MCP (Model Context Protocol) server that connects AI compute usage to verified ecological credit retirement on Regen Network. The product name is Regen Compute; the category it creates is Regenerative AI. Users connect it to Claude Code or Cursor, and it provides tools to estimate their AI session's ecological footprint, browse available credits, and retire them via Regen Marketplace's existing credit card flow.

Framing

  • This is "regenerative contribution," NOT "carbon offset." We fund verified ecological regeneration. We do not claim carbon neutrality.
  • Live sell order data served dynamically from Regen Ledger. Credit card purchases available via Regen Marketplace. Retirement certificates verifiable on-chain.

Tech Stack

  • Language: TypeScript (ES2022, ESM modules)
  • Runtime: Node.js >= 20
  • MCP SDK: @modelcontextprotocol/sdk
  • Data sources:
    • Regen Ledger REST API (credit classes, projects, batches, sell orders)
    • Regen Indexer GraphQL (api.regen.network/indexer/v1/graphql) — retirement certificates, aggregations
    • Regen Marketplace (app.regen.network) — purchase flow links
    • ecoBridge API (api.bridge.eco) — cross-chain token support, real-time prices, widget deep links

Project Structure

src/
├── index.ts              # MCP server entry point, tool/prompt registration, server instructions
├── config.ts             # Centralized env config, isWalletConfigured() gate
├── tools/
│   ├── footprint.ts      # estimate_session_footprint tool
│   ├── credits.ts        # browse_available_credits tool (live sell order aggregation)
│   ├── certificates.ts   # get_retirement_certificate tool (nodeId + txHash lookup)
│   ├── impact.ts         # get_impact_summary tool
│   └── retire.ts         # retire_credits tool (on-chain execution OR marketplace link)
├── services/
│   ├── ledger.ts         # Regen Ledger REST client (lcd-regen.keplr.app)
│   ├── indexer.ts        # Regen Indexer GraphQL client (api.regen.network)
│   ├── estimator.ts      # Footprint estimation heuristics
│   ├── wallet.ts         # Cosmos wallet init, sign+broadcast (singleton)
│   ├── order-selector.ts # Best-price sell order routing (cheapest-first fill)
│   ├── ecobridge.ts      # ecoBridge API client (registry, tokens, chains, widget URLs)
│   └── payment/
│       ├── types.ts      # PaymentProvider interface (authorize → capture two-phase)
│       ├── crypto.ts     # CryptoPaymentProvider (balance check, no-op capture)
│       └── stripe-stub.ts # Placeholder for Regen team Stripe integration

Read the full file on GitHub · 134 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. 2mo ago First seen · 134 lines · 2,124 tokens per session scan A 226ed6b3715a

Subscribe to this mod's changes

regen-compute CLAUDE.md is an instructions file published in the GitHub repository regen-network/regen-compute (4 stars, last pushed 21d ago), licensed Apache-2.0. It adds 2,124 tokens to every session, about $0.0085 per session on Opus 5.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 instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,461 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,750 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,261 tokens