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/miniidealab/openlogos/agents-mdgit clone --depth 1 https://github.com/miniidealab/openlogosWhat 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.03006 | $0.03006 |
| Opus 5 | $0.01503 | $0.01503 |
| Sonnet 5 | $0.00601 | $0.00601 |
| Haiku 4.5 | $0.00301 | $0.00301 |
Grade A, and why
openlogos 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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- openlogos CLAUDE.md — 92% identical, 4 lines differ
How it starts
The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Assistant Instructions
This project follows the OpenLogos methodology.
Read logos/logos-project.yaml first to understand the project resource index.
Project Context
- Config:
logos/logos.config.json - Resource Index:
logos/logos-project.yaml
⚠️ 语言策略(最高优先级)
本项目的文档语言为 中文(配置于 logos/logos.config.json → locale: "zh")。
你的所有输出——包括生成的文档、代码注释、回复消息——必须使用中文。 即使 Skill 文件使用其他语言编写,你的输出也必须是中文。 违反此规则将导致产出不可用。
Methodology Rules
- Never write code without first completing the design documents
- Follow the Why → What → How progression
- All API designs must originate from scenario sequence diagrams
- All code changes must have corresponding API orchestration tests
- Use the Delta change workflow for iterations (see logos/changes/ directory)
- All generated test code must include an OpenLogos reporter (see logos/spec/test-results.md)
Interaction Guidelines
When the user's request is vague or they ask "what should I do next":
- Scan
logos/resources/to determine the current project phase - Suggest the specific next step based on what's missing
- Provide a ready-to-use prompt the user can directly say
- Never start generating documents without confirming key information
Phase 检测逻辑(检测到对应阶段时,必须先读取 Skill 文件并按其步骤执行):
logos/resources/prd/1-product-requirements/为空 → Phase 1 → 读取logos/skills/prd-writer/SKILL.md并按其步骤执行- 需求存在但
2-product-design/为空 → Phase 2 → 读取logos/skills/product-designer/SKILL.md并按其步骤执行 - 设计存在但
3-technical-plan/1-architecture/为空 → Phase 3 Step 0 → 读取logos/skills/architecture-designer/SKILL.md并按其步骤执行 - 架构存在但
3-technical-plan/2-scenario-implementation/为空 → Phase 3 Step 1 → 读取logos/skills/scenario-architect/SKILL.md并按其步骤执行 - 场景存在但
logos/resources/api/为空 → Phase 3 Step 2 → 读取logos/skills/api-designer/SKILL.md和logos/skills/db-designer/SKILL.md并按其步骤执行 - API / DB 设计完成后但
3-technical-plan/3-deployment/为空 → Phase 3 Step 3 → 读取logos/skills/deployment-designer/SKILL.md并按其步骤执行 - 部署方案存在但
logos/resources/test/为空 → Phase 3 Step 4a → 读取logos/skills/test-writer/SKILL.md并按其步骤执行(如需部署需同时设计 smoke) - 测试用例存在但
logos/resources/scenario/为空 → Phase 3 Step 4b → 读取logos/skills/test-orchestrator/SKILL.md并按其步骤执行(仅 API 项目) - 编排测试存在但
logos/resources/implementation/为空 → Phase 3 Step 5 → 读取logos/skills/code-implementor/SKILL.md并按其步骤执行(完成后可用logos/skills/code-reviewer/SKILL.md进行代码审查) - 代码已生成但
logos/resources/verify/acceptance-report.md不存在 → Phase 3 Step 6(运行测试后openlogos verify) - 部署完成但
smoke-report.md/SMOKE_PASS缺失 → Phase 3 Step 8(openlogos smoke,人类确认点)
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 · 142 lines · 3,006 tokens per session scan A aff5cf089d04
openlogos AGENTS.md is an instructions file published in the GitHub repository miniidealab/openlogos (71 stars, last pushed 6d ago), licensed Apache-2.0. It adds 3,006 tokens to every session, about $0.0150 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
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.