Borrowing it
Nothing to install: this file belongs to Tako-Research/TakoVM. 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/Tako-Research/TakoVM/main/CLAUDE.mdgit clone --depth 1 https://github.com/Tako-Research/TakoVMWrote 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/tako-research/takovm/claude-md)<a href="https://agentmods.dev/instructions/tako-research/takovm/claude-md"><img src="https://agentmods.dev/badge/instructions/tako-research/takovm/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.00926 | $0.00926 |
| Opus 5 | $0.00463 | $0.00463 |
| Sonnet 5 | $0.00185 | $0.00185 |
| Haiku 4.5 | $0.00093 | $0.00093 |
Grade A, and why
TakoVM 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 6d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tako VM
A secure file system and Python execution layer for AI agents. Lets agents and platforms run untrusted code safely in gVisor-backed, isolated containers (each with its own workspace) backed by job queues, retries, and execution history. REST API for sync/async job execution, plus a Python SDK for library-mode usage.
Direction: evolving toward a "serverless filesystem for agents": durable, per-agent workspaces that persist and rehydrate across runs (object-store-backed, content-addressed snapshots, hydrate/flush at run boundary). Today each container is single-use; persistent workspaces are on the roadmap. gVisor remains the sole isolation boundary.
Why gVisor?
Docker alone shares the host kernel, so a container escape gives root. gVisor intercepts syscalls in a userspace kernel (runsc), so even a kernel exploit stays inside the sandbox. This is the core security promise of Tako VM.
Architecture
tako_vm/
├── server/
│ ├── app.py # FastAPI routes
│ ├── queue.py # WorkerPool, async jobs
│ ├── correlation.py # Request correlation ID tracking
│ └── limits.py # Rate limiting
├── execution/
│ ├── worker.py # CodeExecutor (runs Docker containers)
│ ├── docker.py # Docker utilities (container naming, cleanup)
│ ├── builder.py # ContainerBuilder (for pre-built images)
│ ├── health.py # Health checks
│ └── retry.py # Retry logic
├── sdk/
│ └── client.py # Python SDK (library-mode client)
├── cli.py # CLI entry point (`tako-vm` command)
├── config.py # Pydantic config (TakoVMConfig)
├── constants.py # Shared constants (UV_CACHE_VOLUME, etc.)
├── job_types.py # Job type registry
├── models.py # ExecutionRecord, JobStatus
├── sandbox.py # Direct Docker sandbox (library mode, no server)
├── security.py # Security utilities
└── storage.py # PostgreSQL persistence
docker/
├── Dockerfile.executor # Base executor image (uv + gosu)
├── Dockerfile.server # API server image
└── entrypoint.sh # Installs deps, runs code as sandbox user, writes timing
lima-gvisor.yaml # Lima VM config for macOS dev with gVisor
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.
- 6d ago First seen · 81 lines · 926 tokens per session scan A 46360921309a
TakoVM CLAUDE.md is an instructions file published in the GitHub repository Tako-Research/TakoVM (87 stars, last pushed today), licensed Apache-2.0. It adds 926 tokens to every session, about $0.0046 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).
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 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.
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.