Borrowing it
Nothing to install: this file belongs to rakovi4/continue-framework. 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/rakovi4/continue-framework/main/CLAUDE.mdgit clone --depth 1 https://github.com/rakovi4/continue-frameworkWrote 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/rakovi4/continue-framework/claude-md)<a href="https://agentmods.dev/instructions/rakovi4/continue-framework/claude-md"><img src="https://agentmods.dev/badge/instructions/rakovi4/continue-framework/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/rakovi4/continue-framework/claude-md"><img src="https://agentmods.dev/badge/instructions/rakovi4/continue-framework/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.00684 | $0.00684 |
| Opus 5.5 | $0.00274 | $0.00274 |
| Sonnet 5.5 | $0.00137 | $0.00137 |
| Haiku 4.5 | $0.00068 | $0.00068 |
Grade A, and why
continue-framework 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 1mo 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
TDD Framework Template — Clean Architecture backend (multi-module) + frontend + E2E acceptance tests.
Technology stack and commands are declared in ProductSpecification/technology.md. Read that file for build commands, test commands, and framework-specific conventions.
Architecture
application → adapters → usecase → domain
All backend modules live under backend/. Never place them in the project root.
| Module | Description | Dependencies |
|---|---|---|
backend/domain |
Entities, value objects, exceptions | None (code generation only) |
backend/usecase |
Application services, port interfaces | domain |
backend/adapters/rest |
Web controllers, auth | usecase |
backend/adapters/storage |
Database repositories, migrations | usecase |
backend/adapters/email |
Mail integration | usecase |
backend/application |
Entry point, wiring | all modules |
acceptance |
Black-box API tests (top-level) | None (HTTP + Selenium) |
Dependency flow is strictly inward. Never import from outer layers in inner layers.
The acceptance suite is also the current-state documentation of what the product does — read it (not a sweep of story folders) to learn how an area behaves today. Story folders are deltas plus their rationale. See .claude/rules/workflow.md, "Where the Current State Lives".
On-Demand Guidelines
The always-on rules (.claude/rules/*.md) hold only the high-level map, invariants, and safety guardrails. The per-topic detail is deferred to .claude/guidelines/ and is not auto-loaded — read the matching file before doing that kind of work.
| When you are about to… | Read first |
|---|---|
| Write or refactor any code (backend, frontend, tests, or helpers) | .claude/guidelines/coding-detail.md |
| Write or refactor frontend code or browser (Selenium/Cypress/Playwright) tests | .claude/guidelines/frontend-rules.md |
| Write or run TDD tests (red/green cycles, assertions, stop-on-failure) | .claude/guidelines/tdd-rules.md |
| Execute a scenario/task work unit (sequences, adapter-discovery, progress, resuming) | .claude/guidelines/workflow-detail.md |
| Start/stop services, touch CI runners, or run load tests | .claude/guidelines/infrastructure-detail.md |
| Edit prompt-library docs (agents/skills classification, structure) | .claude/guidelines/prompt-rules.md |
| Load or wire a technology binding (two-layer tech structure) | .claude/guidelines/technology-loading.md |
| Emit sub-agent progress to the live log | .claude/guidelines/agent-logging.md |
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.
- 1mo ago Changed · +6 tokens per session 061c17b22031
- 1mo ago Changed · -1 lines · -39 tokens per session 12e829746bd0
- 1mo ago First seen · 48 lines · 717 tokens per session scan A e298e3401d3d
continue-framework CLAUDE.md is an instructions file published in the GitHub repository rakovi4/continue-framework (54 stars, last pushed 29d ago), licensed MIT. It adds 684 tokens to every session, about $0.0027 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-09-03.
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.