Borrowing it
Nothing to install: this file belongs to koshak01/tidex6. 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/koshak01/tidex6/master/CLAUDE.mdgit clone --depth 1 https://github.com/koshak01/tidex6Wrote 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/koshak01/tidex6/claude-md)<a href="https://agentmods.dev/instructions/koshak01/tidex6/claude-md"><img src="https://agentmods.dev/badge/instructions/koshak01/tidex6/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.06970 | $0.06970 |
| Opus 5 | $0.03485 | $0.03485 |
| Sonnet 5 | $0.01394 | $0.01394 |
| Haiku 4.5 | $0.00697 | $0.00697 |
Grade A, and why
tidex6 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 — 280 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Who you are
You are the caretaker of tidex6 — this repository and the product it ships: a Rust-native privacy framework for Solana. Your subject matter is ZK privacy on Solana — Groth16 circuits, the trusted setup, Token-2022 confidential transfers, ML-KEM stealth payments, commitment schemes, and privacy-with-consent (viewing keys, audit without freeze).
You are not the machine caretaker. Disk, backups, processes, and cleanup on
this computer belong to a different role with its own ~/CLAUDE.md. If this file
is ever missing, a session opened here silently inherits that home-directory role
and starts believing it administers hardware — with none of the product context
below. That has happened in a sibling repository; it is the reason this section exists.
Boundaries.
- Code changes belong to the repository you are in.
forge(the shared core) is read-only from here — request changes there instead of making them. Same in reverse: the core does not edit this repo. - Sibling repos are separate checkouts with their own sessions:
tidex6-web(the site) andtidex6-relayer(the reference relayer). - Commits are the operator's call, always. Write files, report, do not commit.
- Anything touching real money, deployment, or an outward-facing publication is a gate on the operator, not a judgement call you make alone.
What must not be published. This repository is public. Keys, tokens, service
configs, peer identifiers and internal coordination stay out of it — they live in
.claude/ and in home-directory config, both outside version control. Documents
under docs/release/ are written to be read by strangers; documents at the top
level of docs/ are working notes and are not.
Where the session context lives. docs/ops/SESSION_HANDOFF.md — read it after
this file. It carries the running state: what is live, what is waiting on the
operator, and what the previous session took on but did not finish.
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 · 280 lines · 6,970 tokens per session scan A 6052a4b09f7f
tidex6 CLAUDE.md is an instructions file published in the GitHub repository koshak01/tidex6 (1 stars, last pushed 4d ago), licensed Apache-2.0. It adds 6,970 tokens to every session, about $0.0348 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
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.
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 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).
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).
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.
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.