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

@inotives/agent-rig

v0.1.9

Published

Filesystem-first agent workspaces for Claude, Codex, OpenCode, and custom subscription tools.

Readme


What It Is

AgentRig is a TypeScript CLI tool for scaffolding a filesystem-first agent workspace into any project.

It creates a .agent-rig/ directory where agents, shared context, workflow records, findings notes, handoff logs, credentials, and launch instructions live. Markdown is the default workflow store. SQLite is available for larger projects and becomes the live source of truth after migration. AgentRig does not orchestrate AI APIs; users run subscription tools such as Claude, Codex, OpenCode, or custom tools directly.

The main idea is to provide a controllable and customizable engineering loop inside the project folder. You can use your existing Codex or Claude subscription to run the planner, worker, and reviewer workflow without moving project coordination into a separate hosted system.

Handoff logs are intended for cross-session resume notes when work stops midstream or a session closes after a meaningful milestone. They are not meant to duplicate normal planner, worker, or reviewer task flow, which should already live in phase docs, task files, code review notes, and task status changes.

The current MVP can scaffold a workspace, manage agents and credentials, install profile-declared skills, create fully briefed Markdown- or SQLite-backed tasks, run a Codex/OpenCode worker-reviewer loop, report live status, and serve a read-only task board.

Detailed maintainer and agent workflow instructions are in INSTRUCTIONS.md.

Core Model

AgentRig workspaces are ordinary project files:

.agent-rig/
├── _shared/        # context, workflow store, profiles, notes, handoff logs
├── .creds/         # gitignored local secrets
├── <agent>/        # agent.toml, instructions.md, context, skills, tools, runs
└── human/          # human approval, unblock, and override helpers

The default agent-rig init --yes workspace is a solo worker agent using codex. Interactive setup can scaffold solo, coder-reviewer, trinity, supervisor-worker, swarm, testing-reviewer, or custom patterns.

Fresh workspaces can select SQLite directly with agent-rig init --yes --workflow-store sqlite. Markdown remains the default.

Agent instructions start from editable profiles in .agent-rig/_shared/profiles/. Built-in profiles are planner, worker, reviewer, researcher, writer, and designer; custom profiles are plain Markdown files with YAML frontmatter.

Built-in profiles are maintained as templates under templates/profiles/. To start a new built-in profile in the repository, run:

npm run profile:create -- api-specialist

The generator creates the required metadata, standard instruction headings, and the default shared skills. Complete the profile before building or publishing AgentRig.

Dependencies

Required:

node >= 22
npm or npx

AgentRig is packaged as an npm CLI.

Installation

npm install -g @inotives/agent-rig
# or
pnpm add -g @inotives/agent-rig

Verify the CLI is available:

agent-rig --help

You can also run AgentRig without a global install:

npx @inotives/agent-rig --help

Setup

Run AgentRig from inside the project you want to scaffold:

cd path/to/your-project
agent-rig init

agent-rig init starts a setup interview and writes a .agent-rig/ workspace into the current project.

For the non-interactive MVP default, scaffold a solo worker agent using codex:

agent-rig init --yes

To start a fresh workspace with SQLite:

agent-rig init --yes --workflow-store sqlite

Or do the same through npx:

npx @inotives/agent-rig init --yes

After setup, validate the workspace:

agent-rig validate
agent-rig doctor
agent-rig agents
agent-rig status

AgentRig installs default shared skills during setup. To skip network skill installs in automation or tests:

AGENT_RIG_SKIP_SKILLS=1 agent-rig init --yes

For task lifecycle, workflow storage, worker-reviewer operation, and GitHub issue planning, see INSTRUCTIONS.md.

For a backup-first upgrade of an existing deployment, see docs/upgrade-existing-deployment.md.

Local Task Board UI

Start the read-only task board from the project whose workflow state you want to inspect:

agent-rig ui
# open http://127.0.0.1:8787 in a browser

The UI binds to localhost only and uses port 8787 by default. Select another port with agent-rig ui --port 9000; the command prints the listening URL and does not open a browser automatically. The board reads the active workflow provider and never mutates tasks or handoffs. Use the agent-rig tasks ... commands for all workflow changes.

The board has two pages.

  • The landing page lists the phases as cards. Each card shows the phase name, an active or complete badge, a progress bar with "N of M done", chips for the non-zero status counts, the time of the last update, and a Detail button. Phases with open work come first. The Unassigned card is last.
  • The phase view shows the task flow of one phase. The header has a breadcrumb ("All phases / Phase 25"), the state badge, and the progress. The page has graph search, status and agent filters, Collapse done, a task side panel, and a searchable handoff timeline with a handoff modal.

The landing page loads only the phase summaries. The phase view loads only the tasks of its phase. The graph shows only the tasks of the phase. A task with dependencies in other phases shows an "N external" marker. The task panel lists each external dependency with its phase. A click on it opens that task in its own phase view. Both pages support light and dark themes.

| URL | Page | |---|---| | #/ | Landing page with phase cards. | | #/?phase=<phase> | Phase view, for example #/?phase=phase-25. | | #/tasks/<id>?phase=<phase> | Task panel inside its phase view. | | #/tasks/<id> | The UI reads the phase of the task, then opens the task in its phase view. |

An unknown phase shows a "phase not found" message with a link back to the landing page.

The UI reads these endpoints:

| Endpoint | Response | |---|---| | GET /api/phases | One summary per phase: counts by status, total, and the latest update. No task rows. | | GET /api/workflow?phase=<phase> | The tasks of one phase, with depends_on. An unknown phase returns 404. | | GET /api/tasks/<id> | One task with its details. | | GET /api/tasks/<id>/handoffs | The handoffs of one task. |

