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/opencompanyapp/kosmokrator/claude-mdgit clone --depth 1 https://github.com/OpenCompanyApp/kosmokratorWrote 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/opencompanyapp/kosmokrator/claude-md)<a href="https://agentmods.dev/instructions/opencompanyapp/kosmokrator/claude-md"><img src="https://agentmods.dev/badge/instructions/opencompanyapp/kosmokrator/claude-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.1 | $0.01496 | $0.01496 |
| Opus 5 | $0.00748 | $0.00748 |
| Sonnet 5 | $0.00299 | $0.00299 |
| Haiku 4.5 | $0.00150 | $0.00150 |
Grade A, and why
kosmokrator 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 6d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
KosmoKrator
AI coding agent for the terminal. Mythology-themed CLI built with PHP 8.4, Symfony Console, and a dual renderer (TUI/ANSI).
Quick Start
bin/kosmokrator # Run with auto-detected renderer (TUI if available, ANSI fallback)
bin/kosmokrator --renderer=ansi # Force ANSI mode
bin/kosmokrator --no-animation # Skip the animated intro
Architecture
bin/kosmokrator → Kernel → AgentCommand → AgentSessionBuilder → AgentLoop (REPL)
├── ToolExecutor → tools + PermissionEvaluator
├── ContextManager → compaction, pruning, system prompt
├── StuckDetector → headless loop convergence
├── LLM client (AsyncLlmClient or PrismService)
├── UIManager → TuiRenderer | AnsiRenderer
├── ToolRegistry → tools (bash, file_read, file_write, file_edit, grep, glob)
└── SubagentOrchestrator → parallel child agents
Key directories
src/Agent/— Agent core: AgentLoop (REPL orchestrator), ToolExecutor, ContextManager, StuckDetector, subagent systemsrc/LLM/— LLM clients: AsyncLlmClient (Amp HTTP, async), PrismService (Prism PHP, sync), RetryableLlmClient (decorator)- prism-relay boundary: Provider-specific logic (SSE parsing quirks,
stream_optionssupport, usage extraction formats,finish_reasonmapping, error normalization, prompt caching strategies) belongs in theopencompany/prism-relaypackage, NOT in KosmoKrator'ssrc/LLM/. KosmoKrator's LLM layer should only contain agent-level orchestration: retry policy, streaming-to-UI bridging, cancellation handling. Provider capabilities (e.g.supportsStreamUsage()) are declared in prism-relay'sProviderCapabilitiesandRelayRegistry, consumed via the registry in AsyncLlmClient.
- prism-relay boundary: Provider-specific logic (SSE parsing quirks,
src/UI/— Rendering layer with split interface hierarchyUI/Tui/— Symfony TUI renderer: TuiRenderer, TuiModalManager (dialogs), TuiAnimationManager (breathing/spinners), SubagentDisplayManager, widgetsUI/Ansi/— Pure ANSI fallback: AnsiRenderer, MarkdownToAnsi (with Handler/ for table/list extraction), AnsiTableRendererUI/Diff/— Unified diff rendering with word-level highlightingUI/Theme.php— Shared color palette, tool icons, context barUI/AgentDisplayFormatter.php— Shared agent display utilities (used by both renderers)UI/AgentTreeBuilder.php— Builds agent tree from orchestrator stats
src/Tool/— Tool implementations inCoding/, permission system inPermission/src/Command/— AgentCommand (main REPL), SetupCommand, slash commands inSlash/src/Session/— SQLite persistence: sessions, messages, memories, settingssrc/Task/— Task tracking system with tool integrations
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.
- 6d ago First seen · 107 lines · 1,496 tokens per session scan A 1d91f856a8fb
kosmokrator CLAUDE.md is an instructions file published in the GitHub repository OpenCompanyApp/kosmokrator (20 stars, last pushed 5d ago), licensed MIT. It adds 1,496 tokens to every session, about $0.0075 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).
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 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).
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.
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.
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.