Borrowing it
Nothing to install: this file belongs to hiero-ledger/solo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/hiero-ledger/solo/main/CLAUDE.mdgit clone --depth 1 https://github.com/hiero-ledger/soloWrote 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/instructions/hiero-ledger/solo/claude-md)<a href="https://agentmods.dev/instructions/hiero-ledger/solo/claude-md"><img src="https://agentmods.dev/badge/instructions/hiero-ledger/solo/claude-md.svg" alt="Measured on agentmods" 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.03627 | $0.03627 |
| Opus 5 | $0.01813 | $0.01813 |
| Sonnet 5 | $0.00725 | $0.00725 |
| Haiku 4.5 | $0.00363 | $0.00363 |
Grade A, and why
solo 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 5d 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 — 326 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
Solo (@hiero-ledger/solo) is a CLI tool for deploying and managing private Hedera Networks on Kubernetes. It orchestrates consensus nodes, mirror nodes, block explorers, and JSON-RPC relays via Helm charts and Kubernetes APIs.
- Language: TypeScript (ES2022, ESM)
- Runtime: Node.js >= 22.0.0
- CLI Framework: Yargs with Listr2 for task execution
Common Commands
All task commands use Task (task):
# Install dependencies
npm install
# Build (compile TypeScript + lint)
task build
# Compile only
task build:compile
# Run unit tests with coverage
task test
# Auto-fix lint/formatting issues (run before committing)
task format
# List all available tasks including E2E tests
task --list-all
# Run a specific E2E test suite
task test-e2e-integration
task test-e2e-standard
# Run solo via tsx (development mode, without building)
npm run solo-test -- <COMMAND> <ARGS>
To run a single unit test file directly:
npx mocha 'test/unit/path/to/test.ts'
Logs are written to $HOME/.solo/logs/solo.log. Tail with: tail -f $HOME/.solo/logs/solo.log | jq
Architecture
The codebase follows a layered, command-driven architecture with dependency injection (tsyringe-neo):
Entry point: solo.ts → ArgumentProcessor (Yargs) → Command Layer
Layer Overview
-
src/commands/— 14 CLI commands (account, deployment, network, node, cluster, block-node, explorer, mirror-node, relay, one-shot, backup-restore, rapid-fire, file). Each command extendsBaseCommandand implements command-specific workflows. -
src/core/— ~95 services:account-manager.ts,config-manager.ts,chart-manager.ts,key-manager.ts,lock/(distributed leases),logging/(Pino),dependency-managers/(installation checks and dynamic command loading). -
src/integration/— External system clients:kubernetes/(K8s API wrapper),helm/(Helm chart execution),kind/(cluster provisioning),git/,npm/.
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.
- 5d ago First seen · 326 lines · 3,627 tokens per session scan A e102e48cfe4e
solo CLAUDE.md is an instructions file published in the GitHub repository hiero-ledger/solo (43 stars, last pushed yesterday), licensed Apache-2.0. It adds 3,627 tokens to every session, about $0.0181 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-09-01.
Other instructions, from other repositories
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.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
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.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.