npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

create-agentik

v0.2.4

Published

Scaffold an agentic-coding project: persistent memory, spec-driven workflow, and machine-enforced quality gates for Claude Code, Codex, Cursor and any AGENTS.md tool.

Readme

create-agentik

npm downloads license

Make AI coding agents reliable in any repo — in one command. Persistent memory, a spec-before-code workflow, and machine-enforced quality gates. Works with Claude Code, Codex, Cursor, and any AGENTS.md tool.

npm create agentik@latest my-app

That's it. Pick a profile, name it, done — the scaffolder does the structural work; your agent finishes setup.

demo

Why

Agents forget context between sessions, drift from conventions, and hallucinate APIs. Prose instructions don't fix that. Agentik ships three mechanisms that do:

  • Memory as files — current state, decisions (ADRs), conventions, domain.
  • Spec-driven workflow — every non-trivial task starts as a checkable spec.
  • Enforced gatespnpm verify (typecheck + lint + test) is the Definition of Done, run by a hook and in CI. Plus a zero-hallucination verification rule.

What you get

  • A web-frontend, fullstack, or generic profile — opinionated rules (TypeScript strict, zod validation, security, React 19, a11y) and skills.
  • Real configs shipped, not described: strict tsconfig, flat ESLint, Prettier, CI workflow.
  • Reversible by design — switch profiles or toggle any rule/skill later with /configure; nothing is ever deleted, just parked.
  • Personalizable — bring your own domain rules (rules/custom/) and business context with /customize; framework updates never clobber them.

Usage

# Interactive (recommended)
npm create agentik@latest

# Non-interactive / scripted (zero dependencies)
npm create agentik@latest my-app -- \
  --profile web-frontend --name "My App" --yes

# Options
#   --profile <web-frontend|fullstack|generic>   default: web-frontend
#   --name <name>        project name (default: directory name)
#   --layout <compact|classic> default: compact
#   --no-git             skip git init
#   --force              scaffold into a non-empty directory
#   -y, --yes            non-interactive (use flags + defaults)

New projects also get local scripts:

npm run agentik:update
npm run agentik:check

Already have a project? add

Drop the framework into an existing repo — it copies only framework files and never touches your code (package.json, src/, README stay yours):

cd my-existing-app
npm create agentik@latest add        # auto-detects a profile from your deps

It overlays a small root AGENTS.md bridge plus the framework internals under .agentik/: rules/skills, memory, the full config system (.agentik/framework.config.json, /configure, /customize, profiles), merges the gate scripts into your package.json (keeping any you already have), and applies a profile. Re-running is safe (skips files that exist). Then run /init-foundation.

It's smart about it. add inspects your project and proposes a setup, then asks you to confirm:

Smart detection
  Detected: Next.js, Prisma, TypeScript, vitest, ESLint, pnpm
  → profile: fullstack
  → gates:   typecheck=tsc --noEmit  lint=eslint .  test=vitest run
  → pm:      pnpm
Use this setup (profile: fullstack)?  (Y/n)

It picks the profile from your dependencies (Next/React/API/ORM-aware), reads your package manager from the lockfile, and wires the real gate commands it found (and adapts verify.sh to your package manager) — so there's almost nothing left to configure.

Keep it current: update

Refresh an adopted project without losing its knowledge or customizations:

cd my-project
npm create agentik@latest update -- --dry-run
npm create agentik@latest update
npm create agentik@latest update -- --layout compact  # migrate old classic installs

After Agentik is installed in a project, use the shorter local commands:

npm run agentik:update
npm run agentik:check

The command updates framework-owned rules, core skills, commands, profiles, scripts, and documentation. It preserves memory, specs, custom rules and skills, configuration, package.json, README, LICENSE, environment files, and application code. Existing disabled modules remain parked.

Compact Layout

New CLI installs default to compact layout:

AGENTS.md              root bridge for agent discovery
CLAUDE.md              root bridge for Claude Code
.agentik/              rules, skills, memory, specs, profiles, scripts, docs

AGENTS.md stays in the root intentionally because agent tools discover it there. The detailed framework files live in .agentik/ so adopted repos do not look cluttered. Agentik's own README, changelog, contributing guide, and license also live in .agentik/; the project root is left for the app/library itself. Canonical skills live in .agentik/skills/ for all agents; Claude compatibility mirrors live under .agentik/claude/skills/.

After create/add: open the project with your agent and run /init-foundation (or say "init") to wire the quality gates and capture your domain.

License

MIT