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/lithos-ai/motus/agents-mdgit clone --depth 1 https://github.com/lithos-ai/motusWrote 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/lithos-ai/motus/agents-md)<a href="https://agentmods.dev/instructions/lithos-ai/motus/agents-md"><img src="https://agentmods.dev/badge/instructions/lithos-ai/motus/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.04136 | $0.04136 |
| Opus 5 | $0.02068 | $0.02068 |
| Sonnet 5 | $0.00827 | $0.00827 |
| Haiku 4.5 | $0.00414 | $0.00414 |
Grade A, and why
motus AGENTS.md scanned grade A with 1 finding 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
async def fetch(url: str) -> dict: How it starts
The opening of the file, as written. The whole thing — 421 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Motus — Agent Guide
Motus is a full-stack AI agent framework built on a custom async task-graph runtime. It provides agent definitions (ReAct loop), multi-provider LLM clients, a composable tool system (function tools, MCP, Docker sandboxes), persistent memory, a skills system, and FastAPI-based serving infrastructure.
Commands
# Install all dependencies (core + dev)
uv sync --all-extras --dev
# Run unit tests (fast, no API keys needed)
uv run pytest -v tests/unit -m "not slow"
# Run integration tests with VCR replay (no API keys needed)
uv run pytest -v tests/integration -m "integration"
# Re-record VCR cassettes (requires real API keys in .env)
uv run pytest tests/integration/examples/ -v --vcr-record=all
# Format code
uv run ruff format
# Lint and auto-fix
uv run ruff check --fix
# Run all pre-commit hooks on all files
uv run pre-commit run --all-files
# Install git hooks (first-time setup)
uv run pre-commit install
# Start the agent server
uv run motus-serve start myapp:server --port 8000
# Interactive chat with an agent
uv run motus-serve chat
Tech Stack
- Python 3.12+ (uses modern syntax:
X | None,dict[K, V],TYPE_CHECKING) - Async runtime: asyncio +
concurrent.futuresfor cross-thread coordination - Validation: pydantic >= 2.12.5
- Web: fastapi >= 0.128.0, uvicorn >= 0.40.0, httpx >= 0.28.1
- LLM clients: anthropic >= 0.40.0, openai >= 2.15.0, google-genai >= 1.0.0
- Tool execution: docker >= 7.1.0, kubernetes >= 34.1.0, mcp[cli] >= 1.25.0, paramiko >= 4.0.0
- Testing: pytest >= 9.0.2, pytest-asyncio >= 0.24.0, vcrpy >= 8.1.1
- Linting: ruff (rules: E, F, I, W; ignores: E501, E402)
- Package manager: uv (workspace with members
.andservices/*)
Project Structure
src/motus/
├── __init__.py # Motus, ModelClient — high-level API
├── runtime/ # Core task-graph engine (owner: @NorthmanPKU)
│ ├── agent_runtime.py # GraphScheduler (event loop, dependency DAG, retries/timeouts)
│ │ # AgentRuntime (thread-safe wrapper, cross-thread task submission)
│ ├── agent_task.py # @agent_task decorator, AgentTaskDefinition (descriptor protocol)
│ ├── agent_future.py # AgentFuture — lazy future with operator overloading & sync barriers
│ ├── task_instance.py # TaskInstance (COMPUTE/RESOLVE), TaskPolicy, TaskStatus, stack stitching
│ ├── hooks.py # HookManager — task_start / task_end / task_error lifecycle events
│ ├── types.py # AgentTaskId, AgentFutureId counters
│ └── tracing/ # Distributed tracing, OpenTelemetry export, live trace server
├── agent/ # Agent definitions (owners: @NorthmanPKU, @JackFram)
│ ├── base_agent.py # AgentBase[T] — abstract base with tools, memory
│ ├── react_agent.py # ReActAgent — Reasoning + Acting loop
│ ├── skills.py # Skill loading (SKILL.md) and tool creation
│ └── tasks.py # model_serve_task — agent task for model calls
├── tools/ # Tool ecosystem (owners: @eliotsolomon18, @coppock, @NorthmanPKU)
│ ├── core/
│ │ ├── tool.py # Tool protocol (description, json_schema, __call__)
│ │ ├── function_tool.py # FunctionTool — wraps Python functions as LLM tools
│ │ ├── mcp_tool.py # MCP (Model Context Protocol) tool integration
│ │ ├── sandbox.py # Sandbox ABC (create/acreate/connect factory methods)
│ │ ├── tool_provider.py # ToolProvider interface
│ │ ├── composite_tool_provider.py
│ │ ├── normalize.py # Schema generation and tool normalization
│ │ └── decorators.py # @tool and @tools convenience decorators
│ ├── providers/
│ │ ├── docker/ # DockerSandbox — container-based code execution
│ │ └── brave/ # Brave Search tool
│ └── runtime/
│ └── sync_manager.py # Sync/async coordination for tool calls
├── models/ # Multi-provider LLM clients (owner: @yzhou442)
│ ├── base.py # BaseChatClient, ChatMessage, ToolCall, ChatCompletion
│ ├── anthropic_client.py # Claude API
│ ├── openai_client.py # OpenAI API
│ ├── gemini_client.py # Google Gemini API
│ ├── openrouter_client.py # OpenRouter aggregator
│ └── message_schema.py # Unified message data models
├── memory/ # Memory & context management (owners: @JackFram, @vasiliskyp)
│ ├── base_memory.py # BaseMemory abstract interface
│ ├── basic_memory.py # BasicMemory (simple in-memory)
│ ├── compaction_memory.py # CompactionMemory (auto-compacting context)
│ ├── config.py # CompactionMemoryConfig
│ ├── interfaces.py # ConversationLogStore ABC
│ └── stores/ # LocalConversationLogStore
├── serve/ # Agent serving infrastructure
│ ├── server.py # AgentServer (FastAPI)
│ ├── cli.py # motus-serve CLI (start/chat/submit/status/run)
│ ├── worker/ # Worker pool (executor, context, pool)
│ └── analytics/ # Analytics collector and web dashboard
└── utils/ # Shared utilities (owner: @coppock)
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.
- 5d ago First seen · 421 lines · 4,136 tokens per session scan A cb59b0ee159f
motus AGENTS.md is an instructions file published in the GitHub repository lithos-ai/motus (482 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 4,136 tokens to every session, about $0.0207 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.