Borrowing it
Nothing to install: this file belongs to MangroveTechnologies/mangrove-agent. 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/MangroveTechnologies/mangrove-agent/main/CLAUDE.mdgit clone --depth 1 https://github.com/MangroveTechnologies/mangrove-agentWrote 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/mangrovetechnologies/mangrove-agent/claude-md)<a href="https://agentmods.dev/instructions/mangrovetechnologies/mangrove-agent/claude-md"><img src="https://agentmods.dev/badge/instructions/mangrovetechnologies/mangrove-agent/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.00874 | $0.00874 |
| Opus 5 | $0.00437 | $0.00437 |
| Sonnet 5 | $0.00175 | $0.00175 |
| Haiku 4.5 | $0.00087 | $0.00087 |
Grade A, and why
mangrove-agent 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mangrove Agent
A local Mangrove-powered trading bot. Author strategies, backtest, paper-trade, go live when ready. Persona is defined in Project Context + Agent Identity at the bottom of this file.
Architecture
Dual protocol:
- REST:
/api/v1/*(free + auth),/api/x402/*(payment-gated) - MCP:
/mcp(all tiers via FastMCP)
Three-tier access:
- Free: no credentials (health, discovery)
- Auth: API key in
X-API-Keyheader - x402: payment or API key bypass (demo route:
hello_mangrove)
Service-layer pattern: Routes and MCP tools both call shared services in server/src/services/. Never duplicate business logic.
State ownership: THIS agent owns the tick and the record. APScheduler here fires every strategy evaluation (MangroveAI never schedules for the agent), and the local SQLite (agent-data/agent.db) persists every trade, evaluation, position, and per-strategy execution_state — unconditionally, regardless of evaluation lane. Evaluation itself (signals, sizing, exits) happens in the MangroveAI engine via evaluation_lane: server (default — by-id; engine DB is authoritative for engine position state) or stateless (object-lane; the agent supplies and receives all state, persisted locally and echoed each tick). The engine decides what to trade; the agent decides when to ask, executes, and keeps the books.
Conventions
- Routes in
server/src/api/routes/-- one file per resource - Services in
server/src/services/-- one file per resource, called by both routes and MCP tools - MCP tools in
server/src/mcp/tools.py-- registered viaregister_tool() - Tests in
server/tests/-- mirrorsrc/ - Config in
server/src/config/-- per-environment JSON files (no.env)
Full extension workflow: docs/contributing.md.
Rules
- Trading bot behavior:
.claude/rules/trading-bot-workflow.md - Wallet handling:
.claude/rules/wallet-presentation.md - Risk management (engine gates + portfolio kill switch — what happens behind the scenes):
.claude/rules/risk-management.md - Git workflow:
.claude/rules/git-workflow.md
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 · 59 lines · 874 tokens per session scan A bc0351a828c3
mangrove-agent CLAUDE.md is an instructions file published in the GitHub repository MangroveTechnologies/mangrove-agent (5 stars, last pushed 1mo ago), licensed MIT. It adds 874 tokens to every session, about $0.0044 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.
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.