Borrowing it
Nothing to install: this file belongs to mbk-dev/okama-mcp. 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/mbk-dev/okama-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/mbk-dev/okama-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/mbk-dev/okama-mcp/agents-md)<a href="https://agentmods.dev/instructions/mbk-dev/okama-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/mbk-dev/okama-mcp/agents-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/mbk-dev/okama-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/mbk-dev/okama-mcp/agents-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.02085 | $0.02085 |
| Opus 5.5 | $0.00834 | $0.00834 |
| Sonnet 5.5 | $0.00417 | $0.00417 |
| Haiku 4.5 | $0.00209 | $0.00209 |
Grade B, and why
okama-mcp AGENTS.md scanned grade B with 2 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
`chilango`, so install new files via `sudo cp` (then `sudo chown chilango:chilango`, mode 644). Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`curl -s https://mcp.okama.io/ | diff - deploy/nginx/index.html`. How it starts
The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
okama-mcp — Development rules for AI agents
Environment
- Project uses uv for environment and dependency management. Each worktree owns its
.venv/. - New dependencies must be added in
pyproject.tomland additionally torequirements.txt. - Use the interpreter in the uv environment (
uv run python ...). - Use
uv addfor runtime dependencies,uv add --group testfor test tools, anduv add --group devfor development tools. Both groups are installed by default. uv.lockis local and gitignored, as this project is distributed through PyPI. Fresh checkouts resolve compatible versions; do not require--lockedbefore the first sync.- All temporary files (including generated images, screenshots, scratch scripts, data
dumps) go into the gitignored
tmp/directory at the project root — never into the repo root,/tmp, or source directories. Clean it up freely; nothing intmp/is precious.
Worktrees
Worktrees for this repo live at ~/projects/rs/wt/okama-mcp/<branch> — never inside the
repository tree. Two Orca settings enforce that and they are stored locally, not in the
repo, so a machine rebuild loses them silently; re-apply both:
worktreeBasePath: ../../../wt—orca project setup-update --setup <setup-id> --worktree-base-path ../../../wt.- Wait for setup to complete before starting agent — a toggle in Orca's repository
settings, no CLI equivalent. Without it the agent (and its MCP client) starts while
uv sync --all-groupsis still running, which is exactly the failure below.
Never type anything into Orca's local Setup Script field: a non-empty local script flips
commandSourcePolicy to local-only and silently disables the committed orca.yaml.
A fresh worktree has no usable environment until its uv environment is built. orca.yaml
(scripts.setup) does that automatically for Orca-created worktrees; for a manual
git worktree add, run the same two commands in the new tree before anything else:
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 Changed · +10 lines · +197 tokens per session 6e09e9b0a1aa
- 14d ago Changed · +4 lines · +31 tokens per session 7bd0f744e7c1
- 2mo ago Changed · -2 tokens per session 345dc08542a1
- 2mo ago First seen · 120 lines · 1,859 tokens per session scan B c74dc7ae0b18
okama-mcp AGENTS.md is an instructions file published in the GitHub repository mbk-dev/okama-mcp (5 stars, last pushed 9d ago), licensed MIT. It adds 2,085 tokens to every session, about $0.0083 per session on Opus 5.5. A static security scan graded it B with 2 findings (asks for root, makes network calls). 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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).