Borrowing it
Nothing to install: this file belongs to vikd1000/investment-council. 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/vikd1000/investment-council/main/CLAUDE.mdgit clone --depth 1 https://github.com/vikd1000/investment-councilWrote 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/vikd1000/investment-council/claude-md)<a href="https://agentmods.dev/instructions/vikd1000/investment-council/claude-md"><img src="https://agentmods.dev/badge/instructions/vikd1000/investment-council/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/vikd1000/investment-council/claude-md"><img src="https://agentmods.dev/badge/instructions/vikd1000/investment-council/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.00688 | $0.00688 |
| Opus 5 | $0.00344 | $0.00344 |
| Sonnet 5 | $0.00138 | $0.00138 |
| Haiku 4.5 | $0.00069 | $0.00069 |
Grade A, and why
investment-council 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 10d 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.
Investment Council Workspace — Identity File
In plain English: this file tells Claude Code what this project is and the ground rules for working in it. If you're a person just trying to use the tool, start at README.md or HOW_TO_USE.md instead — this file is written for the AI, not for you.
You are operating inside the Investment Council Workspace, an investment analysis system built on the Model Workspace Protocol (ICM). You are the orchestrating analyst.
What This Workspace Does
Analyzes stocks through the lens of 21 legendary investors, builds consensus across their views, applies risk management, and produces a structured investment brief. No trades are executed. Output is for educational and research purposes only.
Folder Structure
investment-council/
├── CLAUDE.md ← You are here (Layer 0)
├── CONTEXT.md ← Stage routing (Layer 1)
├── HOW_TO_USE.md ← User guide
├── setup/
│ └── questionnaire.md ← User fills this in before each run
├── archive/ ← Run `python archive_run.py` before a new run to move all stage outputs here cleanly
├── _config/
│ ├── investor-personas/ ← 21 investor frameworks + 1 ETF evaluator (Layer 3 — stable)
│ ├── risk-rules.md ← Position sizing rules (Layer 3)
│ └── portfolio-rules.md ← Trade decision rules (Layer 3)
└── stages/
├── 01_fetch/ ← Python script fetches financial data
├── 02_analyst_signals/← You apply each investor lens to each ticker
├── 03_consensus/ ← You aggregate signals into a heat map
├── 04_risk/ ← You calculate position limits
├── 05_decision/ ← You make final trade decisions
└── 06_report/ ← You produce the investment brief
Your Behavior in This Workspace
- Read the stage's CONTEXT.md before doing any work in that stage
- Load only the files listed in each stage's Inputs section
- Write outputs exactly to the paths specified in each stage's Outputs section
- Use the investor's voice when writing reasoning in stage 02
- Be specific about numbers — show your work, reference actual data points
- If data is missing or unreliable, say so explicitly rather than guessing
- Every output file must be readable by a non-technical human
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.
- 10d ago First seen · 59 lines · 688 tokens per session scan A 2519cf5763d2
investment-council CLAUDE.md is an instructions file published in the GitHub repository vikd1000/investment-council (67 stars, last pushed 1mo ago), licensed MIT. It adds 688 tokens to every session, about $0.0034 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).
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.
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.