packmind: Instructions file for Claude Code

CLAUDE.md

packmind CLAUDE.md is an instructions file for Claude Code from PackmindHub/packmind. It costs 835 tokens per session, scanned A, original, Apache-2.0.

Repository guidance for coding agents working on Packmind, an Nx monorepo: one code repository containing multiple applications and shared packages.

In plain words
What is it for?
Use it when starting the Docker-based development environment or testing, linting, and building an application or shared package.
Why use it?
It maps the applications, packages, databases, cache, background jobs, and Nx commands, so developers know where code belongs and how to run checks locally.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md.

This is PackmindHub/packmind's own configuration. It tells Claude Code how to work on packmind itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything packmind configures →

Reuse

Borrowing it

Nothing to install: this file belongs to PackmindHub/packmind. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/PackmindHub/packmind/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/PackmindHub/packmind

Made for: Claude Code.

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

agentmods badge for packmind CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/packmindhub/packmind/claude-md/github.svg)](https://agentmods.dev/instructions/packmindhub/packmind/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/packmindhub/packmind/claude-md"><img src="https://agentmods.dev/badge/instructions/packmindhub/packmind/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.

agentmods 80×15 button for packmind CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/packmindhub/packmind/claude-md"><img src="https://agentmods.dev/badge/instructions/packmindhub/packmind/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 835 This file is loaded in full into every session.
When invoked 835 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00835 $0.00835
Opus 5.5 $0.00334 $0.00334
Sonnet 5.5 $0.00167 $0.00167
Haiku 4.5 $0.00084 $0.00084

Measured 1mo ago against content hash 28da2cdddf36, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

CLAUDE.md · 65 lines

How it starts

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

Nx Monorepo Structure

This is an Nx monorepo containing applications and reusable packages.

Core Technologies

  • Runtime: Node.js (version specified in .nvmrc)
  • Language: TypeScript
  • Database: PostgreSQL with TypeORM for entity persistence
  • Cache: Redis for caching
  • Background Jobs: BullMQ for job queue management
  • Testing: Jest with @swc/jest as test runner

Directory Structure

  • apps/ - Deployable applications (API, frontend, CLI, e2e tests, docs)
  • packages/ - Reusable domain and infrastructure packages shared across apps
  • .github/workflows/ - CI/CD pipelines for build, test, quality checks, and deployment

Local Development Environment

Local development uses Docker Compose to run all services (API, frontend, Redis, PostgreSQL). Docker Compose automatically provisions PostgreSQL and Redis - no manual setup required.

Working with Nx

The following commands apply for both NX apps and packages (use ./node_modules/.bin/nx show projects to list actual apps and packages.)

  • Test a project: ./node_modules/.bin/nx test <project-name>
  • Lint a project: ./node_modules/.bin/nx lint <project-name>
  • Build a project: ./node_modules/.bin/nx build <project-name>
  • Test affected projects: pnpm run test:staged
  • Lint affected projects: pnpm run lint:staged

Code Quality

  • Linting: ./node_modules/.bin/nx lint <project-name> runs ESLint, using the config file eslint.config.mjs.
  • Formatting: Prettier is used for code formatting. You don't have to run it, it's set as a pre-commit hook.

Commands

  • When running commands, ensure you use the correct Node version (see .nvmrc at the project's root level)
  • When renaming or moving a file that is commited to git, use git mv instead of mv
  • ensure the env variable PACKMIND_EDITION is properly set to oss
  • when asked to execute packmind-cli, use node ./dist/apps/cli/main.cjs
  • Some default skills use version-routed directories (packmind-versions/<version>/) and ask you to run packmind --version to pick the right one. Since you already run the local build with node ./dist/apps/cli/main.cjs, you always have the latest — skip the --version check and use the highest-numbered packmind-versions/ directory (currently 0.35.0 for both packmind-onboard and packmind-update-playbook). There is no next/ directory.

Read the full file on GitHub · 65 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. 1mo ago Changed · +1 lines 28da2cdddf36
  2. 1mo ago First seen · 64 lines · 835 tokens per session scan A 50a73faae4bd

Subscribe to this mod's changes

packmind CLAUDE.md is an instructions file published in the GitHub repository PackmindHub/packmind (319 stars, last pushed 4d ago), licensed Apache-2.0. It adds 835 tokens to every session, about $0.0033 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.

Related

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

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,786 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, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 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,680 tokens

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

microsoft/vscode · 2,731 tokens

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.

denoland/deno · 3,077 tokens