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/lee-to/ai-workspace/agents-mdgit clone --depth 1 https://github.com/lee-to/ai-workspaceWrote 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/lee-to/ai-workspace/agents-md)<a href="https://agentmods.dev/instructions/lee-to/ai-workspace/agents-md"><img src="https://agentmods.dev/badge/instructions/lee-to/ai-workspace/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.01185 | $0.01185 |
| Opus 5 | $0.00593 | $0.00593 |
| Sonnet 5 | $0.00237 | $0.00237 |
| Haiku 4.5 | $0.00119 | $0.00119 |
Grade A, and why
ai-workspace 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Project map for AI agents. Keep this file up-to-date as the project evolves.
Project Overview
Cross-project shared context CLI + MCP server. Manages shared files, directories, and notes across projects organized into groups, with full-text search and a local Rust-only CodeGraph MVP.
Tech Stack
- Language: Rust (edition 2024)
- Database: SQLite (rusqlite, bundled)
- CLI: Clap v4 (derive)
- Protocol: MCP over stdio (JSON-RPC, custom implementation)
Project Structure
ai-workspace/
├── Cargo.toml # Package config, dependencies
├── Cargo.lock # Locked dependency versions
├── Makefile # Build automation (build, test, lint, fmt, check)
├── README.md # Project landing page
├── src/
│ ├── main.rs # Entry point, clap App definition
│ ├── models.rs # Data models (Project, Group, SharedItem, SharedItemKind)
│ ├── walk.rs # File tree walker and grep (ignore + regex crates)
│ ├── indexer.rs # FTS5 indexer for shared .md files (mtime refresh, reindex)
│ ├── codegraph.rs # Rust-only CodeGraph parser, sync/reindex, source snippets
│ ├── cli/
│ │ └── mod.rs # CLI subcommands and handlers
│ ├── db/
│ │ ├── mod.rs # DB module exports
│ │ ├── schema.rs # SQLite schema creation (tables, FTS5, triggers)
│ │ └── crud.rs # Database CRUD operations (Db struct)
│ └── mcp/
│ ├── mod.rs # MCP server entry (stdio loop, request routing)
│ ├── protocol.rs # JSON-RPC types (request, response, error)
│ └── tools.rs # MCP tool implementations (workspace, project, service, event, codegraph tools)
├── tests/
│ ├── cli_tests.rs # CLI integration tests
│ ├── fts_search.rs # FTS5 fulltext search integration tests
│ └── mcp_tests.rs # MCP protocol integration tests
└── .ai-factory/
└── DESCRIPTION.md # Project specification and tech stack
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 · 95 lines · 1,185 tokens per session scan A 580506f11ab8
ai-workspace AGENTS.md is an instructions file published in the GitHub repository lee-to/ai-workspace (58 stars, last pushed 9d ago), licensed MIT. It adds 1,185 tokens to every session, about $0.0059 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
cli AGENTS.md
AGENTS.md instructions for googleworkspace/cli, covering agents.md, project overview, build & test, changesets and architecture.
turso AGENTS.md
Instructions for tursodatabase/turso, covering turso agent guidelines, quick reference, testing, running tests and test organization.
intelligent-terminal rust.instructions.md
Concise Rust coding conventions for this repository.
azure-sdk-for-rust resourcemanager.instructions.md
Instructions for Azure/azure-sdk-for-rust, a project described as: This repository is for the active development of the Azure SDK for Rust. For consumers of the SDK we recommend visiting Docs.rs and looking up the docs for any of libraries in the SDK.
iroha AGENTS.md
AGENTS.md instructions for hyperledger-iroha/iroha, covering agents instructions, quickstart, repository structure, development workflow and documentation.
bifrost AGENTS.md
Instructions for bifrost-proxy/bifrost, covering bifrost 项目开发规则, 执行心法, 执行模式与完成定义, 任务模式判定 and 变更类型与验证路由（先判定，后执行）.