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

@fleettools/opencode-plugin

v1.2.0

Published

FleetTools OpenCode Plugin - AI Agent Coordination System

Readme

FleetTools OpenCode Plugin

Integrates FleetTools CLI functionality into OpenCode using a tools-first approach.

Installation

Add this plugin to your OpenCode config:

{
  "plugin": ["@fleettools/opencode-plugin"]
}

After restarting OpenCode, the plugin will provide tools for FleetTools management.

Initial Setup

First time users: Run the setup command to create OpenCode command files:

/fleet_opencode_setup

This creates .opencode/commands/fleet.md and subcommand files for easier access.

Available Tools

🔧 fleet_opencode_setup

Create OpenCode command files for FleetTools (run once)

Parameters:

  • projectPath (optional, string) - Project path (defaults to current directory)
  • overwrite (optional, boolean) - Overwrite existing command files

📊 fleet_status

Get FleetTools service status and configuration

Parameters:

  • format (optional, enum: text|json, default: text) - Output format

🚀 fleet_start

Start FleetTools services

Parameters:

  • services (optional, array: api,squawk) - Services to start (default: all enabled)

🛑 fleet_stop

Stop FleetTools services

Parameters:

  • services (optional, array: api,squawk) - Services to stop (default: all running)
  • force (optional, boolean) - Force stop without graceful shutdown
  • timeout_ms (optional, number) - Timeout for graceful shutdown (ms)
  • json (optional, boolean) - Output in JSON format

🩺 fleet_doctor

Check FleetTools installation and configuration

Parameters:

  • fix (optional, boolean) - Attempt to fix common issues automatically

⚙️ fleet_setup

Initialize FleetTools configuration

Parameters:

  • global (optional, boolean) - Setup global configuration only
  • setup_force (optional, boolean) - Force re-initialization

🔍 fleet_services

Manage FleetTools services

Parameters:

  • args (optional, string) - Arguments to pass to fleet services command

📝 fleet_help

Show FleetTools help and usage

Parameters:

  • args (optional, string) - Additional help arguments

🧠 fleet_context

Get compact FleetTools state for context/memory

Parameters:

  • verbose (optional, boolean) - Include detailed information

Usage Examples

After running fleet_opencode_setup once, you can use slash commands:

# Check FleetTools status
/fleet status

# Start services
/fleet start

# Stop services  
/fleet stop

# Get help
/fleet help

# Doctor check
/fleet doctor

# Check services
/fleet services

Or use tools directly:

# Get status in JSON format
fleet_status --format json

# Force stop with timeout
fleet_stop --force true --timeout_ms 5000

# Auto-fix issues
fleet_doctor --fix true

Memory Features

The plugin automatically injects FleetTools context:

  • Session start: Provides FleetTools state snapshot
  • Session compaction: Preserves FleetTools guidance across compactions

This prevents repeated setup/context loss during long conversations.

Requirements

  • OpenCode >= 1.0.0
  • FleetTools CLI (must be available in PATH)
  • Node.js >= 18.0.0
  • Bun >= 1.0.0 (for building)

Development

cd plugins/opencode
bun run build    # Compile TypeScript
bun test         # Run tests

License

MIT License - see LICENSE file for details.