Borrowing it
Nothing to install: this file belongs to team-attention/tide. 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/team-attention/tide/main/CLAUDE.mdgit clone --depth 1 https://github.com/team-attention/tideWrote 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/team-attention/tide/claude-md)<a href="https://agentmods.dev/instructions/team-attention/tide/claude-md"><img src="https://agentmods.dev/badge/instructions/team-attention/tide/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/team-attention/tide/claude-md"><img src="https://agentmods.dev/badge/instructions/team-attention/tide/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.00633 | $0.00633 |
| Opus 5.5 | $0.00253 | $0.00253 |
| Sonnet 5.5 | $0.00127 | $0.00127 |
| Haiku 4.5 | $0.00063 | $0.00063 |
Grade A, and why
tide 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tide — Monorepo
This repo hosts two independent Tide products that share the brand but not code (different languages, separate builds). Pick the right app directory before working.
| App | Path | Stack | Build |
|---|---|---|---|
| Terminal (v1) | apps/terminal/ |
Rust + WGPU native macOS app | cargo (run from apps/terminal/) |
| Desktop (v2) | apps/desktop/ |
Electron + Node + React | npm (run from apps/desktop/) |
Before building, define the work
Whenever a request means creating or changing something — a feature, a fix, a refactor, anything you'd write code for — do not start until these three are explicit. They are the contract for the work:
- Goal — exactly what is wanted, as a concrete outcome, not a vague direction.
- Current state & gap — how it works today and precisely what's missing or wrong. If you can't state the gap, you don't understand the task yet.
- Verification scenario — the concrete steps that prove it's done: what you'll do, what you expect to see. If you can't name how you'd check it, you can't claim it works.
If any of the three is missing or ambiguous, ask before writing code — one focused round of questions to pin it down. Don't guess the goal, don't invent a gap, and don't build something you have no way to verify. Filling these in is the first step of the work, not overhead.
Rules
- Each app is self-contained. Its build files (
Cargo.toml/package.json), source, tests, docs, and scripts all live under its own directory. The repo root holds only brand-level files (README.md,LICENSE,assets/,.github/). - Never run a build from the repo root.
cd apps/terminalfor Rust,cd apps/desktopfor the Electron app. - No code is shared across the two apps (Rust ≠ TypeScript). If you ever share anything it is the process-boundary contract shape, mirrored per language.
- Each app has its own detailed instructions — read those before changing code:
apps/terminal/CLAUDE.md(+apps/terminal/AGENTS.md,apps/terminal/docs/)apps/desktop/docs_v2/and thetide-v2-planskill.
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 First seen · 53 lines · 633 tokens per session scan A 8dd3a779cef1
tide CLAUDE.md is an instructions file published in the GitHub repository team-attention/tide (76 stars, last pushed 10d ago), licensed MIT. It adds 633 tokens to every session, about $0.0025 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-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).
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).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.