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/kahtaf/opencandle/agents-mdgit clone --depth 1 https://github.com/Kahtaf/OpenCandleWrote 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/kahtaf/opencandle/agents-md)<a href="https://agentmods.dev/instructions/kahtaf/opencandle/agents-md"><img src="https://agentmods.dev/badge/instructions/kahtaf/opencandle/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.01628 | $0.01628 |
| Opus 5 | $0.00814 | $0.00814 |
| Sonnet 5 | $0.00326 | $0.00326 |
| Haiku 4.5 | $0.00163 | $0.00163 |
Grade A, and why
OpenCandle 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OPENCANDLE
Financial data analysis agent. TypeScript + Vitest + Pi shell framework.
COMMANDS
npm start # run agent (tsx src/cli.ts)
npm run gui # run local browser GUI at 127.0.0.1:14567
npm test # unit tests — full test menu in tests/AGENTS.md
npm run lint # biome check (CI gates on this)
npm run typecheck # TypeScript typecheck without emitting files
npm run gates # full agent handoff proof battery
npm run bootstrap:agent # prepare a fresh agent worktree
npm run eval -- <suite> # eval front door — the only supported eval surface
npm run review:pr # repo autoreview + typecheck/lint/test gate
WHERE TO LOOK
| Task | Location | Notes |
|---|---|---|
| New market tool | src/tools/<domain>/ |
→ src/tools/AGENTS.md |
| New API provider | src/providers/ |
Wrap with wrapProvider(); fixture in tests/fixtures/ |
| New workflow | src/workflows/ |
Wire routing in src/routing/ |
| Tests, evals, fixtures | tests/ |
→ tests/AGENTS.md |
| Local GUI | gui/ |
→ gui/AGENTS.md |
| Type definitions | src/types/<domain>.ts |
One file per domain |
| Memory / persistence | src/memory/ |
SQLite-backed |
| System prompt | src/system-prompt.ts |
Core AI persona instructions |
| Pi shell integration | src/pi/ |
Extension, session, tool adapter |
| Add-on tool package | docs/build-a-tool.md |
Tools as separate npm packages |
Core abstractions (most-connected in the codebase; start here when tracing behavior):
SessionCoordinator(src/runtime/session-coordinator.ts) — session/turn orchestrationMarketStateService(src/market-state/service.ts) — durable watchlists, portfolios, alerts, reportscache/rateLimiter(src/infra/) andwrapProvider()(src/providers/wrap-provider.ts) — every external call goes through these
CODE STYLE
- Files kebab-case; tool names snake_case with Typebox params — copy the shape of an existing tool in
src/tools/market/. - Imports:
node:prefix for builtins,.jsextensions on relative imports,typekeyword for type-only imports. - Strictly typed. No
anyexcept provider raw API responses.
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 · 104 lines · 1,628 tokens per session scan A 5b3d16381792
OpenCandle AGENTS.md is an instructions file published in the GitHub repository Kahtaf/OpenCandle (22 stars, last pushed today), licensed MIT. It adds 1,628 tokens to every session, about $0.0081 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
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.