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

@terreno/agent-plugin-loop

v58.0.4

Published

Goal-driven code scans for Terreno: charter a measurable long-term goal, map-reduce the repository into verified findings, slice them into IPs and tasks, and drive each slice through the Terreno lifecycle until the metric hits target.

Readme

Terreno Loop plugin for Claude Code

Goal-driven loops for Claude Code. Give it an outcome an agent can measure on its own, such as CI wall time, bundle size, or lint count, and it charters the goal, finds the work, slices it into pull requests, and re-measures after each one lands until the metric hits target or the budget runs out. Each slice goes through the terreno lifecycle plugin, so install that plugin too.

Reference: https://github.com/TerrenoLabs/terreno/blob/master/docs/reference/scan-plugin.md

Install

Pick one channel and register only that one. Each channel provides a plugin named terreno-loop, so two channels give duplicate commands.

Latest stable release, installed from npm as @terreno/agent-plugin-loop:

/plugin marketplace add https://raw.githubusercontent.com/TerrenoLabs/terreno/master/plugins/claude-release/.claude-plugin/marketplace.json
/plugin install terreno-loop@terreno-releases

Every merge to master:

/plugin marketplace add TerrenoLabs/terreno
/plugin install terreno-loop@terreno-plugins

One release, pinned: add TerrenoLabs/terreno#<version> as the marketplace instead.

Then run /terreno-loop:run <goal>. Claude Code does not auto-update third-party marketplaces by default; run /plugin update terreno-loop@<marketplace> to pick up a new release.

What you get

| Command | Does | | --- | --- | | /terreno-loop:1-aim | Charter the goal: metric, baseline, rules, budget | | /terreno-loop:2-sweep | Run the rules and map parallel workers into candidate findings | | /terreno-loop:3-sift | Dedupe, verify, and rank findings | | /terreno-loop:4-plot | Slice findings into PR-sized plans | | /terreno-loop:5-track | Re-measure the metric and choose the next move | | /terreno-loop:campaign | Run bounded rounds, stopping at each gate | | /terreno-loop:run | Stay resident: keep the goal moving and tend every open PR |

Loops can run for hours and use many tokens. Set a budget or stop condition in the charter.

Maintainers

This directory is generated. Do not hand-edit it; run bun run skills:sync.

Claude Code resolves a plugin skill's command from the frontmatter name, so the shortened names live here instead of in the shared skill files. Cursor, Codex, and npx skills keep the canonical names from plugins/terreno-loop/.

| Source | Owns | | --- | --- | | plugins/terreno-loop/skills/ | Aim, Sweep, Sift, Plot, Track, and the outer loops | | plugins/terreno-loop/references/ | Scan contract, map-reduce, goal tracking, schemas |