agentmods.dev

clude CLAUDE.md

Repository-wide instructions for a project that includes a memory-focused npm software library, an autonomous social-media bot, web apps, a mobile app, and a server. They also define required project rules, staging practices, and agent skills.

In plain words
What is it for?
Use them when working anywhere in this repository, especially the SDK, bot, React and Vite web apps, Flutter mobile app, Express server, project rules, staging workflow, or required agent memory.
Why use it?
They tell coding agents which parts of the project exist and which rules, memory system, and workflows must be followed before making changes.

Instructions file

21 1mo ago A scan 2,501 tokens original MIT
View the source file sebbsssss/clude
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/sebbsssss/clude/claude-md
Clone the repo
git clone --depth 1 https://github.com/sebbsssss/clude
Per session 2,501 This file is loaded in full into every session.
When invoked 2,501 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.02501 $0.02501
Opus 5 $0.01251 $0.01251
Sonnet 5 $0.00500 $0.00500
Haiku 4.5 $0.00250 $0.00250

Measured 2d ago against content hash 60c1d62f0c5a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

clude 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 2d 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.

CLAUDE.md · 171 lines

How it starts

The opening of the file, as written. The whole thing — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Clude Bot

What This Repo Is

  1. npm SDK (clude) — persistent cognitive memory for AI agents. Consumers import Cortex and call recall/store.
  2. Autonomous bot — @Cludebot on X/Twitter, running 24/7.
  3. Web apps — apps/chat/ (user-facing) and apps/dashboard/ (admin). Independent React 19 + Vite + Tailwind v4 apps.
  4. Mobile app — apps/mobile/ Flutter app with Riverpod, GoRouter, Freezed.
  5. Server — apps/server/ Express backend on Railway.

Full details: rules/01-project-overview.md. All rules live in rules/ — read the relevant rule file before working in an area.

gstack

Use the /browse skill from gstack for all web browsing. Never use mcp__claude-in-chrome__* tools.

Available skills: /office-hours, /plan-ceo-review, /plan-eng-review, /plan-design-review, /design-consultation, /review, /ship, /browse, /qa, /qa-only, /design-review, /setup-browser-cookies, /retro, /investigate, /document-release, /codex, /careful, /freeze, /guard, /unfreeze, /gstack-upgrade.

Clude Memory (Required for ALL agents)

Clude is our product. Every agent MUST actively use it. The clude-memory MCP server is configured in .mcp.json.

Every heartbeat / conversation, you MUST:

  1. Store memories about your work: decisions made, findings, blockers, task outcomes, things learned. Use store_memory with source: "mcp:<your-role>" (e.g. mcp:ceo, mcp:lead-pm, mcp:researcher).
  2. Recall memories when starting work on a topic you may have context on. Use recall_memories before diving in.
  3. Minimum 1 memory per heartbeat where you do meaningful work. More is better.

Memory type guide:

  • episodic — events, task completions, meetings, incidents
  • semantic — facts, knowledge, architecture decisions, team info
  • procedural — how-to knowledge, workflows, patterns that work
  • self_model — reflections on your own performance, strengths, gaps

Always include: meaningful tags, importance (0-1), and summary. This is our product — dogfood it seriously.

Read the full file on GitHub · 171 lines

Changes

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.

  1. 2d ago First seen · 171 lines · 2,501 tokens per session scan A 60c1d62f0c5a

Subscribe to this mod's changes

clude CLAUDE.md is an instructions file published in the GitHub repository sebbsssss/clude (21 stars, last pushed 1mo ago), licensed MIT. It adds 2,501 tokens to every session, about $0.0125 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-30.

Backend and APIsFrontendMemory and context
Related

Other instructions, from other repositories

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.

github/spec-kit · 7,104 tokens

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).

microsoft/vscode · 6,785 tokens

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.

openai/codex · 5,182 tokens

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.

langchain-ai/langchain · 4,345 tokens

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).

microsoft/vscode · 5,001 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens