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

@framers/agentos-extensions-registry

v0.18.0

Published

Extension catalog for AgentOS — channel, tool, and provider metadata with dynamic loading via createCuratedManifest()

Readme

@framers/agentos-extensions-registry

Extension catalog for AgentOS — metadata, query helpers, and createCuratedManifest() factory.

npm

What this package is

This is the catalog and SDK for AgentOS extensions. It does not contain extension source code — it provides:

  • Static metadata catalogs (CHANNEL_CATALOG, TOOL_CATALOG, PROVIDER_CATALOG) describing every known extension: its name, package, SDK, required secrets, and capabilities.
  • Query helpers (getChannelEntry(), getToolEntry(), getProviderEntry()) for looking up catalog entries at runtime.
  • Dynamic loader (createCuratedManifest()) that resolves which extension packages are actually installed, then builds an ExtensionManifest the AgentOS runtime can consume.

Architecture: catalog vs. source code

| Package | Role | |---|---| | @framers/agentos-extensions | Source code — the actual channel adapters, tool implementations, and extension packs | | @framers/agentos-extensions-registry (this) | Catalog/SDK — indexes the extensions above, stores metadata, and dynamically loads whichever packages are installed | | @framers/agentos | Runtime — provides ITool, IChannelAdapter, ExtensionManifest, and the agent kernel that consumes the manifest |

Dependency direction: this package depends on @framers/agentos for runtime types (peer dep) and references extension packages from @framers/agentos-extensions as optional dependencies. Only installed extensions are loaded; missing packages are silently skipped.

Installation

pnpm add @framers/agentos-extensions-registry

Then install whichever extension packages you need (e.g. @framers/agentos-ext-telegram). Only installed packages will be loaded by createCuratedManifest().

Main exports

| Export | Description | |---|---| | createCuratedManifest(options?) | Builds an ExtensionManifest from installed extensions. Accepts channel/tool filters, secrets, and per-extension overrides. | | CHANNEL_CATALOG | Static catalog of all 37 channel platform entries (platform, package, SDK, required secrets) | | TOOL_CATALOG | Static catalog of tool extensions (web search, CLI executor, image search, etc.) | | PROVIDER_CATALOG | Static catalog of 21 LLM provider entries (provider name, models, base URLs) | | getAvailableExtensions() | Returns only extensions whose npm packages are resolvable in the current environment | | getAvailableChannels() | Returns only channel adapters whose packages are installed | | SECRET_ENV_MAP | Maps secret keys (e.g. telegram.botToken) to environment variable names |

Usage

import { createCuratedManifest } from '@framers/agentos-extensions-registry';

// Load all installed extensions
const manifest = await createCuratedManifest({ channels: 'all', tools: 'all' });

// Or selectively enable specific channels
const manifest = await createCuratedManifest({
  channels: ['telegram', 'discord', 'slack'],
  tools: 'all',
  secrets: {
    'telegram.botToken': process.env.TELEGRAM_BOT_TOKEN,
    'discord.botToken': process.env.DISCORD_BOT_TOKEN,
    'slack.botToken': process.env.SLACK_BOT_TOKEN,
  },
});

// Pass to AgentOS runtime
const agent = new AgentOS();
await agent.initialize({ extensionManifest: manifest });

createCuratedManifest(options?)

| Parameter | Type | Default | Description | |---|---|---|---| | channels | string[] \| 'all' \| 'none' | 'all' | Which channel platforms to enable | | tools | string[] \| 'all' \| 'none' | 'all' | Which tool extensions to enable | | secrets | Record<string, string> | {} | Secrets map (falls back to env vars) | | basePriority | number | 0 | Base priority for all extensions | | overrides | Record<string, Override> | {} | Per-extension overrides: { enabled?, priority?, options? } |

License

MIT