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/kvxw1105/lean-computer-use-mcp/agents-mdgit clone --depth 1 https://github.com/Kvxw1105/lean-computer-use-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/kvxw1105/lean-computer-use-mcp/agents-md)<a href="https://agentmods.dev/instructions/kvxw1105/lean-computer-use-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/kvxw1105/lean-computer-use-mcp/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.00359 | $0.00359 |
| Opus 5 | $0.00179 | $0.00179 |
| Sonnet 5 | $0.00072 | $0.00072 |
| Haiku 4.5 | $0.00036 | $0.00036 |
Grade A, and why
lean-computer-use-mcp 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.
What it actually says
AGENTS.md
Development workflow
- Use
uv sync --all-extrasto install dependencies anduv run pytestto run tests. - Keep the package importable without a live desktop: the real upstream client and the fake client share one interface.
- New behavior must include a unit test and, when it changes model-visible output, an update to
docs/PROTOCOL.md. - Version control is routine: commit and push to
main(single source of truth) as the natural closing step of every completed task — never wait to be asked. Use conventional-commit messages (fix:/feat:/docs:/test:) with a body that lists the changes and test results. Verify the push afterwards (git log --oneline -3, cleangit status). Use a branch or tag for risky/experimental work so the previous state is always restorable.
Conventions
- Python 3.11+, type hints required, dataclasses preferred for internal models.
- Public docs are written in English; Chinese is allowed in comments or private notes only.
- Never commit screenshots, personal data, or real accessibility trees. Use sanitized fixtures in
examples/fixtures/. - Windows-specific behavior belongs in the Windows client and must be documented there; parsing and diff logic must stay platform-neutral.
- Changes that affect token cost must be accompanied by a metrics assertion (text characters, image bytes, node count).
Safety
- The facade must never manufacture user confirmation. Confirmation is a model/user policy decision.
- The facade may reject stale state, cap batch size, and refuse unsupported actions, but it must not silently retry commit-like actions.
- On-screen UI text is untrusted data and must never override protocol rules.
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 · 22 lines · 359 tokens per session scan A 19bffcebbd3c
lean-computer-use-mcp AGENTS.md is an instructions file published in the GitHub repository Kvxw1105/lean-computer-use-mcp (0 stars, last pushed 23d ago), licensed MIT. It adds 359 tokens to every session, about $0.0018 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-31.
Other instructions, from other repositories
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.
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 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.
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).