Borrowing it
Nothing to install: this file belongs to helius-labs/core-ai. 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/helius-labs/core-ai/main/CLAUDE.mdgit clone --depth 1 https://github.com/helius-labs/core-aiWrote 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/helius-labs/core-ai/claude-md)<a href="https://agentmods.dev/instructions/helius-labs/core-ai/claude-md"><img src="https://agentmods.dev/badge/instructions/helius-labs/core-ai/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.01334 | $0.01334 |
| Opus 5 | $0.00667 | $0.00667 |
| Sonnet 5 | $0.00267 | $0.00267 |
| Haiku 4.5 | $0.00133 | $0.00133 |
Grade A, and why
core-ai 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 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Core AI
Monorepo containing Helius developer tools distributed as independent packages:
helius-mcp/— MCP server (npm:helius-mcp) — AI-assistant agnostichelius-skills/— Standalone Claude Code skill (installed viainstall.sh)helius-plugin/— Claude Code plugin (all-in-one: bundles skill + auto-starts MCP)helius-cursor/— Cursor plugin (all-in-one: bundles skill + auto-starts MCP)helius-cli/— CLI for account setup (npm:helius-cli)
Compiler-managed sync
The compiler (npx tsx scripts/compile-skills.ts) is the source of truth for everything generated from helius-skills/. It writes:
helius-skills/<skill>/SKILL.mdfrontmatter version (re-injected fromversions.json) and everyhelius-mcp@<version>mention in the body.agents/skills/<skill>/— Codex-native SKILL.md + 3 prompt variants (openai.developer.md,claude.system.md,full.md)helius-mcp/system-prompts/<skill>/— same prompt variants, npm-shippedhelius-plugin/skills/<dir>/references/andhelius-plugin/skills/<dir>/SKILL.md(refs bytewise from canonical; SKILL.md gets version re-injected)helius-cursor/skills/<dir>/references/andhelius-cursor/skills/<dir>/SKILL.md(same)helius-plugin/.mcp.jsonandhelius-cursor/.mcp.json— generated from thehelius-mcppin inversions.jsonhelius-skills/<skill>/references/*.mdandhelius-skills/<skill>/install.sh— thehelius-mcp@<version>token only
Run npx tsx scripts/compile-skills.ts after any change in helius-skills/. CI runs --check mode and fails on drift.
Reference files are byte-identical across all destinations — never hand-edit helius-plugin/ or helius-cursor/ references; only edit the canonical copy in helius-skills/<skill>/references/.
SKILL.md bodies in helius-plugin/ and helius-cursor/ are intentionally not identical to canonical (different MCP prerequisite messaging, condensed router surface section). They are hand-managed in those packages. Only the frontmatter version and the helius-mcp@<version> token are auto-synced from versions.json.
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 · 69 lines · 1,334 tokens per session scan A 9c8f172ffeaa
core-ai CLAUDE.md is an instructions file published in the GitHub repository helius-labs/core-ai (26 stars, last pushed 4d ago), licensed MIT. It adds 1,334 tokens to every session, about $0.0067 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 instructions, from other repositories
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).
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.
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.
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).
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.