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/wot-ui/open-wot/agents-mdgit clone --depth 1 https://github.com/wot-ui/open-wotWrote 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/wot-ui/open-wot/agents-md)<a href="https://agentmods.dev/instructions/wot-ui/open-wot/agents-md"><img src="https://agentmods.dev/badge/instructions/wot-ui/open-wot/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.00663 | $0.00663 |
| Opus 5 | $0.00331 | $0.00331 |
| Sonnet 5 | $0.00133 | $0.00133 |
| Haiku 4.5 | $0.00066 | $0.00066 |
Grade A, and why
open-wot 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 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.
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
Project Guidelines
Scope
open-wot 是 wot-ui v2 的 CLI、MCP 与离线知识库仓库。优先做最小改动，保持命令输出、数据结构和测试预期稳定。
Architecture
src/commands放 CLI 子命令实现。src/mcp放 MCP server、tools 与 prompts。src/data放元数据加载与版本解析。scripts/extract.ts负责从上游 wot-ui 仓库提取离线数据。data/保存发布时携带的离线数据。skills/保存给 Agent 使用的技能说明与参考资料。apps/website是官网子包；README.md是官网/docs的唯一内容源。
Build And Test
- 安装依赖：
pnpm install - 代码检查：
pnpm lint - 类型检查：
pnpm typecheck - 测试：
pnpm test - 构建：
pnpm build - 全量校验：
pnpm lint && pnpm typecheck && pnpm test && pnpm build
OpenSpec Workflow
- 新功能、破坏性变更、跨模块改造或架构调整，先使用
.agents/skills/openspec-propose创建并评审变更提案，再使用.agents/skills/openspec-apply-change实现。 - 小型 bug 修复、拼写和文档微调可以直接修改，不要求创建 OpenSpec change。
- 实现完成后使用
.agents/skills/openspec-verify-change核对规格、任务、实现和测试；确认无误后使用.agents/skills/openspec-archive-change归档。 - OpenSpec 的项目上下文和 artifact 规则位于
openspec/config.yaml；进行 OpenSpec 工作流时以 CLI 返回的路径和状态为准，不手工假设 artifact 位置。 - SDD/OpenSpec 的 proposal、spec、design 和 tasks 文档统一使用简体中文；仅保留校验器要求的固定英文标记以及代码标识符、路径、命令和产品名。
Conventions
- 修改 CLI、MCP tool、prompt 或数据结构后，同步检查对应测试与 README。
- 修改提取逻辑后，优先验证真实提取流程或至少验证生成数据兼容现有 loader。
- 修改命令输出后，至少手动跑一个真实命令确认文本格式没有意外回归。
- 修改 CLI、MCP 或接入流程文档时，只编辑
README.md；官网文档会在构建时直接读取它，不要新增平行的手写 HTML 文档。 - 修改官网后运行
pnpm site:lint && pnpm site:build。 - 处理 wot-ui 组件知识、示例生成、文档问答时，先查看
skills/wot-ui-v2/SKILL.md。 - 未经明确要求，不要顺手重构无关模块。
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 · 43 lines · 663 tokens per session scan A e831954e74e4
open-wot AGENTS.md is an instructions file published in the GitHub repository wot-ui/open-wot (33 stars, last pushed 7d ago), licensed MIT. It adds 663 tokens to every session, about $0.0033 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
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).