What is node-huckleberry-mcp CLAUDE.md?

Repository instructions for contributors to a TypeScript project called node-huckleberry-mcp. They point developers to the project’s architecture, task roadmap, conventions, security guidance, and required checks.

Use them when starting a task, choosing work from the roadmap, checking the Firebase and Firestore setup, or preparing a branch and pull request.

They provide one place to learn how the repository works and how changes should be made safely. They also clarify which build, lint, formatting, and test commands must pass.

How KenLSM/node-huckleberry-mcp configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to KenLSM/node-huckleberry-mcp. 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/KenLSM/node-huckleberry-mcp/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/KenLSM/node-huckleberry-mcp

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/kenlsm/node-huckleberry-mcp/claude-md/github.svg)](https://agentmods.dev/instructions/kenlsm/node-huckleberry-mcp/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/kenlsm/node-huckleberry-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/kenlsm/node-huckleberry-mcp/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/kenlsm/node-huckleberry-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/kenlsm/node-huckleberry-mcp/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 553 This file is loaded in full into every session.

When invoked 553 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.00553	$0.00553
Opus 5.5	$0.00221	$0.00221
Sonnet 5.5	$0.00111	$0.00111
Haiku 4.5	$0.00055	$0.00055

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

Security

Grade A, and why

node-huckleberry-mcp 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 · 43 lines

How it starts

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

CLAUDE.md

See AGENTS.md — the canonical contributor guide for this repo (architecture, conventions, how to pick up tasks, secrets/safety).

Quick orientation:

TASKS.md — the roadmap and source of truth for what to build, in what order, and which model tier to use per task.
docs/architecture.md — the verified auth/data mechanism, live Firebase config, Firestore schema, and the T0.2 decision (use the Firebase JS SDK).

Toolchain: TypeScript + oxc (oxlint + oxfmt) + Vitest — not ESLint/Prettier/Jest. Before committing run npm run build, npm run lint, npm run format, and npm test (all must pass). See AGENTS.md → Toolchain for details.

Branch hygiene: one concern per branch, one branch per PR — start each task from a fresh branch off main, and never bundle unverified work with verified work. See AGENTS.md → Git → Branch hygiene.

Note — we deviate from the Python reference; verify features ourselves

The Python projects (Woyken/py-huckleberry-api, bckenstler/py-huckleberry-mcp) are a reference for leads, not a spec to copy. They are themselves reverse-engineered and can be wrong, incomplete, or stale, and we have intentionally diverged (oxc/Vitest toolchain, lenient read models, a different tool surface, no active-session timers).

For any new feature, verify the real Huckleberry/Firestore behavior ourselves before trusting it — don't port a write shape or field name on the Python project's word. The loop:

Do the action in the official Huckleberry app.
Inspect the resulting Firestore document(s) — npm run inspect:schema.
Build the Zod model + op to the observed shape (not the Python one).
Prove it with a gated live round-trip (HUCKLEBERRY_ALLOW_WRITES=1).

Where the real backend disagrees with the Python port, follow the backend. See docs/discovery-plan.md for how we map the full API/Firestore surface, and TASKS.md → B5 for a known live-confirmed deviation (solids food tracking: the Python log_solids stores foods/reactions and a different custom-food doc shape than we currently write).

Read the full file on GitHub · 43 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 · 43 lines · 553 tokens per session scan A 4d25165ca505

Subscribe to this mod's changes

node-huckleberry-mcp CLAUDE.md is an instructions file published in the GitHub repository KenLSM/node-huckleberry-mcp (1 stars, last pushed 2mo ago), licensed MIT. It adds 553 tokens to every session, about $0.0022 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-31.

baby-sleep baby-tracker claude cursor firebase firestore

node-huckleberry-mcp CLAUDE.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
node-huckleberry-mcp CLAUDE.mdKenLSM/node-huckleberry-mcp	Instructions file	1	2mo ago	MIT	A	553	Claude Code
data-scientist copilot-instructions.mdrealnghon/data-scientist	Instructions file	2	4mo ago	MIT	A	373	GitHub Copilot
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	5,649	GitHub Copilot
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	today	MIT	A	4,680	Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	3,093	GitHub Copilot

node-huckleberry-mcp: Instructions file for Claude Code