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

@nhd2106/imitation-machine

v0.2.0

Published

Enterprise agentic SDLC plugin and CLI for OpenCode and Claude-style skill workflows

Downloads

395

Readme

@nhd2106/imitation-machine

Standalone enterprise agentic SDLC plugin and CLI. Install once and you have the full workflow — gates, personas, audit trail, monorepo impact tooling, intake decomposition, staged review, and the agentic CLI — without depending on any other plugin.

What you get:

  • Complete skill-driven workflow (brainstorm → plan → TDD → staged reviews → verify → release)
  • Hard gates (coverage / typecheck / security / spec / quality)
  • Verification-before-completion (agentic verify all)
  • Mono-repo impact tooling (agentic repo *)
  • Audit trail and plan approvals
  • Worktree lifecycle (agentic worktree create / cleanup-merged)
  • Persona orchestration (agentic orchestrate run --plan PLN-...)
  • Intake decomposition unique to this plugin: zoom-out, architecture-deepening, requirements-brief, issue-slicing, grill-me, prototype
  • Staged review unique to this plugin: review-specreview-qualityreview-securityreview-final

Prior art and inspiration: the discipline-shaping patterns in this plugin (RED-GREEN-REFACTOR, root-cause-first debugging, fresh-subagent-per-task review, evidence-before-completion) draw on community work like Superpowers and related skill libraries. The implementation is fully self-contained — no runtime dependency on any external plugin.

Quickstart

If you are trying this for the first time from a local checkout of this repository, start here.

From this source checkout, use ./bin/agentic unless you already installed agentic on your PATH.

  1. Install local dependencies first: bun install
  2. If you are contributing from this checkout, read CONTRIBUTING.md for the full repo-local setup and verification flow.
  3. Choose exactly one install target based on the client you use. Here, surface means the client or tool you are installing into, such as OpenCode or Claude.
    • OpenCode: ./bin/agentic install local --surface opencode
    • Claude: ./bin/agentic install local --surface claude
    • Codex: ./bin/agentic install local --surface codex (supported packaged local install surface)
  4. Check the current workflow mode: ./bin/agentic mode show
  5. Run the final verification gate: ./bin/agentic verify all
  • ./bin/agentic mode show tells you how strict the repo is configured to be.
  • ./bin/agentic verify all is the final "do the checks say this is ready?" command.

Tiny example workflow

Canonical final sequence:

1. Open a repo that opted into imitation-machine.
2. Load `using-agentic`.
3. Pick the process skill that matches the task (for example `plan` or `tdd`).
4. Do implementation and task-level `review-spec` / `review-quality`.
5. Run specialized checks/updates as needed: `review-security` / `@security`, `@qa`, `@docs`.
6. Run `./bin/agentic verify all` for fresh verification evidence.
7. Run `review-final` via `@reviewer-final`.
8. `@release` / PR / handoff (PR/release/handoff).

Skill-selection quickstart

| Bucket | Use these skills when... | | --- | --- | | Read-only intake | Use zoom-out for read-only orientation before planning or before implementation; no writes or implementation. Use architecture-deepening for read-only candidate discovery of shallow/deep modules, seams, dependencies, tests, and handoffs. Use grill-me, requirements-brief, or issue-slicing to clarify, synthesize, or draft issue slices without writes. Tracker publishing stays a separate opt-in workflow with explicit approval. | | Prototyping | Use prototype for approved disposable prototype work after intake; keep it not production implementation, not a TDD shortcut, and separate from production implementation. | | Implementation | Use plan, executing-plans, subagent-driven-development, or tdd once the work is approved. | | Review | Use review-spec, review-quality, review-security, and review-final for staged readiness checks. | | Delivery | Use verify, gate, pr, release, requesting-code-review, receiving-code-review, and finishing-a-development-branch. | | Workspace | Use repo, worktree, and commit for scoped impact, isolation, and verified commits. | | Debugging | Use systematic-debugging for unclear failures and dispatching-parallel-agents only for safe independent fanout. | | Governance | Use using-agentic, adr, and design for opted-in workflow, architectural decisions, and UI direction. |

Contributing

Contributors working from this repo checkout should start with CONTRIBUTING.md for Bun setup, bounded change expectations, staged review order, and local verification commands. Pull requests in this repo also use the checked-in pull request template.

2-minute mental model

using-agentic is the entry skill. It does not do the work itself. It tells the agent, "this repo opted into the workflow, so load the right process skill before you start making changes."

In plain language:

  • using-agentic appears first when a repo wants the full workflow discipline.
  • Skills: reusable workflow or policy packages such as using-agentic, plan, tdd, and verify.
  • Personas: roles or subagents used during execution and review, such as a planner, coder, or reviewer.
  • Planner persona: appears when the task needs a plan or clearer execution steps.
  • Coder persona: appears when a bounded implementation task is ready to be done.
  • Reviewer personas: appear after implementation to check spec fit, quality, and sometimes security.
  • verify skill: appears at the end to gather fresh evidence before anyone says the work is complete.

