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

@retinue/tools-slack

v0.3.0

Published

Slack tools for a Retinue agent: read channels and history, post messages and replies — gated and idempotent.

Readme

@retinue/tools-slack

npm licence

Slack tools for a Retinue agent. Read channels and history, post messages and thread replies — with every write gated behind human approval and carrying an idempotency key.

Install

npm i @retinue/tools-slack

Use

import { createAgent } from "@retinue/agentkit/providers";
import { createStaticCredentialResolver } from "@retinue/agentkit/tools";
import { createSlackToolkit } from "@retinue/tools-slack";

const agent = createAgent({
  manifest: { id: "helper", name: "Helper", instructions: "Answer in the thread you were asked in.", modelPolicy: { role: "smart" } },
  tools: [
    createSlackToolkit({
      credentialRef: "slack-bot",
      // Per tenant in a multi-tenant deployment: one workspace, one bot token.
      resolver: createStaticCredentialResolver({ "slack-bot": process.env.SLACK_BOT_TOKEN ?? "" }),
    }),
  ],
});

Tools

| Tool | Effect | Approval | |---|---|---| | slack_list_channels | read | never | | slack_read_history | read | never | | slack_post_message | external-write | always | | slack_reply_in_thread | external-write | always |

Scopes your bot token needs

channels:read for listing, channels:history for reading, chat:write for posting. A missing scope comes back as an unauthorized failure naming Slack's own error, not as a silent no-op.

Behaviour worth knowing

Slack answers 200 with ok: false. This is the mistake worth not making: a toolkit that checks the HTTP status alone reports success for channel_not_found, not_in_channel and invalid_auth — and the model then believes it posted a message that never arrived. The envelope is read, not the status.

ratelimited is its own outcome, retryable, so the model waits rather than retrying with different arguments. invalid_auth is unauthorized and not retryable, because trying again cannot fix a token.

Pagination follows the cursor to a ceiling and reports truncated when it stopped early.

Message text is untrusted content. It reaches the model inside the runtime's envelope — a Slack message saying "ignore your instructions" arrives as data.

Licence

MIT — see LICENSE.

Copyright (c) 2026 Azeem Sarwar and Rise Experts.