@llblab/pi-kit
Version-pinned distribution of LLB Lab extensions for Pi
Package details
Install @llblab/pi-kit from npm and Pi will load the resources declared by the package manifest.
$ pi install npm:@llblab/pi-kit- Package
@llblab/pi-kit- Version
0.1.7- Published
- Aug 22, 2026
- Downloads
- 716/mo · 716/wk
- Author
- llblab
- License
- MIT
- Types
- extension, skill
- Size
- 5.3 MB
- Dependencies
- 4 dependencies · 0 peers
Pi manifest JSON
{
"extensions": [
"./node_modules/@llblab/pi-actors/dist/pi-actors/index.js",
"./node_modules/@llblab/pi-codex-usage/index.ts",
"./node_modules/@llblab/pi-grow-loop/index.ts",
"./node_modules/@llblab/pi-telegram/index.ts"
],
"skills": [
"./node_modules/@llblab/pi-actors/dist/skills",
"./node_modules/@llblab/pi-grow-loop/skills",
"./node_modules/@llblab/pi-telegram/skills"
]
}Security note
Pi packages can execute code and influence agent behavior. Review the source before installing third-party packages.
README
@llblab/pi-kit
@llblab/pi-kit is the version-pinned LLB Lab extension distribution for Pi. It provides one installable package while each included extension keeps its own repository, release line, and development lifecycle.
Included packages
| Package | Version | Resources |
|---|---|---|
@llblab/pi-actors |
0.50.0 |
Extension and Skills |
@llblab/pi-codex-usage |
0.9.3 |
Extension |
@llblab/pi-grow-loop |
0.7.2 |
Extension and Skills |
@llblab/pi-telegram |
0.36.11 |
Extension and Skills |
Versions are exact by design. Updating an extension does not change an installed kit until this repository explicitly advances that dependency and publishes a new kit version.
Install
From npm:
pi install npm:@llblab/pi-kit
From GitHub:
pi install git:github.com/llblab/pi-kit
Pi loads the bundled extension entrypoints and Skills declared by this package. The kit itself does not register an extension or introduce runtime behavior.
Development
npm install
npm run validate
To advance one included package, update its exact version in dependencies, run npm install, update the package table and changelog, then validate the packed artifact. Do not use version ranges.
Security
Pi extensions execute with the user's system permissions. Review every included package and its release before advancing the pinned version.