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

plumblines

v0.3.1

Published

A plain-Markdown project continuity framework for AI coding agents.

Downloads

319

Readme

Plumblines

A plain-Markdown continuity framework for AI coding agents.

AI agents forget decisions between sessions and act on stale assumptions. Plumblines gives them a .agent_files/ memory layer — project state, decisions, change history, and risks as Markdown records anchored to commits, with gates that flag stale or undocumented changes.

It's a coordination layer, not a source of truth: the code always wins.

Quick start

npx plumblines init                        # scaffold .agent_files/
npx plumblines init --team --hooks --ci --obsidian

Pure Node, no dependencies, nothing to clone. Then:

  1. Fill PROJECT_STATE.md — or run the plumblines-init skill to draft it from your codebase.
  2. Point your agent at .agent_files/AGENT_RULES.md before it changes code.
  3. Record each change under .agent_files/local/changes/ (the plumblines-change skill does this).

From a clone instead: bash scripts/plumblines-init.sh (or pwsh scripts/plumblines-init.ps1). Full setup, layouts, and the manual-copy mapping: docs/integration.md.

Installing the agent skills

Copy them where your agent looks for skills. For Claude Code:

cp -r skills/plumblines-init skills/plumblines-change .claude/skills/   # or ~/.claude/skills/

PowerShell: Copy-Item -Recurse skills\plumblines-init, skills\plumblines-change .claude\skills\. Other agents: point them at the SKILL.md files directly — they're plain Markdown.

What it creates

.agent_files/
  AGENT_RULES.md        # how the agent uses the memory
  CONTEXT_PRIORITY.md   # which sources win when they conflict
  LOADING_POLICY.md     # what to read per task
  PROJECT_STATE.md      # state, architecture, decisions
  local/changes/        # one record per change
  compacted/            # summaries of older records

--team adds shared/ and domains/<domain>/ for large codebases.

How it works

  • Each record carries a trust label (verified, inferred, assumed, needs-review, stale) and a valid_as_of_commit, so memory can be flagged when its dependencies change.
  • Two gates keep it honest — staleness reports records whose deps moved; completeness blocks source commits with no change record (and trust that escalates above its inputs):
npx plumblines check          # completeness (blocking) + staleness (report)

Learn more

| Doc | What | |---|---| | integration.md | install paths, layouts, name mapping | | framework.md | the full model and principles | | record-schema.md | the frontmatter contract | | ci-wiring.md | hooks and CI | | obsidian.md | record dashboards in Obsidian |

Status

v0.3.1 — public draft. Plain Markdown throughout; works with any coding agent, editor, or repository.