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/comisai/comis/claude-mdgit clone --depth 1 https://github.com/comisai/comisWhat 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.07394 | $0.07394 |
| Opus 5 | $0.03697 | $0.03697 |
| Sonnet 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 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.
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.
- 2d 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 2d ago), licensed Apache-2.0. It adds 7,394 tokens to every session, about $0.0370 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
PuPu AGENTS.md
Instructions for haoxiang-xu/PuPu, covering gitnexus — code intelligence, always do, never do, resources and cli.
PuPu CLAUDE.md
Instructions for haoxiang-xu/PuPu, covering gitnexus — code intelligence, always do, never do, resources and cli.
commonly CLAUDE.md
Instructions for Team-Commonly/commonly, covering claude.md / agents.md, 🧠 product vision & architecture philosophy, what commonly is, the architecture model and key concepts.
takt AGENTS.md
Instructions for nrslib/takt, covering repository guidelines, project structure & module organization, build, test, and development commands, coding style & naming conventions and testing guidelines.
VaultysClaw agent-controller.instructions.md
Use when working on the agent-controller package: tools, skills, agent runtime, WebSocket client, local SQLite DB, LLM integration, or CLI modes.
open-ace CLAUDE.md
Instructions for open-ace/open-ace, covering claude.md, where process documents go, pushing, test placement and ci semantics and schema snapshots (schema-sync ci).