GET /api/workflow without phase still returns all tasks. The UI does not call it.

The frontend is packaged as static assets. From a repository checkout, npm run build compiles TypeScript and then runs Tailwind to generate dist/ui.css, copies src/ui/core/ui.html to dist/index.html, and emits the frontend bundle used by the server. Run npm install before the first build so the local Tailwind executable is available; installed packages serve the already-built assets and do not build frontend dependencies at runtime.

Common Commands

| Command | Purpose | |---|---| | agent-rig init | Run the setup-pattern interview and scaffold .agent-rig/. | | agent-rig init --yes | Scaffold a solo worker using codex with Markdown storage. | | agent-rig init --yes --workflow-store sqlite | Scaffold a solo worker with a fresh SQLite workflow store. | | agent-rig add <agent-name> | Add an agent to an existing workspace. | | agent-rig add <agent-name> --profile worker | Add an agent from an editable profile. | | agent-rig profiles | List available agent profiles. | | agent-rig profiles show worker | Print a profile Markdown template. | | agent-rig profiles update worker --agent worker | Preview a built-in profile update for one deployed agent. | | agent-rig profiles update worker --all --apply | Apply a built-in profile update to all matching agents and create backups. | | npm run profile:create -- designer | Create a partial built-in profile template in templates/profiles/. | | agent-rig doctor | Check local AgentRig environment and workspace health. | | agent-rig agents | List configured agents and tools. | | agent-rig validate | Validate workspace files without mutating them. | | agent-rig ui | Serve the read-only local task board at 127.0.0.1:8787. | | agent-rig ui --port <port> | Serve the read-only local task board on a custom port. | | agent-rig creds | Create credential placeholders and .env.example files. | | agent-rig skills | Install and list shared or agent-local skills. | | agent-rig status | Show live session state, task counts, loop observability, and recent handoffs. | | agent-rig start --agent <agent-name> | Print launch guidance plus relevant resume context for a configured agent. | | agent-rig tasks create "<title>" --body-file <path> | Create a fully briefed task in the active store. | | agent-rig tasks update-body <task-id> --body-file <path> | Replace a task brief through the active store. | | agent-rig tasks | List shared tasks. | | agent-rig tasks show <task-id> | Print the canonical task Markdown. | | agent-rig tasks next --agent <agent-name> | Print the next dependency-ready shared task for an agent. | | agent-rig tasks next --agent <agent-name> --claim | Mark the next dependency-ready shared task as in_progress. | | agent-rig tasks set-status <task-id> <status> | Update task lifecycle status. | | agent-rig tasks assign <task-id> <agent-name> | Assign a shared task to an agent. | | agent-rig tasks block <task-id> --reason <reason> | Mark a task blocked and record the blocker. | | agent-rig tasks done <task-id> | Mark a task done. | | agent-rig tasks handoff <task-id> ... | Record a manual handoff in the active store. | | agent-rig plan github-issue [<number>] | Discover open GitHub Issues or select one for planning. Discovery does not create tasks. | | agent-rig plan branch <number> | Create and publish the issue planning branch and print its compare link. | | agent-rig plan resume <number> | Resume an existing unapproved issue plan. | | agent-rig plan approve <number> | Record explicit human approval for an issue plan. | | agent-rig plan tasks <number> | Create dependency-gated workflow tasks after plan approval. | | agent-rig workflow migrate --to sqlite | Validate and migrate the Markdown workflow store to SQLite. | | agent-rig workflow import --from markdown | Import new unmarked Markdown records without overwriting SQLite. | | agent-rig workflow backup [--output <path>] | Create and validate a consistent read-only SQLite snapshot. | | agent-rig workflow rebuild [--replace --confirm "REPLACE SQLITE"] | Preview or guardedly rebuild SQLite from Markdown. | | agent-rig loop | Run the Codex/OpenCode worker-reviewer loop continuously. | | agent-rig loop --once | Run one Codex/OpenCode worker-reviewer loop tick and exit. | | agent-rig watch --once | Process one ready shared task and exit. |

Implementation Phases

The current implementation history is split into completed archived phases plus the capability-based structure work from Phase 20:

1. CLI scaffold
2. Workspace model and validation
3. Credentials and agent management
4. Live state and launch
5. First MVP watch loop
6. Pre-release and npm registry preparation
...
13. Worker-reviewer loop
14. OpenCode loop adapter
15. Loop observability
16. Pluggable workflow storage
17. Task board UI
18. SPA task board UI
19. DaisyUI task board refresh
20. Capability-based source structure

See docs/phases.

Development

Run the local checks:

npm run build
npm test
npm --cache /tmp/agent-rig-npm-cache pack --dry-run

npm run build is required when changing the UI source or packaging a release: it runs tsc and the Tailwind/DaisyUI static-asset build in scripts/build-ui.mjs.

For future phases, follow the planning and manager workflow in INSTRUCTIONS.md and AGENTS.md. Complete the final human end-to-end check before marking a phase complete.

Repository Layout

agent-rig/
├── docs/
│   ├── project_specs.md
│   ├── profiles.md
│   ├── _archived/
│   └── phases/
├── src/
│   ├── cli/
│   ├── workspace/
│   ├── profiles/
│   ├── workflow/
│   └── ui/
│       ├── core/               # routing, server, API, contracts, config
│       ├── common/             # shared UI components and helpers
│       └── pages/task-board/   # task board page and task detail behavior
├── templates/
├── test/
│   ├── ui/
│   └── integration/
├── AGENTS.md
├── README.md
└── LICENSE

License

Apache License 2.0. See LICENSE.