Borrowing it
Nothing to install: this file belongs to Datarails/dr-claude-code-plugins-re. 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/Datarails/dr-claude-code-plugins-re/main/CLAUDE.mdgit clone --depth 1 https://github.com/Datarails/dr-claude-code-plugins-reWrote 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/datarails/dr-claude-code-plugins-re/claude-md)<a href="https://agentmods.dev/instructions/datarails/dr-claude-code-plugins-re/claude-md"><img src="https://agentmods.dev/badge/instructions/datarails/dr-claude-code-plugins-re/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/datarails/dr-claude-code-plugins-re/claude-md"><img src="https://agentmods.dev/badge/instructions/datarails/dr-claude-code-plugins-re/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.10840 | $0.10840 |
| Opus 5.5 | $0.04336 | $0.04336 |
| Sonnet 5.5 | $0.02168 | $0.02168 |
| Haiku 4.5 | $0.01084 | $0.01084 |
Grade A, and why
dr-claude-code-plugins-re 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 yesterday.
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 — 521 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.
What This Is
A Claude Code plugin for Datarails Finance OS. It provides skills (skills/*/SKILL.md) and commands (commands/*.md) that connect to a remote MCP server at https://mcp.datarails.com/mcp (configured in .claude-plugin/plugin.json). There is no local server code — the MCP server is hosted remotely.
Critical Rules
NEVER generate reports, Excel files, or any artifacts without first fetching fresh data from the live Datarails API. Reports with fake/placeholder data have zero value.
NEVER hardcode client-specific information in skills or committed files. Table IDs, field names, and account hierarchies differ per client — every skill discovers them inline at runtime (see "Client Data Discovery" below). Never bake them into a skill, a committed config, or a persisted profile file.
Prefer the engine over local computation for metric values. When the business-metrics data layer is available (use_semantic_layer_v2) and get_business_metric_data returns empty for a CALC metric that list_business_metrics shows as clean (no status_info.error_message / source_warning), sweep parameters (date_end, aggregation_period, scenario) before deriving the value from base metrics yourself. The most common cause of an empty response is bucket-end clipping: the engine only emits a bucket when bucket_end <= date_end, so a mid-bucket date_end silently drops the in-progress period — round date_end up to the bucket end. If after the sweep you still need to compute client-side as a fallback, label it explicitly in the user-facing output: "derived from client-side because get_business_metric_data returned empty for these parameters — not the canonical engine value." Never present a derived number as if it came from the metrics layer.
Build & Release
# Bump version in plugin.json (single source of truth)
# .claude-plugin/plugin.json → "version": "X.Y.Z"
# Publish release — GitHub Actions builds the ZIP automatically
git tag vX.Y.Z && git push origin main --tags
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.
- yesterday Changed · +17 lines · +347 tokens per session 6d064406df12
- 1mo ago Changed · +22 lines · +422 tokens per session 05952b9a9526
- 1mo ago First seen · 482 lines · 10,071 tokens per session scan A 1ea7603de7e0
dr-claude-code-plugins-re CLAUDE.md is an instructions file published in the GitHub repository Datarails/dr-claude-code-plugins-re (3 stars, last pushed 2d ago), licensed MIT. It adds 10,840 tokens to every session, about $0.0434 per session on Opus 5.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
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.