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 agentmods add instructions/sanchez314c/agent-nero/claude-mdgit clone --depth 1 https://github.com/sanchez314c/agent-neroWrote 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/sanchez314c/agent-nero/claude-md)<a href="https://agentmods.dev/instructions/sanchez314c/agent-nero/claude-md"><img src="https://agentmods.dev/badge/instructions/sanchez314c/agent-nero/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 | $0.00822 | $0.00822 |
| Opus 5 | $0.00411 | $0.00411 |
| Sonnet 5 | $0.00164 | $0.00164 |
| Haiku 4.5 | $0.00082 | $0.00082 |
Grade C, and why
agent-nero CLAUDE.md scanned grade C with 1 finding 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 2d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- Destructive shell commands are blocked (rm -rf /, mkfs, dd if=, fork bombs). How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — Agent NERO
Project-specific instructions for Claude Code sessions working on this codebase.
Project Overview
Agent NERO is a Model Context Protocol (MCP) server that provides persistent, named LLM agents to Claude Code. Unlike disposable subagents, NERO agents stay alive in memory with full conversation history, tool-use capabilities, and a shared memory bus.
- Language: TypeScript (strict mode, ES2022 target, ESNext modules)
- Runtime: Node.js >= 20.0.0
- Transport: stdio (JSON-RPC 2.0) via
@modelcontextprotocol/sdk - LLM Backend: Anthropic API via
@anthropic-ai/sdk(Opus and Sonnet models)
Architecture Quick Reference
src/index.ts Entry point, MCP server setup, tool registration
src/types.ts All TypeScript interfaces and type definitions
src/agent.ts NeroAgent class — tool-use loop, history management
src/agent-pool.ts Agent lifecycle management (spawn/kill/reset/broadcast)
src/agent-tools.ts 7 internal tool definitions + executors (file I/O, grep, shell, memory)
src/memory-bus.ts Shared key-value store with versioning
src/tools/*.ts 10 MCP tool handlers (one file per tool)
Build and Run
# Run from source (no build step needed)
npx tsx src/index.ts
# With file watching
npm run dev
# Type check (no emit)
npm run typecheck
# Full build to dist/
npm run build
Key Conventions
- File naming:
kebab-case.ts - Class naming:
PascalCase(NeroAgent, MemoryBus, AgentPool) - MCP tool naming:
nero_prefix,snake_case(nero_spawn, nero_ask) - Internal tool naming:
snake_casewithout prefix (read_file, run_command) - Tool registration pattern: Each MCP tool lives in
src/tools/<name>.tsand exports aregister*Tool()function - Zod schemas: Used for all MCP tool input validation
- Logging:
process.stderr.write()only (stdout is reserved for MCP JSON-RPC)
Important Constraints
- stdout is exclusively for MCP JSON-RPC communication. Never use
console.log(). - Agent history must always start with a
userrole message (Anthropic API requirement). - The tool-use loop is capped at 15 iterations per
nero_askcall. - History pruning uses both a sliding window (configurable, default 50 messages) and a token budget (100k estimated tokens).
- Path sanitization blocks /proc, /sys, /dev, /boot for agent internal tools.
- Destructive shell commands are blocked (rm -rf /, mkfs, dd if=, fork bombs).
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.
- 2d ago First seen · 79 lines · 822 tokens per session scan C 00706fc5e215
agent-nero CLAUDE.md is an instructions file published in the GitHub repository sanchez314c/agent-nero (0 stars, last pushed 3mo ago), licensed MIT. It adds 822 tokens to every session, about $0.0041 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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).
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.