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

@dot-agent/cli

v0.12.0

Published

CLI toolkit for building, packaging, and executing deterministic FSM-based agents

Downloads

572

Readme


An agent is a folder: a .description manifest, a .behavior state machine, an optional persona, and the knowledge it teaches. This CLI turns that folder into a single portable .agent file, and runs one back.

$ npm install -g @dot-agent/cli
$ mkdir my-agent && cd my-agent
$ dot-agent init --name my-agent --domain example.com
✓ Scaffolded agent project in /tmp/my-agent
  Files: LICENSE, README.md, SOUL.md, agent.behavior, agent.description,
         behaviors/.gitkeep, guides/.gitkeep, knowledge/.gitkeep

$ dot-agent pack --dir . --out my-agent.agent
✓ Packed → my-agent.agent
  ID: example.com/my-agent
  Warnings: 1
⚠ agent.description:2:10 W003 domain still has default value "example.com"

The warning is the point: pack lints before it writes, so a broken agent fails at authoring time rather than at run time.

Install

npm install -g @dot-agent/cli

Or run it without installing:

npx @dot-agent/cli <command>

Commands

| Command | What it does | |---|---| | dot-agent init [--name <name>] [--domain <domain>] [--dir <dir>] [--force] | Scaffold an agent project | | dot-agent pack [--dir <dir>] [--out <file>] [--version <tag>] [--commit <hash>] | Lint and package into a .agent archive | | dot-agent unpack <file.agent> [--out <dir>] [--force] | Extract an .agent back to editable sources | | dot-agent run <file.agent \| dir> | Load an agent and start its state machine | | dot-agent run <src> --mcp | Serve a loaded agent over MCP | | dot-agent run --helper | Serve the interactive authoring helper over MCP | | dot-agent configure --claude | Install the native Claude Code plugin and remove any legacy MCP entries this CLI wrote before | | dot-agent configure [--gemini] [--agy] [--murici] [--skill] [--mcp] | Write the skill file and/or MCP config directly, for hosts with no dot-agent plugin (yet) | | dot-agent server-mcp | Serve the authoring tools over MCP | | dot-agent agents list · agents path <name> | List installed agents, or resolve one to a path |

The MCP commands take --mcp-transport stdio|http and --mcp-port <n>.

init writes into the current directory unless you pass --dir. It refuses to start when any file it would write already exists — naming every collision at once, before writing anything — so pointing it at a populated folder is safe. Pass --force to overwrite them deliberately.

Without --version, pack prompts for one in a terminal and packs versionless otherwise; it never invents a default.

Use as a library

Every command is also an exported function, for embedding in a Node or Electron host:

import { pack, run } from '@dot-agent/cli'

const packed = await pack({ dir: './my-agent', out: './my-agent.agent' })
console.log(packed.id, packed.path, packed.warnings.length)

const { bundle, session } = await run({ source: './my-agent.agent' })

Also exported: init, unpack, configure, listAgents, getAgentPath, startDevMcpServer, and the AgentBundle / PackResult / LintMessage types.

Writing an agent

The .description and .behavior formats, the memory model and the full lint-code list are the language specification, not CLI surface:

Or let the CLI teach you interactively: dot-agent run --helper starts an agent whose whole purpose is explaining how to write one.

Requirements

Node.js 24 or newer.

License

Copyright (c) 2026 Danilo Borges. Licensed under the Apache License 2.0 — see LICENSE.