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

opencode-auto-todos

v1.3.0

Published

OpenCode plugin that automatically adds custom todos to every feature's task list

Readme

opencode-auto-todos

npm version

An OpenCode plugin that automatically appends custom todos to every task list. Define your standard workflow items once, and they'll be added to every todowrite call automatically.

Use Cases

  • Version bump reminder — Never forget to bump versions before merging
  • GitHub workflow — Always create branch, commit, and open PR
  • Code review checklist — Add standard review items to every feature
  • Deployment steps — Ensure deploy-related tasks are always tracked

Installation

# In your project directory
npm install --save-dev opencode-auto-todos

Then add to your opencode.json:

{
  "plugin": ["opencode-auto-todos"]
}

Configuration

Create an auto-todos.json file in your project root or inside .opencode/:

{
  "todos": [
    {
      "content": "Version bump - update version in package.json",
      "priority": "medium",
      "match": "version bump",
      "order": "first"
    },
    {
      "content": "Create branch, commit changes, open PR",
      "priority": "medium",
      "match": "github",
      "order": 2
    }
  ],
  "always": false,
  "deduplicate": true
}

Config Options

| Field | Type | Default | Description | |-------|------|---------|-------------| | todos | AutoTodo[] | required | List of todos to automatically add | | always | boolean | false | If true, add todos to every todowrite call. If false, only when the list is first created (empty). | | deduplicate | boolean | true | Skip adding a todo if a similar one already exists in the list. |

AutoTodo Shape

| Field | Type | Required | Description | |-------|------|----------|-------------| | content | string | yes | The todo text to display | | priority | "high" \| "medium" \| "low" | no | Priority level (default: "medium") | | match | string | no | Substring to match against existing todos for deduplication. If omitted, content is used. | | order | "first" \| "last" \| number | no | Position where the todo is inserted (default: "last"). "first" = beginning, "last" = end, number = 1-based index (e.g., 1 = first, 2 = second). |

How It Works

  1. The plugin hooks into OpenCode's tool.execute.before event for the todowrite tool
  2. Before any todo list is written, it checks the config file
  3. It appends your configured todos to the list (unless they already exist)
  4. The model then sees the complete list including your standard items

Example

With this config:

{
  "todos": [
    { "content": "Read CLAUDE.md or project docs", "order": "first" },
    { "content": "Version bump", "match": "version" },
    { "content": "Create branch, commit, open PR", "match": "github" }
  ]
}

Every time you start a new feature, the agent's todo list will automatically include:

✓ [your feature-specific todos]
☐ Read CLAUDE.md or project docs
☐ Version bump
☐ Create branch, commit, open PR

License

MIT