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 🙏

© 2025 – Pkg Stats / Ryan Hefner

agentic-cli

v0.1.9

Published

Modular AI agent system with specialized subagents and commands for enhanced OpenCode capabilities

Downloads

84

Readme

Agentic

npm version License: MIT

Modular AI agents and commands for structured software development with OpenCode.

What It Does

Agentic is a workflow management system for AI-assisted software development using OpenCode. It provides:

  1. Modular AI Agents & Commands: Pre-configured prompts and specialized subagents that enhance OpenCode's capabilities through task decomposition and context compression
  2. Structured Development Workflow: A phased approach (Research → Plan → Execute → Commit → Review) for handling tickets and features
  3. Knowledge Management: Organized "thoughts" directory structure for storing architecture docs, research, plans, and reviews
  4. Distribution System: A CLI tool to distribute agent/command configurations to projects via .opencode directories

Purpose

The system aims to:

  • Make AI-assisted development more systematic and reproducible
  • Reduce context window usage through specialized subagents
  • Maintain project knowledge over time (architecture decisions, research, implementation history)
  • Provide guardrails for AI agents through structured workflows

Quick Start

Installation

From npm (Recommended)

npm install -g agentic-cli
# or
bun add -g agentic-cli

From Source

git clone https://github.com/Cluster444/agentic.git
cd agentic
bun install
bun link  # Makes 'agentic' command available globally

Deploy to Your Project

cd ~/projects/my-app
agentic pull

This creates a .opencode directory with all agents and commands.

Development Workflow

  1. Create a ticket in thoughts/tickets/
  2. Use the research command to analyze the codebase from the ticket details
  3. Use the plan command to generate an implementation plan for the ticket using the research
  4. Use the execute command to implement the changes
  5. Use the commit command to commit your work
  6. Use the review command to verify the implementation

Between each phase it is important to inspect the output from each phase and ensure that it is actually in alignment with what you want the project do be and the direction it is going. Errors in these files will cascade to the next phase and produce code that is not what you wanted.

In OpenCode, these commands are invoked with a slash: /research, /plan, /execute, etc. In most cases you want to provide arguments that may simple by the filename of the ticket, reserach or plan to work with.

Important Notes

IMPORTANT: Between each phase you MUST review the outputs for correctness. This is YOUR job, not the model's. The system may produce working results, but that doesn't mean they are correct for your project. Quality input and review leads to quality output - the more care you put into early research and planning, the smoother the implementation will be!

Documentation

Getting Started

Core Components

Project Structure

Requirements

Contributing

This project is in active development. Contributions, ideas, and feedback are welcome!

License

MIT License - see LICENSE file for details