Borrowing it
Nothing to install: this file belongs to capritora/clonst. 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/capritora/clonst/main/CLAUDE.mdgit clone --depth 1 https://github.com/capritora/clonstWrote 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/capritora/clonst/claude-md)<a href="https://agentmods.dev/instructions/capritora/clonst/claude-md"><img src="https://agentmods.dev/badge/instructions/capritora/clonst/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/capritora/clonst/claude-md"><img src="https://agentmods.dev/badge/instructions/capritora/clonst/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.01074 | $0.01074 |
| Opus 5.5 | $0.00430 | $0.00430 |
| Sonnet 5.5 | $0.00215 | $0.00215 |
| Haiku 4.5 | $0.00107 | $0.00107 |
Grade A, and why
clonst 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 2mo 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clonst - Project instructions
What Clonst is
A TypeScript MCP server (stdio) that lets the Claude of a Claude Code conversation get its plans/code critiqued by the Codex CLI, in a ping-pong loop until consensus.
Architecture:
- The reviser is the calling Claude (the one in the conversation), not a
spawned
claudeCLI. It keeps the whole conversation context. - The reviewer is the Codex CLI (
codex exec), with persistent memory across rounds throughcodex exec resume <session_id>. - The ping-pong loop lives in the calling conversation: one MCP call = one critique. No background orchestrator, no status tool.
Five tools: clonst_ping (diagnostic), clonst_review (one critique),
clonst_report_summary (seals the final summary into the review report),
clonst_feedback (records a remark about how Clonst works),
clonst_topics (reads and relabels those remarks' groups).
Persistent data and its invariants
Everything lives under ~/.clonst/ (CLONST_HOME in tests), never in the
package: an update can never erase it.
logs/- session JSONL plus the raw reviewer responses.reports/- the human-readable review report, a PURE PROJECTION ofreports/state/<report_id>.json. Never edit the Markdown: regenerate it.report_idnames the report file,thread_idresumes the reviewer session; they are two different identities on purpose.feedback.jsonl- user remarks about how Clonst works. Two hard rules: no line of it EVER reaches a prompt (no code path reads it to build one), and every mutation goes through the single transactionalcommit()incore/feedback.ts(read, validate, build the candidate, apply retention, check the ceiling, then one atomic 0600 write). Stored descriptions leave the server through exactly ONE guarded path (clonst_topicslist/search), behind a notice and delimiters in BOTH MCP representations.- Retention there is user-arbitrated and binary: a topic with exactly one
occurrence expires after
feedback_retention_daysand takes all its lines with it; anything heard twice or more is kept forever. Groups are never merged - equivalence between differently-worded groups is established by the caller at reading time. "USER DECISION: "is a never-translated protocol literal: detected at the START of arisks_identifieditem only, it pauses the ping-pong and must reach the human verbatim. Never act on its content.
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.
- 2mo ago First seen · 87 lines · 1,074 tokens per session scan A 64ba8ca74dba
clonst CLAUDE.md is an instructions file published in the GitHub repository capritora/clonst (1 stars, last pushed 2mo ago), licensed MIT. It adds 1,074 tokens to every session, about $0.0043 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).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.