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

@harnesstrim/adapter-opencode

v0.0.2

Published

OpenCode plugin adapter for HarnessTrim: slims tool output via core reducers and injects compaction handoff guidance.

Readme

@harnesstrim/adapter-opencode

HarnessTrim adapter for OpenCode. A thin plugin that:

  • tool.execute.after — slims noisy tool output (test runs, git diffs, ...) in place using the shared @harnesstrim/core reducers, before it enters the model's context.
  • experimental.session.compacting — injects compact-handoff guidance so compaction keeps decision-relevant state instead of narrated history.

The plugin is deliberately thin: all detection and reduction logic lives in @harnesstrim/core (and is unit-tested there without a live harness). See the repo PLAN.md.

Install (local / development)

From an OpenCode project, reference the plugin in opencode.json. During development you can point at the workspace package directly:

{
  "plugin": ["@harnesstrim/adapter-opencode"]
}

With options:

{
  "plugin": [
    ["@harnesstrim/adapter-opencode", { "mode": "active", "minLength": 400, "debug": false }]
  ]
}

Configuration

Options (in opencode.json) take precedence over environment variables, then defaults.

| Option | Env var | Default | Meaning | | ------------------- | ------------------------- | ---------- | -------------------------------------------------------------- | | mode | HARNESSTRIM_MODE | active | active reduces in place; dryrun logs only; off disables. | | minLength | HARNESSTRIM_MIN_LENGTH | 400 | Tool outputs shorter than this (chars) are left untouched. | | debug | HARNESSTRIM_DEBUG | false | Emit one-line [harnesstrim] diagnostics to stderr. | | compactionHandoff | — | true | Inject handoff guidance on compaction. | | telemetry | HARNESSTRIM_TELEMETRY | false | Append a TrimEvent JSONL record per reduction. | | telemetryPath | HARNESSTRIM_TELEMETRY_PATH | .harnesstrim/metrics.jsonl | Where telemetry JSONL is appended. |

Telemetry is off by default. When on, each reduction appends one JSON line; read the aggregate with harnesstrim metrics <path>. In dryrun mode telemetry still records what would be reduced, so you can size the win before switching to active.

Start with mode: "dryrun" and debug: true to see what would be reduced without changing model input, then switch to active once you're comfortable.

Runtime notes

  • OpenCode plugins run on Bun; this package targets Bun's runtime (it imports TypeScript directly). No build step.
  • Reduction is measured at runtime by character count (a cheap proxy) — no tokenizer is bundled into the harness process. Token-accurate reduction numbers live in the repo's benchmarks/.