What is plandb CLAUDE.md?

Project instructions for PlanDB, a Rust task-graph database with a command-line interface, API server, and SQLite storage. They cover development commands, branch rules, and commit naming.

Use them when developing PlanDB, running its Rust or functional tests, checking formatting, choosing a branch name, or preparing a commit.

They make the project's contribution process predictable and explain how to build, test, format, lint, and submit changes safely.

How Agent-Field/plandb configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to Agent-Field/plandb. 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/Agent-Field/plandb/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/Agent-Field/plandb

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/agent-field/plandb/claude-md/github.svg)](https://agentmods.dev/instructions/agent-field/plandb/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/agent-field/plandb/claude-md"><img src="https://agentmods.dev/badge/instructions/agent-field/plandb/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/agent-field/plandb/claude-md"><img src="https://agentmods.dev/badge/instructions/agent-field/plandb/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,173 This file is loaded in full into every session.

When invoked 1,173 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.

Model	Per session	Once invoked
Fable 5.1	$0.01173	$0.01173
Opus 5.5	$0.00469	$0.00469
Sonnet 5.5	$0.00235	$0.00235
Haiku 4.5	$0.00117	$0.00117

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

Security

Grade A, and why

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

CLAUDE.md · 128 lines

How it starts

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

PlanDB — Project Instructions

What This Is

PlanDB is "the issue tracker your AI agents are missing" — a task graph database (CLI + MCP + HTTP) that agents use to decompose work, parallelize, adapt mid-flight, and persist knowledge. Single Rust binary, SQLite-backed.

Development

cargo build            # build
cargo test             # unit tests (8 tests)
bash tests/functional_test.sh  # functional tests (7 scenarios)
cargo clippy           # lints
cargo fmt --check      # formatting

Rust 1.75+ required. No external dependencies — SQLite is bundled via rusqlite.

Branch Rules

main is protected: CI must pass, no force push, no branch deletion
All changes go through PRs (admin can bypass for hotfixes)
Branch naming: feat/, fix/, docs/, refactor/, ci/
Delete branches after merge

Commit Conventions

feat: new user-facing capability
fix: bug fix
refactor: code change that doesn't add features or fix bugs
docs: documentation only
ci: CI/CD changes
test: adding or fixing tests
chore: maintenance (deps, config, cleanup)

These prefixes drive automatic PR labeling via release-drafter.

Release Flow

Releases are intentional, not automatic. Every push to main runs CI but does NOT create a release.

How it works

PR merges to main
  → ci.yml runs (build, test, functional tests)
  → release-drafter updates a DRAFT release on GitHub (accumulates changes)

Ready to ship:
  → git tag v0.X.Y -m "description"
  → git push origin v0.X.Y
  → release.yml triggers:
      1. Runs full test suite
      2. Builds cross-platform binaries (linux x86/arm, macOS x86/arm, windows)
      3. Generates checksums
      4. Publishes GitHub release with auto-generated notes from the draft

Version bumping

Patch (v0.2.0 → v0.2.1): bug fixes, docs, refactors
Minor (v0.2.x → v0.3.0): new features
Major (v0.x → v1.0): breaking changes

The release-drafter auto-suggests the next version based on PR labels (feat: → minor, fix: → patch).

Read the full file on GitHub · 128 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.

2mo ago First seen · 128 lines · 1,173 tokens per session scan A 27bb046ff24b

Subscribe to this mod's changes

plandb CLAUDE.md is an instructions file published in the GitHub repository Agent-Field/plandb (111 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 1,173 tokens to every session, about $0.0047 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.

LLM Orchestration Rust ai-agents cli mcp

plandb CLAUDE.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
plandb CLAUDE.mdAgent-Field/plandb	Instructions file	111	1mo ago	Apache-2.0	A	1,173	Claude Code
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

plandb: Instructions file for Claude Code