init

A command that scans a project to identify its programming stack and saves the findings as Nemp memories. It checks common project files and reads `package.json` when available.

In plain words
What is it for?
Run `/nemp:init` when starting with a project so its frameworks, tools, lockfile, and basic structure can be recorded.
Why use it?
It avoids manually documenting the project setup and gives the memory system useful context for future work.

Command

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.

agentmods
npx agentmods add commands/sukinshetty/nemp-memory/init
Clone the repo
git clone --depth 1 https://github.com/SukinShetty/Nemp-memory
Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,977 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00009 $0.01977
Opus 5 $0.00005 $0.00988
Sonnet 5 $0.00002 $0.00395
Haiku 4.5 $0.00001 $0.00198

Measured 2d ago against content hash 12bc4ee52e31, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

init 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 2d 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.

commands/init.md · 233 lines

How it starts

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

/nemp:init

Intelligently scan your project and auto-save context as memories.

Instructions

You are an intelligent project analyzer. Scan the current project to detect its stack, then save the findings as Nemp memories.

Step 1: Lightweight Scan (Token Optimized)

IMPORTANT: Use minimal token consumption. Only read essential files. Run ONE combined check.

echo "=== FILES ===" && ls package.json tsconfig.json next.config.* vite.config.* nuxt.config.* astro.config.* svelte.config.* angular.json requirements.txt pyproject.toml Cargo.toml go.mod Gemfile docker-compose.* Dockerfile .env .env.local .env.example 2>/dev/null && echo "=== LOCKFILE ===" && ls package-lock.json yarn.lock pnpm-lock.yaml bun.lockb 2>/dev/null && echo "=== DIRS ===" && ls -d app pages src/app components/ui 2>/dev/null

DO NOT run multiple separate file-existence checks. One command, all checks.

Step 2: Read package.json ONLY (if exists)

IMPORTANT: This is the ONLY file you need to read for detection. DO NOT read README.md, .env files, or scan directories.

[ -f "package.json" ] && cat package.json

From package.json, detect everything using the tables in Step 3.

Step 3: Parse package.json

Detect Framework from dependencies or devDependencies:

Package Framework
next Next.js
react (without next) React (standalone)
@remix-run/react Remix
vue Vue.js
nuxt Nuxt.js
astro Astro
svelte Svelte
@sveltejs/kit SvelteKit
express Express.js
fastify Fastify
hono Hono
elysia Elysia (Bun)
@nestjs/core NestJS
koa Koa

Detect Language:

  • typescript in devDependencies → TypeScript
  • tsconfig.json exists → TypeScript
  • Otherwise → JavaScript

Detect Database/ORM:

Package Database/ORM
prisma or @prisma/client Prisma ORM
drizzle-orm Drizzle ORM
mongoose MongoDB (Mongoose)
pg PostgreSQL (node-postgres)
mysql2 MySQL
better-sqlite3 SQLite
@supabase/supabase-js Supabase
firebase Firebase
@planetscale/database PlanetScale
@neondatabase/serverless Neon
redis or ioredis Redis

Read the full file on GitHub · 233 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. 2d ago First seen · 233 lines · 9 tokens per session scan A 12bc4ee52e31

Subscribe to this mod's changes

init is a command published in the GitHub repository SukinShetty/Nemp-memory (128 stars, last pushed 2mo ago), licensed MIT. It adds 9 tokens to every session and 1,977 once invoked, about $0.0000 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.