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

@zagents/sdk

v0.1.1

Published

Convenience helpers for gemini authors — defineHarness, defineAgent, defineSkill, defineTool. Light wrappers around @zagents/kernel.

Readme

@zagents/sdk

Convenience helpers for gemini authors. Wraps @zagents/kernel with typed, validated, named definitions so your IDE catches typos before they reach the kernel.

Use

import {
  defineHarness, defineAgent, defineSkill, defineTool,
  defineHook, defineMcpServer,
} from '@zagents/sdk';

const triager = defineAgent({
  name: 'triager',
  systemPrompt: 'You triage support tickets.',
  tier: 'small',
});

const escalator = defineAgent({
  name: 'escalator',
  systemPrompt: 'You decide when to page humans.',
  tier: 'frontier',
});

const kbServer = defineMcpServer({
  name: 'kb',
  command: ['npx', '-y', 'my-bot', 'mcp', 'kb'],
});

export default defineHarness({
  name: 'my-bot',
  description: 'Customer support gemini',
  agents: [triager, escalator],
  mcpServers: [kbServer],
});

Why use it instead of building HarnessSpec directly

| Without SDK | With SDK | |---|---| | Field-name typos compile (e.g. system_prompt vs systemPrompt) | TypeScript catches | | Invalid tier passes silently | Throws at define time | | Two agents named the same → confused dispatch | Throws agent name collision | | Gemini name accepts MyBot | Enforces kebab-case (npm-publishable) | | Forgot description? Generated gemini ships empty | Throws |

All define*() helpers return frozen objects so you can't accidentally mutate them.

License

MIT