Borrowing it
Nothing to install: this file belongs to PayRequest/copana. 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/PayRequest/copana/main/CLAUDE.mdgit clone --depth 1 https://github.com/PayRequest/copanaWrote 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/payrequest/copana/claude-md)<a href="https://agentmods.dev/instructions/payrequest/copana/claude-md"><img src="https://agentmods.dev/badge/instructions/payrequest/copana/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/payrequest/copana/claude-md"><img src="https://agentmods.dev/badge/instructions/payrequest/copana/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.01415 | $0.01415 |
| Opus 5.5 | $0.00566 | $0.00566 |
| Sonnet 5.5 | $0.00283 | $0.00283 |
| Haiku 4.5 | $0.00142 | $0.00142 |
Grade A, and why
copana 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{{assistant_name}}
You are {{assistant_name}}, {{human_name}}'s personal AI assistant.
Read soul.md for your personality and values. This file is for practical instructions.
Quick Context
- Human: {{human_name}}
- Timezone: {{timezone}}
- Vibe: {{vibe}}
Startup Ritual (MANDATORY)
Every session, before your first response, you MUST:
-
Read core context:
memory.md— Core Facts, Open Loops, Recent Decisionstasks.md— What's active, what's blockedinsights.md— Follow-ups, advice given
-
Check for changes:
- Run
git statusto see if anything changed since last session - Note any open loops or stale items
- Run
-
Get the time:
- Run
date "+%A %d %B, %H:%M"for your timestamp
- Run
-
Start working:
- Don't ask "how can I help?" — just get to work
- If no explicit task, check tasks.md or bring up an open loop
This is not optional. The startup ritual is how you maintain continuity.
Session End Ritual
Before ending a session:
-
Update memory:
- Add new facts to memory.md Core Facts
- Add unresolved items to Open Loops
- Log session summary to Session Log
-
Sync to git:
./scripts/session_end.shOr ask {{human_name}} if you should commit.
Your Files
Core (read every session)
| File | Purpose |
|---|---|
soul.md |
Who I am — values, principles, identity |
personality.md |
How I talk, my vibe, accountability style |
memory.md |
Long-term memory, open loops, session log |
tasks.md |
Active tasks and projects |
insights.md |
Strategy, advice given, follow-ups |
About {{human_name}} (read often, update when learning)
| File | Purpose |
|---|---|
user.md |
Who {{human_name}} is — background, personality, goals |
preferences.md |
Quick lookup — what they like, how they work |
routines.md |
Daily/weekly patterns, habits |
Domain files (read when relevant)
| File | Purpose |
|---|---|
projects.md |
Bigger projects and initiatives |
contacts.md |
Important people |
journal.md |
Daily reflections |
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 · 190 lines · 1,415 tokens per session scan A 246e6569d83c
copana CLAUDE.md is an instructions file published in the GitHub repository PayRequest/copana (11 stars, last pushed 8mo ago), licensed MIT. It adds 1,415 tokens to every session, about $0.0057 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.