Borrowing it
Nothing to install: this file belongs to moxiespirit/oathscore. 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/moxiespirit/oathscore/main/CLAUDE.mdgit clone --depth 1 https://github.com/moxiespirit/oathscoreWrote 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/moxiespirit/oathscore/claude-md)<a href="https://agentmods.dev/instructions/moxiespirit/oathscore/claude-md"><img src="https://agentmods.dev/badge/instructions/moxiespirit/oathscore/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.00740 | $0.00740 |
| Opus 5 | $0.00370 | $0.00370 |
| Sonnet 5 | $0.00148 | $0.00148 |
| Haiku 4.5 | $0.00074 | $0.00074 |
Grade A, and why
oathscore 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OathScore - Claude Code Instructions
Project Overview
OathScore is a trust layer for AI trading agents. Two products:
/nowendpoint — real-time world state (exchanges, volatility, events, data health) in one call- API quality ratings — independent scoring of financial data APIs (0-100 composite)
Architecture
- Backend: FastAPI on Railway (Docker), Python 3.12+
- Frontend/Docs: Static files served from
public/ - Storage: Dual-write — local JSON (
data/monitor/) + Supabase (persistent) - Billing: Stripe (webhooks verified with HMAC SHA-256) + x402 micropayments (USDC)
- Domain:
api.oathscore.dev(Cloudflare DNS -> Railway)
Key Directories
src/ # All Python source
main.py # FastAPI app, all routes
aggregator.py # Builds /now response
events.py # Economic calendar + FOMC/CPI countdowns
exchange_status.py # Exchange open/close logic
volatility.py # VIX/VVIX/term structure
billing.py # Stripe + API key management
rate_limit.py # Tiered rate limiting
x402.py # Pay-per-request micropayments
config.py # Shared constants
mcp_server.py # MCP server (8 tools)
monitor/
scheduler.py # Background probe loops
ping_probe.py # Uptime + latency
freshness_probe.py # Data staleness
schema_probe.py # Schema stability
docs_probe.py # Documentation quality
accuracy_probe.py # Forecast verification
scoring.py # Composite score engine
alerts.py # Degradation detection
store.py # Local JSON + Supabase dual-write
supabase_store.py # Supabase REST client
config.py # Monitored API definitions
public/ # Static files (llms.txt, ai-plugin.json, robots.txt)
examples/ # Integration examples (httpx, CrewAI, LangChain)
tests/ # API tests against live deployment
docs/ # Methodology, launch posts
tracking/ # Session state, task tracking
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 · 62 lines · 740 tokens per session scan A b44a8091c7f2
oathscore CLAUDE.md is an instructions file published in the GitHub repository moxiespirit/oathscore (1 stars, last pushed 5mo ago), licensed MIT. It adds 740 tokens to every session, about $0.0037 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.