hmem-new-project

hmem-new-project is a skill for Claude Code, Codex from Bumblebiber/hmem. It costs 65 tokens per session (917 once invoked), scanned A, original, MIT.

A procedure for creating a new project record in hmem, including its basic details, codebase information, and linked session entry.

In plain words
What is it for?
Use it when registering a project, documenting its technology and goal, linking its repository, or preparing it for stored project memory.
Why use it?
It ensures new projects use the expected structure and contain enough information for later coding-agent sessions.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions CLAUDE.md; mentions subagents.

Good fit Use it when registering a project, documenting its technology and goal, linking its repository, or preparing it for stored project memory.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/bumblebiber/hmem/hmem-new-project
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.

Any agent
npx skills add Bumblebiber/hmem --skill hmem-new-project
Clone the repo
git clone --depth 1 https://github.com/Bumblebiber/hmem

Made for: Claude Code, Codex.

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 hmem-new-project

README.md
[![agentmods](https://agentmods.dev/badge/skills/bumblebiber/hmem/hmem-new-project/github.svg)](https://agentmods.dev/skills/bumblebiber/hmem/hmem-new-project)
Your own site
<a href="https://agentmods.dev/skills/bumblebiber/hmem/hmem-new-project"><img src="https://agentmods.dev/badge/skills/bumblebiber/hmem/hmem-new-project/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 hmem-new-project

Your own site · 80×15
<a href="https://agentmods.dev/skills/bumblebiber/hmem/hmem-new-project"><img src="https://agentmods.dev/badge/skills/bumblebiber/hmem/hmem-new-project.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 65 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 917 The whole file, excluding the scripts and references it only reads on demand.
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.00065 $0.00917
Opus 5 $0.00032 $0.00458
Sonnet 5 $0.00013 $0.00183
Haiku 4.5 $0.00006 $0.00092

Measured 9d ago against content hash 7a030f1d1312, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

hmem-new-project 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 9d 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.

skills/hmem-new-project/SKILL.md · 93 lines

How it starts

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

/hmem-new-project — New Project Entry

Uses the create_project tool to set up a complete project with one call.

Step 1: Does a codebase exist?

Ask:

"Gibt es bereits eine Codebase? Wenn ja, in welchem Verzeichnis?"

If yes: Scan the directory (README, package.json, CLAUDE.md, etc.) to extract name, tech stack, description, entry points, key modules. Use findings to fill the create_project parameters and later append Codebase details.

If no: All info comes from the user's answers.

Step 2: Quick questions (one at a time)

Ask these in order. Skip what the codebase scan already answered.

  1. Name — "Wie soll das Projekt heißen?"
  2. Stack — "Welche Technologien?"
  3. One-liner — "Beschreib das Projekt in einem Satz"
  4. Goal — "Was ist das Hauptziel?"
  5. Who — "Wer nutzt es?"
  6. Repo — "Repo-Pfad oder URL?"
  7. Deployment — "Wie wird es deployed?"

Stop early if the user says "reicht" or "das war's".

Step 3: Create the project

create_project({
  name: "...",
  tech: "...",
  description: "...",
  goal: "...",
  repo: "...",
  audience: "...",
  deployment: "...",
  tags: ["#lang", "#framework"]
})

This creates:

  • P00XX with sections from the configured schema (or 9 R0009 defaults if no schema)
  • O00XX matching O-entry for session logging (if createLinkedO: true in schema, or always when no schema)

Step 4: Fill in details

If a codebase was scanned, append the findings. The Codebase node (.2) follows a strict schema:

Codebase node structure

  • L3 — Pipeline (first child): Data flow overview — entry → moduleA → moduleB → storage
  • L3 — Modules: One node per source file. Title = filename, body = purpose + src/file.ts
  • L4 — Functions: Under each module, one node per exported function/class. Title = full TypeScript signature, body = one-line description + src/file.ts
append_memory(id="P00XX.2", title="Pipeline", body="src/cli.ts → moduleA.ts → DB")
append_memory(id="P00XX.2", title="moduleA.ts", body="Core logic handler. src/moduleA.ts")
append_memory(id="P00XX.2.N", title="doThing(x: string): Promise<boolean>", body="Does the thing. src/moduleA.ts")

Read the full file on GitHub · 93 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. 9d ago First seen · 93 lines · 65 tokens per session scan A 7a030f1d1312

Subscribe to this mod's changes

hmem-new-project is a skill published in the GitHub repository Bumblebiber/hmem (23 stars, last pushed 1mo ago), licensed MIT. It adds 65 tokens to every session and 917 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

nornweave-api

Give AI agents their own email inboxes using the NornWeave API. Use when building email agents, sending/receiving emails programmatically, managing inboxes, retrieving threads, searching messages, or integrating with email providers (Mailgun, SES, SendGrid, Resend). NornWeave provides LLM-ready markdown parsing and…

DataCovey/nornweave · 77 tokens

alice-open-loop-review

Use Alice open-loop MCP tools to review unresolved commitments and prioritize concrete next actions.

samrusani/AliceMemory · 21 tokens

jira-confluence-cli

Manage Jira issues and Confluence pages using the published mcp-jira-confluence npm package's one-shot CLI (invoked via npx -y mcp-jira-confluence@latest ; no separate bin). Search, read, create, update, comment on, and transition Jira issues; search, read, create, update, comment on, and inspect Confluence pages …

thamaraiselvam/mcp-jira-confluence · 217 tokens

setup-project

Onboards a new developer - explains the project, runs setup steps, verifies everything works.

berkcangumusisik/claude-code-practices · 20 tokens

fix-issue

GitHub issue numarasını alır, okur ve otomatik olarak çözer.

berkcangumusisik/claude-code-practices · 21 tokens

orchestrations

Pick and run a multi-phase workflow that chains foundational task skills (git-wrapup, release-and-publish, maintenance, field-test, setup, etc.) end-to-end. Routes user intent to a workflow file under workflows/ — greenfield builds, maintenance + release, field-test + fix, or known-work + release. Single source for…

cyanheads/pubmed-mcp-server · 159 tokens