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

@favoyang/planrock

v1.2.1

Published

Saved Markdown plan tracking for coding agents.

Readme

Planrock

Planrock is a small CLI and agent skill for saved Markdown plans. It reads plan files under a repository-local plans/ directory, summarizes open and closed plans, and displays checklist progress plus agent session markers.

Skill Install

Install the Planrock skill globally for an agent runtime that supports skills:

npx skills add favoyang/planrock -g -y

URL form:

npx skills add https://github.com/favoyang/planrock -g -y

You can also ask an agent with skill-install support to install favoyang/planrock.

The skill uses its bundled CLI directly, so a global planrock shell command is not required for an agent to use the skill.

CLI Install

Run without installing:

npx @favoyang/planrock status

Install globally with npm:

npm install -g @favoyang/planrock
planrock status

Install globally with Volta:

volta install @favoyang/planrock
planrock status

Link from a local checkout:

git clone https://github.com/favoyang/planrock.git
cd planrock
npm link
planrock status

Usage

planrock status
planrock open
planrock open --sort time
planrock open --full-agent-session
planrock closed
planrock goal plans/example-plan.md

By default, Planrock reads plans/ under the current working directory. Use --working-dir /path/to/repo when you want to inspect a different repository. Add --json for machine-readable output.

Use planrock goal <path-to-plan> to print a copy-pasteable Codex /goal command from the body of the plan's ## Goal section. The output ends with a stable plans/... reference for the original plan file.

When using --working-dir, repo-relative goal paths resolve from that selected working directory:

planrock goal plans/example-plan.md --working-dir /path/to/repo

Plan files live directly under plans/ and use YAML frontmatter:

---
title: Publish Planrock
state: open
priority: P1
created_at: 2026-06-13
agent_sessions:
  - codex:example-session-id
---

- [ ] Do the next concrete step.

Agent Sessions

Use agent_sessions to record the agent sessions that have worked on a plan. Each entry uses <agent-slug>:<session-id>.

Supported agent slugs:

  • codex
  • claude-code

Unknown agents should use a stable lowercase slug such as local-agent. Planrock preserves unknown slugs instead of rejecting them. Human output shortens each entry to the slug plus the first 8 characters of the session id, such as claude-code:example-; use --full-agent-session to show complete values.

Release

Releases are automated with semantic-release from GitHub Actions on main. Use Semantic Commit Messages so the release type can be calculated:

fix: correct plan parsing
feat: add a new CLI command
feat!: change plan file format

Publishing is handled by the release workflow.

Development

npm test
npm pack --dry-run
npx -y -p semantic-release@25 -p @semantic-release/git semantic-release --dry-run

License

MIT