Borrowing it
Nothing to install: this file belongs to comisai/comis. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/comisai/comis/main/CLAUDE.mdgit clone --depth 1 https://github.com/comisai/comisWrote 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/comisai/comis/claude-md)<a href="https://agentmods.dev/instructions/comisai/comis/claude-md"><img src="https://agentmods.dev/badge/instructions/comisai/comis/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/comisai/comis/claude-md"><img src="https://agentmods.dev/badge/instructions/comisai/comis/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.07394 | $0.07394 |
| Opus 5.5 | $0.02958 | $0.02958 |
| Sonnet 5.5 | $0.01479 | $0.01479 |
| Haiku 4.5 | $0.00739 | $0.00739 |
Grade A, and why
comis CLAUDE.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 1mo 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 — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Read AGENTS.md before any code change — it is the authoritative engineering protocol.
This file is a Claude-specific operational supplement. If anything here conflicts with AGENTS.md, follow AGENTS.md and update this file.
Generic Runtime Check — Before Every Code Change
Preserve Comis as a generic agent runtime on every change. Before editing production code, read docs/developer-guide/generic-agent-architecture.md and decide whether the requested behavior is a universal runtime mechanism or application-specific expertise.
- Runtime code may provide reusable mechanisms for orchestration, models, tools, memory, channels, scheduling, approvals, delivery, observability, security, typed prompts, locale policy, and immutable workspace policy.
- Do not add an industry, persona, business workflow, fixed human language, response script, domain vocabulary, or task-specific tool instructions to the engine prompt, workspace starters, default config,
packages/core, orpackages/agent. - Put deployment-specific policy and persona in operator workspace files. Put reusable procedures, examples, domain knowledge, and tool-selection guidance in an opt-in prompt skill. When it should ship with Comis, build a repository-shipped skill instead of specializing runtime code — AGENTS.md §6.5 owns which skill tree actually ships and seeds.
- Put external API capabilities behind MCP or a typed adapter. Keep their instructions bounded and attributed, preserve side-effect/approval metadata, and never let integration or skill prose grant capabilities or override engine/operator policy.
- Promote behavior into the runtime only when an unrelated deployment can use it without inheriting the requester's assumptions. Do not accept a temporary hard-coded special case.
During final diff review, ask: would a completely unrelated agent inherit any domain assumption from this change? If yes, move that behavior to workspace policy, a skill, MCP, or an adapter before calling the change complete. Run pnpm vitest run test/architecture/generic-runtime-boundary.test.ts for every change touching runtime prompts, workspace policy, locale behavior, integrations, health surfaces, or specialization boundaries; extend that gate when the new regression class is not already covered.
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.
- 1mo ago First seen · 234 lines · 7,394 tokens per session scan A 7329fd0d62c1
comis CLAUDE.md is an instructions file published in the GitHub repository comisai/comis (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 7,394 tokens to every session, about $0.0296 per session on Opus 5.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
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.