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

@davidorex/pi-jit-agents

v0.14.6

Published

Agent spec compilation and in-process dispatch runtime — the package that owns everything between 'I have a spec' and 'I have a typed result'

Readme

@davidorex/pi-jit-agents

Agent spec compilation and in-process dispatch runtime. Owns everything between "I have a spec" and "I have a typed result."

Purpose

JIT agents are named callable units with typed input contracts, typed output contracts, and context-parametric implementations materialized at runtime from project state. This package provides:

  • Spec loading with full path resolution and tier-aware discovery
  • Template compilation with project block context injection
  • In-process LLM dispatch with phantom-tool structured output enforcement
  • Agent contract introspection for SDK queries

There is one concept of "agent" regardless of whether a workflow step or a monitor classify call invokes it. Classification is agent execution with a verdict-shaped output schema; it is not a separate primitive.

Boundary

The package owns four public surfaces:

  • loadAgent(name, ctx) → AgentSpec — resolves spec from discovery tiers, fully resolves all path fields to absolute
  • compileAgent(spec, ctx) → CompiledAgent — renders templates, injects contextBlocks from .project/, composes final prompts
  • executeAgent(compiled, dispatch) → JitAgentResult — in-process LLM dispatch with phantom tool enforcement
  • agentContract(spec) → AgentContract — projection for introspection, no execution

Subprocess dispatch stays in pi-workflows. The package never reads from .pi/ — that directory is Pi platform territory.

Discovery tiers

Agent specs are searched in this order:

  1. {cwd}/.project/agents/{name}.agent.yaml — project-level overrides
  2. {userDir ?? ~/.pi/agent/agents/}/{name}.agent.yaml — user-global overrides
  3. {builtinDir}/{name}.agent.yaml — consumer-supplied builtins

The framework package itself ships no bundled agent specs. Consumer packages supply their own builtin directory at loader construction time.

Exports

  • . — main barrel
  • ./types — type definitions
  • ./agent-specparseAgentYaml, createAgentLoader
  • ./templatecreateTemplateEnv, renderTemplate, renderTemplateFile
  • ./compilecompileAgent
  • ./runtimeexecuteAgent, buildPhantomTool
  • ./introspectagentContract