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

@sabaiway/agent-workflow-memory

v1.1.2

Published

Portable, cross-agent memory substrate for AI coding agents — an AGENTS.md entry point + docs/ai context with cap/archive/index enforcement, deployable standalone or as part of the agent-workflow family. The memory layer of the agent-workflow family.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

coder-toolcoder-tool

Keywords

ai-agentsai-codingcoding-agentllmai-toolsclaude-codecodexcursoragents-mdagent-memorycontext-engineeringcross-agentmemorydeveloper-tools

Readme

@sabaiway/agent-workflow-memory

Portable, cross-agent memory substrate for AI coding agents. Deploys an AGENTS.md entry point (+ a CLAUDE.md symlink for Claude Code) and a structured docs/ai/ context store with cap / archive / index-freshness enforcement into any repo. After it runs, any future agent — including a fresh session of yourself — can reconstruct project context in ~60 seconds, find the current task, and avoid repeating past mistakes.

This is the memory layer of the agent-workflow family. It owns the substrate only — docs/ai/, the entry point, caps / 3-tier archive / index gate, the Node enforcement scripts, the pre-commit hook, the templates, and the three setup contracts (visibility / conversational language / agent attribution). It deliberately knows nobody else in the agent-workflow family: the workflow methodology (plan → execute → review vocabulary, lifecycle, queue.md, mandatory Cleanup) lives elsewhere and is injected into a delimited slot in AGENTS.md by the family composition root, not by this package.

Install

npx @sabaiway/agent-workflow-memory@latest init

Installs/refreshes the skill at ~/.claude/skills/agent-workflow-memory (override with --dir <path> or AGENT_WORKFLOW_MEMORY_DIR). init is additive — it never deletes your settings and never writes through a symlink. Re-running updates the skill's own files; that is how you upgrade the skill. Migrating a project's deployment is a separate in-agent step (below).

Use

Open your agent inside a project and run the skill:

  • /agent-workflow-memory — bootstrap a new or empty project. Asks the three setup questions (visibility, conversational language, agent attribution), then writes docs/ai/, AGENTS.md, the enforcement scripts + pre-commit hook, and stamps docs/ai/.memory-version. The two pointer slots in AGENTS.md (the methodology and orchestration pointers, filled later by the family composition root) are left empty.
  • /agent-workflow-memory upgrade — migrate an existing deployment to the skill's current version. Reads docs/ai/.memory-version, runs only newer migrations in semver order, and preserves anything already in either pointer slot (extract-and-reinsert — it never regenerates AGENTS.md wholesale).

Stamps & lineage

Two independent axes: this package's npm version vs the deployment-lineage stamp the substrate writes into a project. They are not the same number. .memory-version tracks the shared agent-workflow deployment lineage (head 1.3.0 today), not this package's version. A project bootstrapped by the kit's fallback carries a .workflow-version; when this substrate is later installed, migrations/legacy-stamp-takeover.md copies that value verbatim into .memory-version and never deletes the legacy stamp. See migrations/README.md.

What this package ships

SKILL.md (procedure + ownership table), references/ (templates + the deployable Node enforcement scripts + the setup contracts), scripts/stamp-takeover.mjs (the upgrade-time lineage state machine + tests), migrations/, capability.json (the family manifest), and this installer. It ships no family-wide tooling (the schema/validator are owned by the composition root) — preserving "knows nobody".

License

MIT — see LICENSE.