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-template-basic-tool

v1.0.0

Published

Template for creating AgentOS extensions

Readme

Template Extension for AgentOS

A template for creating new AgentOS extensions.

Quick Start

  1. Copy this template:
cp -r ext-template ext-myextension
cd ext-myextension
  1. Update package.json:
  • Change name to @framers/agentos-ext-{yourname}
  • Update description, author, keywords
  1. Update manifest.json:
  • Change id to com.framers.ext.{yourname}
  • Update metadata
  1. Implement your tools:
  • Create tools in src/tools/
  • Implement ITool interface
  • Export from src/index.ts

Development

# Install dependencies
npm install

# Build
npm run build

# Watch mode
npm run dev

# Run tests
npm test

# Lint
npm run lint

Structure

ext-template/
├── src/
│   ├── index.ts           # Extension pack export
│   ├── tools/
│   │   └── exampleTool.ts # Example tool implementation
│   └── types.ts           # TypeScript definitions
├── test/
│   └── unit/
│       └── exampleTool.spec.ts
├── manifest.json          # Extension metadata
├── package.json
└── README.md

Creating a Tool

import type { ITool, ToolExecutionContext, ToolExecutionResult } from '@framers/agentos';

export class MyTool implements ITool {
  readonly id = 'com.framers.ext.myext.myTool';
  readonly name = 'myTool';
  readonly displayName = 'My Tool';
  readonly description = 'What this tool does';
  
  readonly inputSchema = {
    type: 'object',
    properties: {
      // Define inputs
    },
    required: []
  };
  
  async execute(input: any, context: ToolExecutionContext): Promise<ToolExecutionResult> {
    try {
      // Your implementation
      return { success: true, output: {} };
    } catch (error) {
      return { success: false, error: error.message };
    }
  }
}

Configuration

Extensions can access configuration through the context:

async execute(input: any, context: ToolExecutionContext) {
  const config = context.configuration?.['myext'] || {};
  const apiKey = config.apiKey;
  // Use configuration
}

Declaring Secrets

If your tool needs an API key, declare it on the descriptor so hosts can surface the requirement:

requiredSecrets: [{ id: 'openai.apiKey' }],
onActivate: (ctx) => {
  exampleTool.setApiKey(ctx.getSecret?.('openai.apiKey'));
},

Secret IDs correspond to packages/agentos/src/config/extension-secrets.json and are also visible inside the AgentOS client UI.

Testing

Write comprehensive tests:

import { describe, it, expect } from 'vitest';
import { MyTool } from '../src/tools/myTool';

describe('MyTool', () => {
  it('executes correctly', async () => {
    const tool = new MyTool();
    const result = await tool.execute(
      { /* input */ },
      { /* context */ } as any
    );
    expect(result.success).toBe(true);
  });
});

Publishing

  1. Build: npm run build
  2. Test: npm test
  3. Version: npm version patch|minor|major
  4. Publish: npm publish --access public

License

MIT - See LICENSE