Borrowing it
Nothing to install: this file belongs to l3lackcurtains/trading-ops. 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/l3lackcurtains/trading-ops/main/CLAUDE.mdgit clone --depth 1 https://github.com/l3lackcurtains/trading-opsWrote 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/l3lackcurtains/trading-ops/claude-md)<a href="https://agentmods.dev/instructions/l3lackcurtains/trading-ops/claude-md"><img src="https://agentmods.dev/badge/instructions/l3lackcurtains/trading-ops/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/l3lackcurtains/trading-ops/claude-md"><img src="https://agentmods.dev/badge/instructions/l3lackcurtains/trading-ops/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.02279 | $0.02279 |
| Opus 5 | $0.01140 | $0.01140 |
| Sonnet 5 | $0.00456 | $0.00456 |
| Haiku 4.5 | $0.00228 | $0.00228 |
Grade A, and why
trading-ops 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 9d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
trading-ops — Project Rules
This file is auto-loaded by Claude Code for every session in this project. It enforces cross-cutting rules globally so every slash command and every freeform conversation inherits them.
For a full repo map, see STRUCTURE.md.
Authoritative protocols
Two rule areas in guide/. Pick the right one for the task:
guide/scan-rules.md— index pointing intoguide/scan/, the protocol for/scan(universal — auto-detects stock/crypto/index/FX/commodity),/scan-macro,/scan-fundamentals,/scan-earnings,/rescan. Split into focused files: structure, protocol, tiers, scorecard, data, crypto-flow, index-flow, fx-flow, commodity-flow, style.guide/discover-rules.md— protocol for/discover. SCREENS folder, screen file structure, retention, verified Finviz filter prefix reference, all preset filter sets (q1/q2/q3/q4/quality/growth/value/defense), 0-results fallback.
Conflict resolution:
- If a
.claude/commands/*.mdfile and a guide file conflict, the guide wins. Open the fix in the guide. - Within
guide/scan/, see the conflict-resolution table inguide/scan-rules.md.
Hard boundaries (never cross)
These apply to every command and every freeform action:
docs/is read-only knowledge base —/ingestis the only writer. Never editdocs/directly. Never create files in it from a scan, freeform action, agent, or self-improvement-loop. The/ingestslash command (.claude/commands/ingest.md) is the single authorized entry point for adding or extending framework knowledge indocs/, and it always shows a write plan and waits for user consent before applying. If during a scan the framework itself seems incomplete, raise it as a "framework question" — don't write; suggest the user run/ingestif appropriate.
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.
- 9d ago First seen · 75 lines · 2,279 tokens per session scan A c5f32588a960
trading-ops CLAUDE.md is an instructions file published in the GitHub repository l3lackcurtains/trading-ops (56 stars, last pushed 4mo ago), licensed MIT. It adds 2,279 tokens to every session, about $0.0114 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
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).
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).
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.
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.