Borrowing it
Nothing to install: this file belongs to VW3st/crypto-monitor. 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/VW3st/crypto-monitor/main/CLAUDE.mdgit clone --depth 1 https://github.com/VW3st/crypto-monitorWrote 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/vw3st/crypto-monitor/claude-md)<a href="https://agentmods.dev/instructions/vw3st/crypto-monitor/claude-md"><img src="https://agentmods.dev/badge/instructions/vw3st/crypto-monitor/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.
<a href="https://agentmods.dev/instructions/vw3st/crypto-monitor/claude-md"><img src="https://agentmods.dev/badge/instructions/vw3st/crypto-monitor/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.02588 | $0.02588 |
| Opus 5 | $0.01294 | $0.01294 |
| Sonnet 5 | $0.00518 | $0.00518 |
| Haiku 4.5 | $0.00259 | $0.00259 |
Grade A, and why
crypto-monitor 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 11d 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 — 214 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.
Overview
Vale Monitor — a self-hosted, read-only Bybit trading dashboard. It aggregates positions, balances and realised P&L across multiple accounts, reads candles, evaluates price alerts, stores strategy definitions, and exposes all of it to agents over MCP. It never places orders; every exchange call is a read.
See README.md for setup and usage, and docs/API.md for the endpoint reference. This file covers what isn't obvious from reading a single file.
backend-setup/ is a different system. It is a Python trading bot that
places real leveraged orders, with its own .env, its own JSON config and its own
README. The TypeScript dashboard does not import it
and never places orders. Do not blur the two: guidance in this file describes the
dashboard only, and the "read-only against the exchange" property is the
dashboard's, not the repository's. Its private config
(accounts_config.json, trading_config.json, state JSON, logs) is gitignored in
two places — never un-ignore them.
The repo is kept free of unreachable modules. Every .ts/.tsx under
client/src, server, shared and scripts is reachable from an entry point
(client/src/main.tsx, server/index.ts, server/mcp/index.ts, scripts/*).
Only 11 shadcn/ui primitives are present — the unused ones were deleted, so add
what you need via the shadcn CLI rather than assuming a component exists. The
same applies to dependencies: there are no unused runtime packages.
An earlier version carried a manual wallet / transaction / P&L-record feature (three tables, ~110 lines of routes, a dozen components). Its UI was orphaned and it duplicated what the exchange already reports, so it was removed. Don't reintroduce those tables to store balances — balances come from Bybit.
Commands
npm run dev # API + Vite middleware on one port (5000)
npm run check # tsc --noEmit — the only static gate; no linter, no test runner
npm run smoke # end-to-end HTTP check; needs a server running
npm run build # vite build -> dist/public, esbuild server -> dist/index.js
npm start # run the production build
npm run mcp # run the MCP server directly
npm run db:push # drizzle-kit push from shared/schema.ts
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.
- 11d ago First seen · 214 lines · 2,588 tokens per session scan A bb5f5a7ae51e
crypto-monitor CLAUDE.md is an instructions file published in the GitHub repository VW3st/crypto-monitor (0 stars, last pushed 1mo ago), licensed MIT. It adds 2,588 tokens to every session, about $0.0129 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
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).
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.
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).