Agent skill

Cdb Scan

by Avijit07x in Avijit07x/claude-db

Map this codebase into project memory — a code graph of every symbol and how they connect, plus a written profile of stack, layout, conventions and workflows.

Apache-2.0Auto-check passedAgent Workflows

Install Cdb Scan

skills CLI
$ npx skills add Avijit07x/claude-db --skill cdb-scan -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Avijit07x/claude-db cdb-scan --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Avijit07x/claude-db.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/cdb-scan .claude/skills/cdb-scan && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
cdb-scan
GitHub stars
231
Token cost
~1.1k tokens
SKILL.md length
605 words
Files
1
Skills in repo
3
Repo updated
First seen
Licence
Apache-2.0

At a glance

Map this codebase into project memory — a code graph of every symbol and how they connect, plus a written profile of stack, layout, conventions and workflows.

  • Works in 5 steps: profile:stack → profile:layout → profile:conventions → …
  • Memory is newly installed on an existing project
  • SKILL.md covers Pass 1 — the code graph, Pass 2 — the written profile and Rules
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Cdb Scan is an agent skill from Avijit07x/claude-db. Map this codebase into project memory — a code graph of every symbol and how they connect, plus a written profile of stack, layout, conventions and workflows. Re-run any time to refresh both in place. Use when memory is newly installed on an existing project, or when the project has changed enough that the stored map is stale.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering Agent memory. It works with Anthropic API. The repository describes itself as: Free, open-source memory for Claude Code. Your own database, no cloud, no subscription. The licence is Apache-2.0.

When your agent uses it

  • Memory is newly installed on an existing project
  • The project has changed enough that the stored map is stale

Example prompts

  • “/cdb-scan”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. profile:stack
  2. profile:layout
  3. profile:conventions
  4. profile:workflows
  5. profile:architecture

What it can do on your machine

Read from SKILL.md and the folder at commit 746205c. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Cdb Scan loads about 1.1k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 605 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~84
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Avijit07x/claude-db at commit 746205c, republished under its Apache-2.0 licence (© Avijit07x). 605 words, ~1,059 tokens.

