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

kelocan

v0.1.1

Published

Kelocan CLI — thin client & agent workflow commands for the Kelocan kanban board

Readme

kelocan

CLI for the Kelocan kanban board — a thin client over the REST API, designed for humans and AI agents (low-token output via --json / --fields).

Install

npm install -g kelocan        # or: npx kelocan <command>

Requires Node.js ≥ 20.

Onboarding — install the MCP server & skills into your agent

npx kelocan init

One command: logs you in (browser), detects installed agents, lets you pick which to configure, writes the kelocan MCP entry and the agent skills, then verifies the connection — in ≤ 3 prompts.

Supported agents:

| Agent | Config file | Entry | Auth | Skills dir | | --- | --- | --- | --- | --- | | Devin CLI | ~/.config/devin/mcp_config.json | mcpServers.kelocan.url | OAuth | ~/.agents/skills | | Claude Code | claude mcp add (fallback ~/.claude.json) | mcpServers.kelocan (http) | OAuth | ~/.claude/skills | | Cursor | ~/.cursor/mcp.json | mcpServers.kelocan.url | OAuth | ~/.agents/skills | | Codex | ~/.codex/config.toml | [mcp_servers.kelocan] + bearer_token_env_var | API key env | ~/.agents/skills | | Opencode | ~/.config/opencode/opencode.json | mcp.kelocan (remote) | OAuth | ~/.agents/skills | | Antigravity | ~/.gemini/antigravity/mcp_config.json or ~/.gemini/config/mcp_config.json (whichever exists) | mcpServers.kelocan.serverUrl + headers | API key header | skills/ next to the config | | Hermes | ~/.hermes/config.yaml | mcp_servers.kelocan + auth: oauth | OAuth | ~/.hermes/skills |

Safety: only the kelocan entry is ever merged — other MCP entries are left untouched, the original file is backed up to <config>.bak, and re-running is idempotent. Secrets are never written literally; API-key installs reference $KELOCAN_API_KEY from the environment.

Non-interactive:

kelocan init --agent devin,cursor        # specific agents
kelocan mcp install --agent all          # only MCP entries
kelocan skills install --agent claude    # only skill files
kelocan uninstall --agent codex          # remove kelocan entry + skills only
kelocan doctor                           # verify everything (read-only)

The skills can also be installed by any agent that supports the Agent Skills convention: npx skills add IFLyer/kelocan-cli.

Auth

kelocan login                          # browser flow: opens the /cli/authorize page
kelocan login --api-key klc_...        # headless: store an existing API key
kelocan login --url http://localhost:8001 --web-url http://localhost:5173
kelocan whoami
kelocan logout

Config is stored in ~/.config/kelocan/config.json (mode 600; %APPDATA%/kelocan on Windows). Environment overrides: KELOCAN_URL, KELOCAN_API_KEY, KELOCAN_WEB_URL.

Commands

| Command | Description | | --- | --- | | board show <board> | Board columns & task counts | | task list <board> [--column X] [--label Y] [--sprint Z] | List tasks | | task show <id> | Task detail | | task prompt <id> | Rendered agent prompt | | task create <board> --title "..." [--column X] [--kind task\|idea\|feedback] [--priority low\|medium\|high\|urgent] [--label a,b] [--sprint active\|backlog\|uuid] | Create task | | task move <id> --to <column\|role> [--position N] | Move task | | task comment <id> -m "..." / --file path | Add comment / attachment | | run start <task> --agent "Devin" | Open agent run (prints run_id) | | run finish <run_id> --outcome succeeded\|failed\|cancelled -m "..." | Close run | | subtask list <task> / subtask toggle <id> | Sub-task checklist |

Boards, columns, and labels can be referenced by name, workflow role (backlog|active|review|done) or UUID. Ambiguous names produce an error listing the candidates.

Output & exit codes

Default output is concise text. --json prints the raw API payload; --fields a,b,c selects fields (JSON objects, or tab-separated text).

Exit codes: 0 success · 1 validation/usage (message lists valid values) · 2 auth · 3 network/server.

Every command supports --help with examples: kelocan task create --help.

Agent workflow example

kelocan task prompt 8c8fb91c-... > prompt.md          # fetch instructions
kelocan run start 8c8fb91c-... --agent "Devin"        # -> run_id: ...
kelocan task comment 8c8fb91c-... -m "Progress: ..."  # report progress
kelocan task move 8c8fb91c-... --to review            # move card
kelocan run finish <run_id> --outcome succeeded -m "PR opened"

Development

npm install
npm run build          # tsc -> dist/
npm test               # unit tests (node:test via tsx)
npm run test:e2e       # e2e vs live backend (needs KELOCAN_E2E=1, KELOCAN_URL, KELOCAN_API_KEY)

Publishing

GitHub Actions publishes to npm when a v* tag is pushed (.github/workflows/publish.yml). Requires an NPM_TOKEN secret.