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/bkuri/jesse-mcp/agents-mdgit clone --depth 1 https://github.com/bkuri/jesse-mcpWrote 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/bkuri/jesse-mcp/agents-md)<a href="https://agentmods.dev/instructions/bkuri/jesse-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/bkuri/jesse-mcp/agents-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 | $0.01318 | $0.01318 |
| Opus 5 | $0.00659 | $0.00659 |
| Sonnet 5 | $0.00264 | $0.00264 |
| Haiku 4.5 | $0.00132 | $0.00132 |
Grade A, and why
jesse-mcp AGENTS.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 4d 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jesse MCP Development Guidelines
MCP server exposing Jesse's algorithmic trading framework to LLM agents. 46 tools across 6 phases.
External References
- jessegpt.md - Strategy writing, indicators, Jesse workflow
- docs/jesse-rest-api.md - Full REST API payload structures
Build/Lint/Test
pip install -e . # Install editable
pytest # Run tests
pytest -v -s tests/test_x.py # Verbose with print
flake8 jesse_mcp/ && black jesse_mcp/ && mypy jesse_mcp/ # Lint/format/typecheck
python -m jesse_mcp # Run server (stdio)
python -m jesse_mcp --transport http --port 8000 # Run server (HTTP)
Code Style
- Formatting: black (88 chars), double quotes
- Imports: stdlib → third-party → local (blank lines between)
- Types: Use
typingmodule (Dict[str, Any],Optional[T], etc.) - Naming:
PascalCaseclasses,snake_casefunctions,UPPER_SNAKE_CASEconstants - Errors: Return
{"error": str(e), "error_type": type(e).__name__}from tools - Logging:
logger = logging.getLogger("jesse-mcp.phase3"), emoji prefixes (✅❌⚠️)
Jesse REST API Gotchas
These are the common mistakes that cause silent failures:
warm_up_candlesinconfig- NOT at root levelexchangesrequiresbalance- Missing balance causes errors- ID must be valid UUID - Use
str(uuid.uuid4()) - Symbol format:
BTC-USDTwith hyphen - Date format:
YYYY-MM-DDstring - Strategy name: Case-sensitive, must match class exactly
See docs/jesse-rest-api.md for full payload structures.
Architecture Patterns
Lazy Initialization (allows testing without Jesse)
jesse = None
_initialized = False
def _initialize_dependencies():
global jesse, _initialized
if _initialized: return
# ... init logic
_initialized = True
Singleton with Getter
_optimizer_instance = None
def get_optimizer(use_mock=None) -> Phase3Optimizer:
global _optimizer_instance
if _optimizer_instance is None:
_optimizer_instance = Phase3Optimizer(use_mock=use_mock)
return _optimizer_instance
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.
- 4d ago First seen · 166 lines · 1,318 tokens per session scan A 4c3d4726ab02
jesse-mcp AGENTS.md is an instructions file published in the GitHub repository bkuri/jesse-mcp (20 stars, last pushed 3mo ago), licensed MIT. It adds 1,318 tokens to every session, about $0.0066 per session on Opus 5. A static security scan graded it A with 0 findings. It comes from a forked repository.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.