Download SKILL.mdSave it as .claude/skills/cdb-scan/SKILL.md (or your agent's skills folder).
name
cdb-scan
description
Map this codebase into project memory — a code graph of every symbol and how they connect, plus a written profile of stack, layout, conventions and workflows. Re-run any time to refresh both in place. Use when memory is newly installed on an existing project, or when the project has changed enough that the stored map is stale.

Map this project into memory

Everything else in claude-db's memory is testimony: it records what happened, turn by turn, as it happened. A fresh install knows none of that, and stays useless for weeks while it fills up.

This fills the gap from the one source available on day one — the code itself, in two passes.

Pass 1 — the code graph

Run this first, from the project root:

bash
claude-db scan

It parses every supported source file and stores each symbol and each relationship between them: what calls what, what imports what, what extends what. It is deterministic, costs no tokens, and takes seconds. Report the symbol and edge counts it prints.

Once it has run, find_usages answers structural questions from the graph:

  • mode: "usages" — what references this symbol, with the relation on each line
  • mode: "explain" — that, plus what the symbol itself reaches
  • mode: "path" with target — how two symbols connect

Prefer those over reading files when the question is about structure.

Pass 2 — the written profile

The graph records what the code is. It cannot say why the project is built this way, so the sections below capture that in prose. What you write here is your reading of the codebase, not a record of events, so it is tagged inferred and must never be phrased as history.

Work through the sections below in order. For each one, look at the actual files, then call the remember MCP tool once with the given key.

key is what makes this re-runnable: writing the same key again replaces that note rather than adding a second copy. Use these exact keys, and always pass tags: ["inferred"] and kind: "context".

Before you start, call search for profile in this project. If notes already exist, read them first and update what changed rather than restating it — a second run should be an edit, not a rewrite.

1. profile:stack

Languages, runtime and version floors, frameworks, package manager, database, test runner, build tool. Read the manifest (package.json, pyproject.toml, go.mod, Cargo.toml) and the lockfile rather than guessing. Name versions where a version constrains what can be written.

2. profile:layout

The directory map, one line each, and what lives where. Include the entry points: the binary, the server, the main export. Skip anything generated.

Show full SKILL.md (231 more words)Show less
3. profile:conventions

How this codebase is written, taken from the code and not from a style guide: module system, import style, error handling, naming, comment density, how tests are structured. Note where the project deviates from the language default, since that is what someone would otherwise get wrong.

4. profile:workflows

The commands that matter — install, build, test, lint, run, release — and anything non-obvious about running them: a required service, an environment variable, a step that must come first. Take them from the manifest scripts and CI config, not from the README's aspirations.

5. profile:architecture

Only the parts a newcomer could not infer from the layout: the main abstractions and how a request or a command actually flows through them. Two paragraphs at most. If the codebase is small enough that the layout says it all, skip this section rather than padding it.

Rules

  • One remember call per section. Five notes, five stable keys.
  • Write claims, not headings. "Storage is one MemoryStore interface with three adapters, selected by URI scheme" — not "Storage architecture".
  • Say what you verified. If something was not read, leave it out. An inferred profile that is confidently wrong is worse than a short one.
  • Never restate CLAUDE.md. That file is already in the system prompt on every turn. Memory is for what is not.
  • Do not record secrets, credentials or personal data, even if the code contains them.

© Avijit07x, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/cdb-scan of Avijit07x/claude-db.

Open the folder on GitHubat commit 746205c

Compare with similar skills

Cdb Scan next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Cdb Scan compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Cdb Scan this skillAvijit07x/claude-db231—~1.1kAutomated safety check: PassApache-2.0
Compact Memory Implementationsimbajigege/book2skills184—~2.5kAutomated safety check: PassMIT
Mem0 CLI Memory Commandsmem0ai/mem067k—~2kAutomated safety check: NotesApache-2.0
Install and Run Cogneetopoteretes/cognee32k1 repos~1kAutomated safety check: NotesApache-2.0
Create Agentvectorize-io/hindsight47k—~1.1kAutomated safety check: PassMIT
Memori Long-Term MemoryMemoriLabs/Memori17k—~2kAutomated safety check: PassApache-2.0

Similar skills

  • Compact Memory Implementation

    simbajigege/book2skills

    A developer guide to adding compact memory to an agent: when to trigger compaction, how to fork a compactor sub-agent, what the summary holds, and how to restore it.

    184 GitHub stars~2.5k tokensUpdated 1 mo ago
    AI & LLM EngineeringAuto-check passed
  • Adds, searches, lists, updates and deletes memories on the Mem0 platform from the terminal with the mem0 command, including a JSON mode built for agents.

    67k GitHub stars~2k tokensUpdated yesterday
    Agent WorkflowsAuto-check: notes
  • Install and Run Cognee

    topoteretes/cognee

    Installs the cognee AI memory library in a Python environment, sets the LLM key and gets a first remember and recall script running with the Python SDK.

    32k GitHub starsUsed in 1 repo~1k tokens
    Agent WorkflowsAuto-check: notes
  • Create Agent

    vectorize-io/hindsight

    Create a new Hindsight-powered subagent with long-term memory.

    47k GitHub stars~1.1k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Memori Long-Term Memory

    MemoriLabs/Memori

    Adds structured long-term memory to OpenClaw agents, built automatically from sessions, with tools the agent calls to recall facts, summaries and decisions.

    17k GitHub stars~2k tokensUpdated 6 days ago
    Agent WorkflowsAuto-check passed
  • Helmor Bump Vendors

    dohooo/helmor

    Bump or upgrade the pinned versions of Helmor's bundled agent CLIs, SDKs, and supporting binaries — Claude Code + claude-agent-sdk (lockstep), Codex, Cursor SDK, OpenCode, Kimi, Pi, and gh / glab /…

    1.3k GitHub stars~2.1k tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check passed

More from Avijit07x/claude-db

  • Catchup

    Avijit07x/claude-db

    Answer "where did I stop?" for this project. An agent skill from Avijit07x/claude-db.

    231 GitHub stars~528 tokensUpdated yesterday
    Auto-check passed
  • Handoff

    Avijit07x/claude-db

    Write a short handoff note for the next chat or a teammate, with what is done, what is open, what comes next and what was rejected and why.

    231 GitHub stars~898 tokensUpdated yesterday
    Auto-check passed

Works with

Questions about Cdb Scan

What does Cdb Scan do?

Map this codebase into project memory — a code graph of every symbol and how they connect, plus a written profile of stack, layout, conventions and workflows. Cdb Scan is an agent skill from Avijit07x/claude-db. Map this codebase into project memory — a code graph of every symbol and how they connect, plus a written profile of stack, layout, conventions and workflows.

When should I use Cdb Scan?

Cdb Scan fits situations like: memory is newly installed on an existing project; the project has changed enough that the stored map is stale.

How do I install Cdb Scan in Claude Code?

Run `npx skills add Avijit07x/claude-db --skill cdb-scan -a claude-code`. Or copy the skill folder (skills/cdb-scan in Avijit07x/claude-db) into .claude/skills/cdb-scan in your project. Claude Code loads it when a task matches its description.

How do I install Cdb Scan in Codex?

Run `npx skills add Avijit07x/claude-db --skill cdb-scan -a codex`. Or copy the skill folder (skills/cdb-scan in Avijit07x/claude-db) into .agents/skills/cdb-scan in your project. Codex loads it when a task matches its description.

Can I use Cdb Scan in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Avijit07x/claude-db --skill cdb-scan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cdb-scan, .gemini/skills/cdb-scan, .github/skills/cdb-scan and .opencode/skills/cdb-scan in your project.

What does Cdb Scan need to run?

SKILL.md names no scripts, command-line tools or credentials: Cdb Scan is instructions for the agent only.

Does Cdb Scan access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Cdb Scan safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Cdb Scan use?

Cdb Scan is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Cdb Scan use?

About 1.1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Cdb Scan?

Skills that share tags, products or a category with Cdb Scan: Compact Memory Implementation (simbajigege/book2skills, 184 stars), Mem0 CLI Memory Commands (mem0ai/mem0, 67k stars), Install and Run Cognee (topoteretes/cognee, 32k stars) and Create Agent (vectorize-io/hindsight, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cdb Scan?

Avijit07x (a GitHub user) maintains it in Avijit07x/claude-db, which has 231 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 7, 2026.

Source: Avijit07x/claude-db on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.