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

@boringos/module-sdk

v1.0.0

Published

Module SDK — types for the Skills + Tools + Modules architecture.

Downloads

159

Readme

@boringos/module-sdk

Public type surface for v2 Modules. Every connector, capability, hybrid app, and built-in subsystem in v2 is shaped as a Module declared with these types.

What's in this package

  • Module — the universal manifest shape
  • Tool, ToolContext, ToolResult, ToolError — callable operations
  • Skill, SkillSource, SkillApplicabilityEvent — markdown teaching loaded into the agent's prompt
  • Routine, RoutineTrigger — scheduled tool calls
  • Webhook, WebhookRequest — inbound HTTP
  • OAuthConfig — connector OAuth dance
  • Migration, ModuleDb — Module-owned DDL
  • ModuleUI, ScreenDef, PanelDef — browser-facing surface
  • ModuleLifecycle, ModuleContext — install / uninstall hooks
  • ModuleFactory, ModuleFactoryDeps — factory shape for service-aware Modules
  • WorkflowSeed, WorkflowBlock, WorkflowEdge — default workflows seeded on install
  • AgentSeed — default agents seeded on install
  • z — re-export of Zod for input/output schemas

This package exports types only (plus the Zod re-export). Registries, dispatch, and prompt assembly live in @boringos/agent and @boringos/core.

Conventions third-party authors must follow

The types here permit many shapes; the framework's runtime expects some choices to be made consistently so every module composes with the Shell, Copilot, workflow templating ({{blockName.field}}), and other modules' tools.

  • Tool result payload shape. Successful results follow a single rule: list-style tools return a named-key object keyed by the plural resource ({ result: { messages } }, { result: { events } }, { result: { deals } }); singular tools return the value directly ({ result: message }). See TOOLS.md → Result payload convention for the full rule and rationale.
  • Error shape. Expected failures always return { ok: false, error: ToolError }; unhandled bugs throw and the dispatcher converts to code: "internal". See ToolError / ToolErrorCode above.
  • tenantId is in ToolContext, never in inputs. Handlers read it from context for DB scoping and audit; clients can't forge it.

Imported by

Every v2 Module — built-in (@boringos/core/src/v2-modules/*) and third-party.

Minimal usage

import { z } from "@boringos/module-sdk";
import type { Module } from "@boringos/module-sdk";

export const helloModule: Module = {
  id: "hello",
  name: "Hello",
  version: "0.1.0",
  description: "Demo module — one tool, one skill",

  skills: [
    {
      id: "hello",
      source: "module",
      body: "Use `hello.greet` to say hi to someone by name.",
    },
  ],

  tools: [
    {
      name: "greet",
      description: "Greet someone by name",
      inputs: z.object({ name: z.string() }),
      async handler({ name }) {
        return { ok: true, result: { message: `Hello, ${name}!` } };
      },
    },
  ],
};

Register it on the host:

import { BoringOS } from "@boringos/core";
import { helloModule } from "./hello.js";

const app = new BoringOS({ /* config */ });
app.module(helloModule);
await app.listen(3000);

See also