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/futuregene/future-os/claude-mdgit clone --depth 1 https://github.com/futuregene/future-osWhat 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.02961 | $0.02961 |
| Opus 5 | $0.01481 | $0.01481 |
| Sonnet 5 | $0.00592 | $0.00592 |
| Haiku 4.5 | $0.00296 | $0.00296 |
Grade A, and why
future-os 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 2d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
FutureOS: one AI agent everywhere — terminal (TUI), desktop (GUI), mobile (Android/iOS), CLI, and IM bots. The core is Rust: a gRPC agent backend plus a channel bridge, loop control plane, CLI, and TUI that all connect to it. The desktop app is Tauri + React (TypeScript) and mobile is React Native (Expo). For architecture and module breakdown read docs/README.md (the docs index), docs/directory-layout.md (what lives under ~/.future/), and the code directly.
Workspace layout
The Rust workspace (Cargo.toml) members and their slice of ~/.future/ (see docs/directory-layout.md):
agent/—future-agent, the gRPC backend. Owns~/.future/agent/(settings, models, auth, JSONL sessions, skills).channels/—future-channel, the Feishu / DingTalk IM bridge. Owns~/.future/channels/config.json.orchestration/loop/—future-loop, the loop control plane (durable goals/todos/gates, deterministic should-run kernel, event-sourced state). Owns~/.future/loop/; seedocs/loop-control-plane.md.tui/—future-tui, the terminal UI (a gRPC client of the agent). Owns~/.future/tui/.cli/—future-cli, builds the unifiedfuturebinary that embeds agent/tui/channel/loop.packages/rpc/—future-rpc, the protobuf wire-contract crate (single source of truth; see proto notes below).
desktop/src-tauri is deliberately not a workspace member (excluded): it builds on its own schedule via npm/tauri, and membership would pull it into every root cargo invocation. packages/ also holds shared npm packages (markdown, thread-projection, json-preview) consumed by desktop/mobile; the repo-root package.json declares npm workspaces ["packages/*", "desktop", "mobile"], so a single npm install at the root hoists all deps.
Project memory
FUTURE.md is a workspace memory index → .future/memory/*.md (institutional gotchas: testing on Linux CI vs macOS, Rust toolchain quirks, GitHub CI/PR flow, future loop CLI operation, llvm-cov coverage measurement). Read the relevant entries before working in those areas — they encode hard-won, non-obvious constraints not visible in the code.
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.
- 2d ago First seen · 94 lines · 2,961 tokens per session scan A 1cff5cffe2a2
future-os CLAUDE.md is an instructions file published in the GitHub repository futuregene/future-os (49 stars, last pushed 3d ago), licensed MIT. It adds 2,961 tokens to every session, about $0.0148 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
kungfu copilot-instructions.md
Copilot instructions for kungfu-systems/kungfu: Read and follow AGENTS.md before proposing or running changes. It is the shared agent router for this repository, including the canonical Shifu development and build entrypoint.
open-autonomy CLAUDE.md
Instructions for valory-xyz/open-autonomy, covering claude.md, project overview, common commands, development setup and testing.
kipi-system AGENTS.md
AGENTS.md instructions for assafkip/kipi-system, covering q entrepreneur os, project structure, conventions, commands and build and test.
orloj CLAUDE.md
Instructions for OrlojHQ/orloj, covering orloj claude instructions, critical repository rules and implementation notes.
Framework_Development_Guide
Instructions for rezaho/MARSYS, covering 0. golden principle, 1. layered architecture (mental model), 2. core classes & responsibilities, 2.1 module overview & logical flow and src/agents/ - agent architecture & communication.
aeon CLAUDE.md
Instructions for aeonfun/aeon, covering aeon, how aeon works, strategy, voice and soul file hierarchy (read in this order).