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

@timps-ai/plugin-sdk

v0.1.1

Published

TIMPS plugin SDK — formal interface for extending TIMPS agents with custom commands, tools, and lifecycle hooks. Build plugins for AI coding workflows.

Readme

@timps-ai/plugin-sdk

Formal interface for extending TIMPS agents with custom commands, tools, and lifecycle hooks.

npm install @timps-ai/plugin-sdk

Usage

import { PluginRegistry, loadPlugin } from '@timps-ai/plugin-sdk'
import type { Plugin } from '@timps-ai/plugin-sdk'

const registry = new PluginRegistry()

// Register a plugin with manifest + handler maps
const myPlugin: Plugin = {
  manifest: {
    name: 'my-plugin',
    version: '1.0.0',
    description: 'Custom commands for my workflow',
    commands: [{ name: 'hello', description: 'Say hello', usage: '/hello <name>' }],
    tools: [{
      name: 'greet',
      description: 'Greet someone',
      parameters: { type: 'object', properties: { name: { type: 'string' } }, required: ['name'] }
    }],
    hooks: ['before:run', 'after:run'],
  },
  commands: {
    hello: async (args, ctx) => `Hello, ${args[0] || 'world'}!`
  },
  tools: {
    greet: async (params, ctx) => ({ output: `Hello, ${params.name}!` })
  },
  hooks: {
    'before:run': async (event, payload, ctx) => { console.log('Starting run...') },
    'after:run': async (event, payload, ctx) => { console.log('Run complete') }
  },
  setup: async (ctx) => { console.log('Plugin initialized') },
  teardown: async (ctx) => { console.log('Plugin cleaned up') },
}

registry.register(myPlugin)

// List registered plugins
console.log(registry.list())

// Resolve a command handler
const handlers = registry.resolveCommand('hello')
console.log(handlers[0].plugin.manifest.name)

// Get all tool specs + handlers
console.log(registry.allTools().length, 'tools registered')

// Load a plugin from a file (default export must be a Plugin object)
const filePlugin = await loadPlugin('./path/to/plugin.js')
registry.register(filePlugin)

Plugin Interface

| Property | Type | Required | Description | |----------|------|----------|-------------| | manifest | PluginManifest | ✅ | Static metadata (name, version, description, commands, tools, hooks) | | commands | Record<string, CommandHandler> | ❌ | Command name → handler mapping | | tools | Record<string, ToolHandler> | ❌ | Tool name → handler mapping | | hooks | Partial<Record<HookName, HookHandler>> | ❌ | Lifecycle hooks | | setup | (ctx: PluginContext) => Promise<void> | ❌ | Called once on activation | | teardown | (ctx: PluginContext) => Promise<void> | ❌ | Called once on deactivation |

Handler Signatures

type CommandHandler = (args: string[], ctx: PluginContext) => Promise<string>
type ToolHandler = (params: Record<string, unknown>, ctx: PluginContext) => Promise<{ output: string; error?: string }>
type HookHandler = (event: HookName, payload: unknown, ctx: PluginContext) => Promise<void>

MemoryAPI

The PluginContext.memory property provides access to the host agent's memory. This is a dependency-injected interface — plugin authors must test within a host that provides MemoryAPI.

interface MemoryAPI {
  loadSemantic(projectPath: string): Promise<SemanticEntry[]>
  saveSemantic(projectPath: string, entries: SemanticEntry[]): Promise<void>
  loadEpisodes(projectPath: string, count?: number): Promise<EpisodicEntry[]>
  appendEpisode(projectPath: string, entry: EpisodicEntry): Promise<void>
}