Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/jsohi/app-trading-engine/claude-mdgit clone --depth 1 https://github.com/jsohi/app-trading-engineWrote 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/jsohi/app-trading-engine/claude-md)<a href="https://agentmods.dev/instructions/jsohi/app-trading-engine/claude-md"><img src="https://agentmods.dev/badge/instructions/jsohi/app-trading-engine/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.04062 | $0.04062 |
| Opus 5 | $0.02031 | $0.02031 |
| Sonnet 5 | $0.00812 | $0.00812 |
| Haiku 4.5 | $0.00406 | $0.00406 |
Grade A, and why
app-trading-engine 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 5d 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trading Engine — Developer Conventions
Reasoning Effort
Always use high reasoning effort for this project. Run /effort high at the start of every session. No shortcuts — everything must be industry standard and production ready.
Code Documentation Standards
All Java code must follow industry-standard documentation practices for a production trading system:
- Class-level Javadoc: Every public class must have a Javadoc comment describing purpose, threading model, allocation behavior, and key design decisions
- Method-level Javadoc: All public methods must have Javadoc with
@param,@return, and@throwswhere applicable - Threading annotations: Document whether a class/method is thread-safe, single-threaded, or requires external synchronization
- Allocation annotations: Hot-path classes must document "Zero allocation after construction" or explicitly note where allocation occurs
- Design rationale: Non-obvious decisions (e.g., hash collision trade-offs, sentinel values, lazy cleanup) must include inline comments explaining why, not just what
- FIX protocol references: FIX message types and tags must reference the tag number (e.g., "ClOrdID (tag 11)", "BusinessRejectReason (tag 380)")
- Cross-references: Use
{@link}to connect related classes (e.g., SessionRegistry → ClusterEgressListener → SessionLookup) - No TODO without ticket: Every TODO must reference a Linear issue (e.g.,
// TODO(APP-166): extract CompID from auth callback)
Build Commands
./gradlew build # Full build (all modules)
./gradlew test # Run all unit tests
./gradlew :messages:generateCodecs # Generate SBE codecs from trading-schema.xml
./gradlew :messages:compileJava # Compile generated codecs
./gradlew :MODULE:test # Run tests for a specific module
./gradlew :integration-tests:test # Run integration tests
./gradlew e2e # Full E2E test (3-node cluster + FIX validation via scripts/e2e.sh)
./gradlew e2eClean # Remove E2E artifacts (logs, cluster data, Aeron dirs) + kill stale processes
./gradlew spotlessApply # Auto-format all source files
./gradlew spotlessCheck # Check formatting (CI)
./gradlew jacocoTestReport # Generate code coverage (HTML + XML)
./gradlew dependencyCheckAnalyze # OWASP CVE scan (fails on CVSS >= 7)
./gradlew projects # List all subprojects
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.
- 5d ago First seen · 205 lines · 4,062 tokens per session scan A 7ca924d1b951
app-trading-engine CLAUDE.md is an instructions file published in the GitHub repository jsohi/app-trading-engine (2 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 4,062 tokens to every session, about $0.0203 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
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.
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.
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).