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

@ai-agent-forge/plugin-workspace-files-write

v0.88.11

Published

Workspace file write capability plugin for Agent Forge (full-control workspace_write tool with atomic replace/patch)

Readme

@agent-forge/plugin-workspace-files-write

Workspace file write capability plugin for Agent Forge, extracted from the host's src/plugins/workspace-files-write (D-075 S3). It registers one full-control tool, workspace_write, which atomically replaces or patches a host-owned file using opaque file and artifact references; bytes and local paths never cross the capability boundary.

The plugin is deliberately inert at load time. Without a host-bound write seam the tool reports an explicit unsupported result; hosts that want real writes bind createNodeWorkspaceFilesWriteHostAdapterV1 (sandboxed root, artifact resolution, version-checked atomic commits) through their profile machinery. Readonly hosts get no tool registration at all.

Install

# from a local checkout
agent-forge plugin install ./plugins/workspace-files-write

# from npm
agent-forge plugin install @agent-forge/plugin-workspace-files-write

The package ships two manifests: agent-forge.json (ecosystem manifest for the deterministic plugin resolver) and plugin.json (host-load manifest consumed by loadCapabilityPluginFromManifest, entry ./dist/entry.js).

Library surface

import { createNodeWorkspaceFilesWriteHostAdapterV1, createWorkspaceFilesWriteCapabilityFactoryV1 } from "@agent-forge/plugin-workspace-files-write";

  • createNodeWorkspaceFilesWriteAdapterV1(options?) — host-injection adapter; requires a host write seam, otherwise returns unsupported.
  • createNodeWorkspaceFilesWriteHostAdapterV1({ root, resolveFileRef, readArtifact, ... }) — real sandboxed host writer: atomic rename commits, expectedVersion checks, per-path single-flight serialization, committed reporting.
  • createWorkspaceFilesWriteCapabilityFactoryV1(adapter?) — registers workspace_write on a full-control CapabilityAPI (defaults to the unbound adapter).
  • Default export of dist/entry.js — the precomposed factory used by external plugin loading.

Development

npm install --ignore-scripts        # repo root, creates the workspace symlink
npm run build                       # plugins/workspace-files-write (tsgo)
npm test                            # vitest; the entry fidelity test requires `npm run build` first