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

@benjamin.francisoud/yokai

v1.0.1

Published

Script to distribute centralized genai files: instructions, prompts, skills and agents

Readme

YokAI

The repositories-configuration.js script automates the process of cloning multiple repositories, copying standardized .github files (such as instructions, prompts, and configuration), and optionally committing and pushing these changes back to each repository. This helps ensure all repositories stay up-to-date with the latest best practices and automation assets.

Powered by Awesome Copilot

Features:

  • Clone all repositories listed in repositories-configuration.yaml
  • Copy files and folders to the .github directory of each repo
  • Optionally commit and push changes (can be disabled with flags)
  • Clean up local clones automatically (unless debug mode is enabled)

Example usage:

$ npm ci # install dependencies - only one time

$ node repositories-configuration.js --help
Options:
  --debug             Keep local cloned repositories after script runs
                                                      [boolean] [default: false]
  ...
  --help              Show help                                        [boolean]
  --version           Show version number                              [boolean]

Clones repositories listed in repositories-configuration.yaml, copies
standardized .github files (instructions, prompts, agents), and optionally
commits/pushes the changes back to each repository.

Examples:

# Clone but don't commit anything...
$ node repositories-configuration.js --debug --dryrun

# Run only on repositories that contain "SOME_REPO_TO_INCLUDE" in their name
node repositories-configuration.js --include SOME_REPO_TO_INCLUDE

# Skip repositories that contain "SOME_REPO_TO_EXCLUDE" in their name
node repositories-configuration.js --exclude SOME_REPO_TO_EXCLUDE

Project-local config (.repositories-configuration)

You can create a project-local JSON dotfile named .repositories-configuration at the root of a repository to provide persistent defaults for this script. Values in the dotfile act as defaults and are overridden by command-line flags. Example JSON:

{
	"branch": "feature/some-branch-name",
	"version-file": "myproject-awesome-copilot.version.md",
	"debug": true,
	"central-repo-url": "https://github.com/my-org/some-repository-with-awesome-copilot-files"
}

Place this file in the repository you run the script against (or in the same folder where you run the script) and the script will pick up those defaults automatically.

repositories-configuration.yaml Validation: a JSON schema (repositories-configuration.schema.json) is provided.