Modes are just how much guardrail you want:

  • lite: the most relaxed; useful when you want lighter workflow enforcement
  • standard: the normal default; some workflow discipline, but not the strictest path
  • strict: the most locked down; load the right workflow skill before doing real work

The core idea is simple: start with using-agentic, let the matching workflow skill drive the task, and finish with verification.

Current status

Ships now

imitation-machine ships a broad workflow surface plus bounded behavioral evaluation for:

  • workflow entry and execution (using-agentic, plan, executing-plans, tdd, subagent-driven-development)

  • review and release flow (requesting-code-review, receiving-code-review, review-spec, review-quality, review-final / @reviewer-final, review-security, pr, release, finishing-a-development-branch)

  • repo/workspace discipline (repo, worktree, gate, verify, commit, adr)

  • clarification, intake, debugging, design, and coordination (zoom-out, architecture-deepening, grill-me, requirements-brief, issue-slicing, systematic-debugging, prototype, design, dispatching-parallel-agents, writing-skills)

  • approved disposable prototype work that is not production implementation and not a TDD shortcut

  • read-only architecture-deepening candidate discovery for shallow/deep module candidates, seams, dependency categories, behavior-protecting tests, risks/tradeoffs, and handoffs

  • tracker publishing remains separate opt-in work with explicit approval; read-only intake skills do not publish tracker updates

  • strong workflow breadth and review/release specialization

  • bounded OpenCode and Claude harness coverage

  • trigger, explicit-request, and multi-turn fixture coverage across the main workflow skills

Remaining gaps

  • systematic-debugging depth
  • requirements-brief / issue-slicing enrichment

Install

Published package assets include the agentic launcher, local install helper scripts, packaged plugin assets, and the skills/ tree.

Use this table as the single install hub:

| Client | Recommended path | Manual fallback | Exact instructions | Support status / notes | | --- | --- | --- | --- | --- | | OpenCode | ./bin/agentic install local --surface opencode | ./scripts/install-local-opencode.sh | .opencode/INSTALL.md | Supported packaged local install from this repo via plugin + skills. | | Claude | ./bin/agentic install local --surface claude | ./scripts/install-local-claude-plugin.sh | CLAUDE_INSTALL.md | Supported packaged local install from this repo via Claude development marketplace. | | Codex | ./bin/agentic install local --surface codex | ./scripts/install-local-codex.sh | CODEX_INSTALL.md | Supported packaged local install from this repo via a minimal Codex plugin root and local marketplace entry; no hooks, no mcpServers, no apps, no agents support, and no bootstrap injection; no live Codex harness claim. | | Cursor | Not currently supported | None | See notes in this table | No packaged installer or verified install flow in this repo today. | | Gemini | Not currently supported | None | See notes in this table | No packaged installer or verified install flow in this repo today. |

If the CLI is already on your PATH, the equivalent install commands are agentic install local --surface opencode, agentic install local --surface claude, and agentic install local --surface codex.

For OpenCode, the packaged local install from this repo creates a local package layout under ~/.config/opencode/imitation-machine/, registers the plugin in ~/.config/opencode/plugins/, and exposes the skills in ~/.config/opencode/skills/imitation-machine/.

OpenCode plugin dangerous git guardrails apply only to the OpenCode plugin behavior, not Claude or Codex. The guardrail blocks high-risk/destructive git commands such as hard reset, force clean, force branch delete, checkout/restore all paths, and force push; normal git inspection (git status, git diff, git log) and non-force push/PR flows remain available under the usual bash permission/policy prompts. This is not a complete shell sandbox and not a replacement for human review.

For Claude, the packaged local install from this repo registers a local Claude Code development marketplace and installs imitation-machine as a real plugin. If you also want loose local skills while iterating, CLAUDE_INSTALL.md includes the optional ./scripts/install-local-claude.sh step.

For Codex, the packaged local install from this repo creates ~/plugins/imitation-machine, copies this repo's skills/ directory into ~/plugins/imitation-machine/skills, and manages ~/.agents/plugins/marketplace.json with a local ./plugins/imitation-machine entry. The checked-in manifest stays minimal: no hooks, no mcpServers, no apps, no agents support, and no bootstrap injection, and no live Codex harness claim.

./bin/agentic install local and ./bin/agentic install local --surface all now install OpenCode, Claude, and Codex in that stable order.

Published registry install guidance, when available for a surface, is documented separately from the packaged local install flow above.

Do not rely on the package name alone for local development.

Source repo / developer-only verification

Repo-only contributor assets include checked-in tests/, harness scripts, and other verification helpers used from a source checkout.

The commands and paths below are for contributors working from this source repository checkout.

For fast bounded transcript/unit coverage across both surfaces in this repo checkout, run bun run test:harness.

