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

@robota-sdk/pack-coding

v3.0.0-beta.93

Published

Robota's coding capability pack — an ICapabilityPack bundling the built-in coding tools, coding command modules, and coding subagents

Readme

@robota-sdk/pack-coding

Robota's coding capability as a single ICapabilityPack: the built-in coding tools, the coding command modules, and the coding subagents in one unit that assembleProduct can add to any product. The The host CLI can compose it for its coding assistant.

Installation

npm install @robota-sdk/pack-coding

Usage

import { assembleProduct } from '@robota-sdk/agent-product';
import { createCodingPack } from '@robota-sdk/pack-coding';
import type { IAIProvider, IProviderDefinition } from '@robota-sdk/agent-core';

declare const providerDefinitions: readonly IProviderDefinition[];
declare const provider: IAIProvider;

const cwd = process.cwd();
const product = assembleProduct({
  id: 'acme-assistant',
  providerDefinitions,
  // The coding tools, /shell + /editor + /git commands, and coding subagents. The file tools are
  // scoped to the cwd you build the pack with.
  packs: [createCodingPack({ cwd })],
});

const session = product.buildRuntime({ session: { cwd, provider } });
void session;

The pack bundles:

  • tools — Shell, Bash, Read, Write, Edit, Glob, Grep, WebFetch, WebSearch, AskUserQuestion (from @robota-sdk/agent-tool-defaults' createDefaultTools).
  • commandModules — /shell, /editor, and /git (from @robota-sdk/agent-command).
  • subagents — general-purpose, Explore, Plan (agent-framework's built-in agents).

createCodingPack passes its cwd and optional sandboxClient straight to the default tool factory, so the pack adds, drops, or reorders none of those tools. Its other options are shellExecutable (the shell for the tools and /shell) and editorTemporaryDirectoryPrefix (for /editor).

Why a factory, and why cwd is required

There is deliberately no context-free codingPack constant. The tool layer refuses a missing execution root, and this factory also requires cwd so each pack's file tools are scoped to the session that constructs it. That matters most when a product hands its whole tool surface to packs by passing defaultTools: [] in the session options. See docs/SPEC.md.

License

AGPL-3.0-only OR LicenseRef-Commercial