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

@roelven/openclaw-verify-tool-output

v1.0.1

Published

OpenClaw plugin that injects verification hints into tool results — nudges agents to verify before claiming success

Readme

verify-tool-output

An OpenClaw plugin that nudges agents to verify their work before claiming success. It appends [VERIFY] hints to tool results so the LLM sees a reminder to check what actually happened.

What it does

Agents have a tendency to run a command, see no error, and immediately tell the user "Done!" — without actually checking that the file was written, the service started, or the cron job was registered. This plugin addresses that by injecting short verification prompts into the tool result that the LLM receives.

After each tool call, the plugin checks which tool was used and appends a context-appropriate hint:

  • exec / bash / process — If the command failed, the hint tells the agent to read stderr and diagnose before retrying. If the command succeeded but produced no output, it reminds the agent to verify the side effect (check the file exists, the service is running, etc.).
  • write / edit / apply_patch — The hint tells the agent to read back the file before reporting success.
  • cron — The hint tells the agent to run cron.list to confirm the schedule.

The hints are appended to what the LLM sees (not what gets persisted), so they influence behavior without polluting the transcript.

Why use it

  • Reduces "blind success" reports where the agent claims completion without verification
  • Catches silent failures (command exits 0 but didn't actually do the thing)
  • Encourages read-back after writes, catching truncation or encoding issues early
  • Works transparently — the user sees better agent behavior without any prompting on their part

Compatibility

  • OpenClaw version: Requires OpenClaw main branch (post-February 2026) with the after_tool_call hook modification from the feat/agent-hardening branch. Specifically, this plugin returns appendContent from the after_tool_call hook, which is not yet part of the standard plugin API.
  • Hook used: after_tool_call with appendContent return value.
  • No external dependencies.

Important: If you install this plugin on a version of OpenClaw that does not have the appendContent support in the after_tool_call hook, the plugin will register without errors but the verification hints will be silently ignored.

Installation

openclaw plugins install @roelven/openclaw-verify-tool-output

Then register it in your ~/.openclaw/openclaw.json:

{
  "plugins": {
    "allow": ["verify-tool-output"],
    "entries": {
      "verify-tool-output": { "enabled": true }
    }
  }
}

Restart the gateway:

openclaw gateway stop && openclaw gateway start

Setup

No additional configuration is needed. The plugin works immediately after installation.

The verification hints are not configurable — they are intentionally opinionated to keep the plugin simple. If you find the hints too aggressive for your use case, you can disable the plugin per-session or uninstall it.

License

MIT