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-shell-guard

v1.1.6

Published

OpenCode plugin that prevents LLM agents from abusing shell commands for code navigation and editing

Readme

Shell Guard Plugin

Prevents LLM agents from abusing shell commands for code navigation and editing.

Problem

When LLMs work on large tasks, they sometimes drift from using proper tools (Serena MCP, edit, grep, glob) and fall back to shell hacks like:

  • Get-Content file.rs | Select-String "pattern" instead of serena_search_for_pattern
  • Get-Content file.rs -Raw | sed 's/old/new/' | Set-Content file.rs instead of edit
  • rg "pattern" src/ instead of grep tool

This leads to brittle, error-prone operations that bypass the intended toolchain.

Solution

The plugin intercepts bash tool calls and detects:

  1. Source code search via shell (e.g., rg, grep, Select-String on .rs/.ts/.py files) → blocks and suggests grep/glob/Serena
  2. Source code edit via shell (e.g., Get-Content + Set-Content, sed -i) → blocks and suggests edit/Serena
  3. Redundant cd in commands → warns and suggests using workdir parameter

Architecture

shell-guard/
├── types.ts              # Violation, Rule types
├── plugin.ts             # OpenCode plugin entry point
├── rules/
│   ├── index.ts          # Rule registry
│   ├── source-code-edit.ts    # Edit detection
│   ├── source-code-search.ts  # Search detection
│   └── cd-warning.ts          # cd warning
└── utils/
    ├── command-parser.ts  # Command parsing utilities
    └── path-checker.ts   # Source file path detection

Configuration

Configure the plugin in opencode.json with project-specific options:

{
  "plugin": [
    ["./shell-guard/plugin.ts", {
      "sourceExtensions": ["rs", "ts", "tsx", "js", "jsx", "py", "cpp", "h", "hpp", "c", "json", "toml", "yaml"],
      "sourceDirs": ["src", "crates", "apps", "packages", "lib", "pkg"],
      "excludedDirs": ["\\temp\\", "/tmp/", "\\logs\\", "/logs/"],
      "excludedCommands": ["cargo", "npm", "pnpm", "git", "docker", "make", "cmake", "tsc", "pytest"]
    }]
  ]
}

Options

| Option | Type | Description | |--------|------|-------------| | sourceExtensions | string[] | File extensions to protect (without dots). Default: ["rs", "ts", "tsx", "js", "jsx", "py", "go", "java", "c", "cpp", "h", "hpp", "cs", "json", "toml", "yaml", "yml", "md", "sql", "kt", "swift", "rb", "php", "vue", "svelte"] | | sourceDirs | string[] | Directory names to treat as source roots. Default: ["src", "crates", "apps", "packages", "lib", "pkg"] | | excludedDirs | string[] | Directories to exclude from checks (always allowed). Default: ["\\temp\\", "/temp/", "\\tmp\\", "/tmp/", "\\logs\\", "/logs/"] | | excludedCommands | string[] | Commands to allowlist (never blocked). Default: [] |

Per-project examples

Rust project:

["./shell-guard/plugin.ts", {
  "sourceExtensions": ["rs", "toml", "json"],
  "sourceDirs": ["src", "crates", "tests", "benches"],
  "excludedCommands": ["cargo", "rustc", "clippy", "rustfmt"]
}]

TypeScript/React project:

["./shell-guard/plugin.ts", {
  "sourceExtensions": ["ts", "tsx", "js", "jsx", "json", "css", "scss"],
  "sourceDirs": ["src", "lib", "apps", "packages"],
  "excludedCommands": ["npm", "pnpm", "yarn", "tsc", "vite", "next"]
}]

C++ project:

["./shell-guard/plugin.ts", {
  "sourceExtensions": ["cpp", "cc", "cxx", "c", "h", "hpp", "hxx", "cmake", "txt"],
  "sourceDirs": ["src", "include", "lib", "vendor"],
  "excludedCommands": ["cmake", "make", "ninja", "clang", "gcc", "g++"]
}]

Behavior

  • Hard Block: Source code search/edit via shell → throws error with suggestion
  • Soft Warn: Redundant cd → logs warning (no enforcement)

Extending

Add new rules by:

  1. Creating a new file in rules/
  2. Implementing the Rule type: (command: string, config?: ShellGuardConfig) => Violation | null
  3. Adding it to rules/index.ts