agent-scripts
Token-efficient, local-first CLI tools for coding agents - compact Maven, npm/Node, and Go test output plus reusable development helpers.
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Check it deeper on your machine
It has changed since its scan on 11 Nov 2026.
As a Claude Code plugin, install it and then ask Claude Code:
/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/ejboy/agent-scripts with scanskillsafety
Or from a terminal, clone it and run it:
git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/ejboy/agent-scripts'
It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.
Badge for your README
Markdown
[](/listings/ejboy--agent-scripts)HTML
<a href="/listings/ejboy--agent-scripts"><img src="/api/listings/ejboy--agent-scripts/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
These steps run a script from the network that findsafeskills does not scan.
The simplest installer keeps the complete repository under `~/.local/share/agent-scripts` and symlinks the four core commands into `~/.local/bin`:
curl -fsSL https://raw.githubusercontent.com/ejboy/agent-scripts/main/install.sh | bash
The installer uses Git when available and otherwise downloads a complete archive snapshot. It does not edit shell startup files. Adding the repository's full `scripts/` directory to `PATH` remains the recommended setup for access to all current and future scripts:
export PATH="$HOME/.local/share/agent-scripts/scripts:$PATH"
For a manual Git installation, clone the repository and add its `scripts/` directory to `PATH`:
mkdir -p "$HOME/.local/share" git clone https://github.com/ejboy/agent-scripts.git ~/.local/share/agent-scripts export PATH="$HOME/.local/share/agent-scripts/scripts:$PATH"
Add the `export` line to your shell startup file to make the tools available in future sessions. You can then invoke the tools under `scripts/` by name from any project.
> [!NOTE] > Skills and command installation are separate. See > [`skills/README.md`](skills/README.md) for installing this repository's > skills, including the optional monitoring experiment. The repository installer installs > commands only and does not invoke the Skills CLI.
See the [installation guide](docs/installation.md) for shell setup, updates, uninstalling, and optional project-local pinning.
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
README.md · README · 212 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.
- # agent-scripts
- [](https://github.com/ejboy/agent-scripts/tree/v0.3.0)
- [](https://skills.sh/ejboy/agent-scripts)
- agent-scripts is a collection of small, local-first command-line utilities for AI-assisted development. Its primary tools, `mvn-lite`, `npm-lite`, and `go-lite`, reduce build and test output noise so agents retain more useful context. Supporting utilities cover browser automation, VS Code extension testing, and local repository discovery. Scripts use predictable command names, work well from PATH, and are designed to be easy for both developers and coding agents to discover and invoke.
- Agent Scripts provides these Agent Skills:
- - `repolink` for repository and local-tool discovery
- - `lite-tools` for quieter, token-efficient Maven, npm/Node, and Go test workflows
- - [`lightweight-monitoring`](skills/lightweight-monitoring/SKILL.md) (experimental) for minimal application monitoring with framework-native facilities and optional StatLite integrations
- - [`coilbase-spring-migration`](skills/coilbase-spring-migration/SKILL.md) (experimental) for bounded Spring Boot JDBC migration guidance
- Related: [AI Badger handoff skills](https://github.com/PVRLabs/aibadger/tree/main/skills)
- provide `handoff` for continuing sessions in Badger and `badger-review` for independent reviews.
- ## Tools
- ### Core Build & Test Wrappers
- - `mvn-lite` — compact Maven output for builds, tests, and verification runs
- - `npm-lite` — compact output for supported npm test and verification workflows (measured output reductions up to 99.99%)
- - `go-lite` — compact `go test` output for coding agents
- ### Browser & Discovery Helpers
- - `html-screenshot` — render local HTML or URLs to PNG
- - `launch-browser` — launch Chrome with DevTools enabled
- - `vscode-test` — compact, approval-friendly VS Code extension testing
- - `repolink` — RepoLink, for local repository and agent-capability discovery
- ### Local Workload Helper
- - `slopstop` — scan for stale developer workloads on macOS and optionally stop verified idle services
- See [choosing the right tool](docs/choosing-tools.md) for measured output savings, recommended use cases, and experiment limitations.
- Public, standalone utilities live under `scripts/`. Repository release tooling lives
- separately under `maintainers/` and is not part of the public utility interface.
- ## Installation
- The simplest installer keeps the complete repository under
- `~/.local/share/agent-scripts` and symlinks the four core commands into
- `~/.local/bin`:
- ```bash
- curl -fsSL https://raw.githubusercontent.com/ejboy/agent-scripts/main/install.sh | bash
- ```
- The installer uses Git when available and otherwise downloads a complete
- archive snapshot. It does not edit shell startup files. Adding the repository's
- full `scripts/` directory to `PATH` remains the recommended setup for access to
- all current and future scripts:
- ```bash
- export PATH="$HOME/.local/share/agent-scripts/scripts:$PATH"
- ```
- For a manual Git installation, clone the repository and add its `scripts/`
- directory to `PATH`:
- ```bash
- mkdir -p "$HOME/.local/share"
- git clone https://github.com/ejboy/agent-scripts.git ~/.local/share/agent-scripts
- export PATH="$HOME/.local/share/agent-scripts/scripts:$PATH"
- ```
- Add the `export` line to your shell startup file to make the tools available in future sessions. You can then invoke the tools under `scripts/` by name from any project.
- > [!NOTE]
- > Skills and command installation are separate. See
- > [`skills/README.md`](skills/README.md) for installing this repository's
- > skills, including the optional monitoring experiment. The repository installer installs
- > commands only and does not invoke the Skills CLI.
- See the [installation guide](docs/installation.md) for shell setup, updates, uninstalling, and optional project-local pinning.
- ## mvn-lite
- *Introverted Maven for coding agents.*
- ```bash
- mvn-lite clean verify
- mvn-lite -pl app -am test
- mvn-lite --full dependency:tree
- ```
- See the [`mvn-lite` guide](docs/mvn-lite.md) for options, output behavior,
- failure logs, scope, and real-project evidence.
- ## npm-lite
- `npm-lite` reduces successful output for the two supported npm workflows and
- direct Node test runs while keeping other invocations unchanged.
- ```bash
- npm-lite run verify
- npm-lite run test:unit
- npm-lite node --test path/to/test.js
- ```
- See the [`npm-lite` guide](docs/npm-lite.md) for supported commands, count
- formats, failure diagnostics, logs, limitations, and experiment evidence.
- ## go-lite
- `go-lite` captures routine `go test` output and reports a compact success line
- while retaining complete failure logs. Other Go commands pass through normally.
- ```bash
- go-lite test ./...
- go-lite test ./internal/storage
- go-lite --full test ./...
- ```
- See the [`go-lite` guide](docs/go-lite.md) for cache behavior, failure logs,
- limitations, and sandbox expectations.
- ## slopstop
- `slopstop` reports safe-to-stop Colima, Gradle, and mvnd candidates only after
- checking their native status. Old or resource-heavy processes appear under
- “Needs review” and are never stopped automatically. The default scan is
- read-only; `--stop` confirms once, and `--stop-safe` stops safe candidates
- without prompting. Each safe candidate is checked again immediately before
- stopping. SlopStop supports macOS only.
- ```bash
- slopstop
- slopstop --stop
- ```
- The current detector rules and limitations are in the
- [SlopStop guide](docs/slopstop.md). During dogfooding, add this
- repository's `scripts/` directory to `PATH` as shown above.
- ## launch-browser
- `launch-browser` is a separate macOS utility for starting Google Chrome with DevTools enabled at `http://127.0.0.1:9222`. It defaults to detached headless mode.
- ```bash
- launch-browser
- launch-browser --visible
- launch-browser --foreground --isolated
- launch-browser --stop
- launch-browser --help
- ```
- Successful detached launches record their service label and PID in `~/.browser-testing-profile/launch-state`, alongside the existing persistent browser profile. `--stop` validates that the recorded service uses the `xyz.pvrlabs.browser.*` prefix, asks `launchctl` to stop it, and verifies that both the recorded PID and DevTools endpoint have stopped before removing state. If the recorded PID still owns port `9222` after service removal, the script terminates that process directly. It never kills an arbitrary process merely because it uses port `9222`.
- The temporary launch log is removed when Chrome exits normally; abnormal-exit logs remain available for diagnostics.
- ## html-screenshot
- `html-screenshot` is a one-shot headless Chrome renderer for local HTML files, `file://` URLs, and HTTP(S) URLs. It does not start or manage a reusable browser instance.
- ```bash
- html-screenshot examples/page.html
- html-screenshot --width 1440 --height 900 --wait 1000 -o /tmp/page.png examples/page.html
- html-screenshot --scale 2 https://example.com
- ```
- It discovers standard macOS Chrome and Chromium application locations before checking `PATH`. Use `--chrome /path/to/chrome` or `CHROME_BIN=/path/to/chrome` to select an executable explicitly. The default viewport is 1280×720 with a 500 ms virtual-time wait. Successful default output is one line; use `--verbose` to retain Chrome diagnostics. Failed renders always include Chrome diagnostics.
- Release maintenance is documented in [maintainers/README.md](maintainers/README.md).
- ## vscode-test
- `vscode-test` provides fixed, reusable operations for macOS VS Code extension testing. Its stable command prefix avoids repeated approvals for changing inline JavaScript, while compact inspection and capped text output reduce transcript noise.
- ```bash
- vscode-test launch --extension-development-path ./extension ./fixture
- vscode-test launch --extension-development-path ./extension ./review.code-workspace
- vscode-test inspect page
- vscode-test inspect panel
- vscode-test text panel --limit 2000
- vscode-test controls page --filter "AI Badger"
- vscode-test click --aria-label "Source Control"
- vscode-test palette "AI Badger: Copy Workspace Changes for Review"
- vscode-test wait-control --aria-label "AI Badger: Copy Changes for Review" --count 1
- vscode-test activate
- vscode-test screenshot /tmp/vscode.png
- vscode-test stop
- ```
- The launch workspace can be a directory or an existing `.code-workspace` file. The default DevTools port is `9223`. Launch state, profiles, extension storage, and diagnostic logs are kept under `~/.agent-scripts/vscode-test`. Inspection does not accept arbitrary JavaScript: `inspect` emits a one-line JSON summary, `controls` lists visible accessible controls and their enclosing UI context, and `text` normalizes whitespace and defaults to at most 4,000 characters. `click` requires one exact visible aria-label match; `palette` selects one exact command; `wait-control` polls until the exact requested count is rendered. These operations require Node.js 22 or newer. Use `VSCODE_TEST_CODE_BIN` or `launch --code` to select another VS Code executable. `activate` requires managed launch state and focuses its recorded process ID, so it distinguishes test and regular windows from the same application bundle. Codex sandbox setup is documented in [the installation guide](docs/installation.md#codex-sandbox-access-for-browser-and-vs-code-tools).
- ## RepoLink
- RepoLink is a machine-local registry for discovering related repositories and useful commands across projects. Projects should document their required commands directly; coding agents can use `repolink` to discover additional machine-local capabilities and related repositories.
- ```bash
- repolink
- repolink command html-screenshot
- repolink commands
- repolink commands --check
- repolink add ~/src/aibadger
- repolink show aibadger
- repolink get aibadger
- ```
- See [choosing the right tool](docs/choosing-tools.md#targeted-repository-discovery) for efficient discovery guidance, registry details, and measured results.
- The old `repo-map` command remains as a deprecated compatibility wrapper for existing scripts and skills. New instructions should use `repolink`.
- ## Status
- This is an experimental, small utility collection. `mvn-lite` is not a complete Maven replacement, and this repository is not a build system, browser automation framework, AI agent, or task runner.
- MIT licensed; see [LICENSE](LICENSE).
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.