For the reusable executable workflow regression lane in this repo checkout that scaffolds a temporary Bun repo, seeds an approved single-task plan, runs a real failing-test-to-passing-test flow, and validates transcript/review/verification evidence, run bun run test:workflow-harness or bun scripts/executable-workflow-harness.ts.

For OpenCode-only live bounded checks in this repo checkout that replay a checked-in manifest through opencode run --print-logs, including continued multi-turn scenarios that use --continue, run bash tests/opencode/run-tests.sh live. Set OPENCODE_LIVE=1 to execute real sessions; otherwise the live harness skips cleanly.

For the opt-in installed OpenCode integration lane in this repo checkout that scaffolds one cli-service temp repo and runs a bounded 3-turn session (opencode run --print-logs, then two opencode run --print-logs --continue calls in the same repo), run bun run test:opencode:installed (or bash tests/opencode/run-tests.sh installed). The happy path requires fresh review-spec, review-quality, and bun test evidence after each later write. Set OPENCODE_INSTALLED_LIVE=1 to execute the real session; otherwise it skips cleanly.

For the opt-in installed Claude integration lane in this repo checkout that scaffolds a docs-review temp repo and runs one bounded 3-turn session (claude --print, then two claude --print --continue calls in the same temp repo), run bash tests/claude-code/run-tests.sh installed. The happy path requires fresh review-spec, review-quality, and bun test evidence after each later write. Set CLAUDE_INSTALLED_LIVE=1 to execute the real session; otherwise it skips cleanly.

For focused Codex installer verification in this repo checkout, run bun run test:codex. That lane executes the real installer against a temp CODEX_AGENTS_DIR, asserts ~/plugins/imitation-machine/.codex-plugin/plugin.json is installed, and confirms the copied installed skills directory contains the packaged skills. Details and current Codex limits live in tests/codex/README.md.

For surface-specific commands, coverage details, and slower integration-oriented checks in the source repo, use the per-surface guides in tests/opencode/README.md, tests/claude-code/README.md, and tests/codex/README.md.

OpenCode verification

Installed-user verification

After running the packaged local install from this repo, verify in an OpenCode session:

opencode run --print-logs "use skill tool to list skills and load using-agentic"

In logs, confirm:

  • plugin path ~/.config/opencode/plugins/imitation-machine.js loaded
  • service=skill initialized
  • using-agentic listed and loadable
  • other imitation-machine skills such as gate, verify, worktree, and repo appear

If skills do not appear, first re-run ./bin/agentic install local --surface opencode. If that still fails, inspect ~/.config/opencode/plugins/imitation-machine.js and ~/.config/opencode/skills/imitation-machine, then restart OpenCode.

Repo-checkout / plugin-development verification

The commands below are source-checkout verification helpers for contributors working in this repository. They are not end-user package install steps.

The bounded OpenCode transcript harness, including the env-gated live runner, is documented in tests/opencode/README.md.

CLI

./bin/agentic install local
./bin/agentic install local --surface all --dry-run
./bin/agentic install local --surface opencode
./bin/agentic install local --surface claude
./bin/agentic install local --surface codex
./bin/agentic --help
./bin/agentic mode show
./bin/agentic mode lite
./bin/agentic mode standard
./bin/agentic mode strict
./bin/agentic mode clear
./bin/agentic verify all
./bin/agentic worktree --help
./bin/agentic worktree cleanup-merged --json
./bin/agentic check-plugin --json
./bin/agentic orchestrate run --plan PLN-xxxx --dry-run
./bin/agentic orchestrate run --plan PLN-xxxx --max-parallel 3 --continue-on-error
./bin/agentic orchestrate status --plan PLN-xxxx --json

Project mode resolution

imitation-machine resolves policy mode in this order:

  1. per-project override set with ./bin/agentic mode lite|standard|strict
  2. repo default from .imitation-machine.json
  3. fallback standard

Repo defaults live in the repo:

{
  "mode": "standard"
}

Per-project overrides are stored outside the repo, keyed by project path, and remain in effect until ./bin/agentic mode clear.

The OpenCode bootstrap now prints the resolved mode and whether it came from override, repo-config, or fallback.

Small flow example:

./bin/agentic mode show
./bin/agentic mode strict
./bin/agentic mode show
./bin/agentic mode clear
./bin/agentic mode show

Mode semantics in v1:

  • lite: relaxes the pre-workflow guard after bootstrap; bash and file writes are allowed without an implementation workflow skill
  • standard: current default behavior; bash allowed after bootstrap, writes still require a workflow skill
  • strict: requires a workflow skill before bash or file writes

Harness verification

This section documents source-repo/developer-only harness assets.

For fast bounded coverage plus surface-specific and integration-oriented guidance in this repo checkout, use tests/opencode/README.md and tests/claude-code/README.md.

The source repo also includes a checked-in live scenario manifest at tests/opencode/live-scenarios.json and a bounded live runner at scripts/opencode-live-harness.ts.