Skip to content
Back to search

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.

Checked today

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
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/ejboy--agent-scripts/badge.svg)](/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

i

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.

  1. # agent-scripts
  2. [![Version](https://img.shields.io/badge/version-0.3.0-blue)](https://github.com/ejboy/agent-scripts/tree/v0.3.0)
  3. [![skills.sh](https://skills.sh/b/ejboy/agent-scripts)](https://skills.sh/ejboy/agent-scripts)
  4. 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.
  5. Agent Scripts provides these Agent Skills:
  6. - `repolink` for repository and local-tool discovery
  7. - `lite-tools` for quieter, token-efficient Maven, npm/Node, and Go test workflows
  8. - [`lightweight-monitoring`](skills/lightweight-monitoring/SKILL.md) (experimental) for minimal application monitoring with framework-native facilities and optional StatLite integrations
  9. - [`coilbase-spring-migration`](skills/coilbase-spring-migration/SKILL.md) (experimental) for bounded Spring Boot JDBC migration guidance
  10. Related: [AI Badger handoff skills](https://github.com/PVRLabs/aibadger/tree/main/skills)
  11. provide `handoff` for continuing sessions in Badger and `badger-review` for independent reviews.
  12. ## Tools
  13. ### Core Build & Test Wrappers
  14. - `mvn-lite` — compact Maven output for builds, tests, and verification runs
  15. - `npm-lite` — compact output for supported npm test and verification workflows (measured output reductions up to 99.99%)
  16. - `go-lite` — compact `go test` output for coding agents
  17. ### Browser & Discovery Helpers
  18. - `html-screenshot` — render local HTML or URLs to PNG
  19. - `launch-browser` — launch Chrome with DevTools enabled
  20. - `vscode-test` — compact, approval-friendly VS Code extension testing
  21. - `repolink` — RepoLink, for local repository and agent-capability discovery
  22. ### Local Workload Helper
  23. - `slopstop` — scan for stale developer workloads on macOS and optionally stop verified idle services
  24. See [choosing the right tool](docs/choosing-tools.md) for measured output savings, recommended use cases, and experiment limitations.
  25. Public, standalone utilities live under `scripts/`. Repository release tooling lives
  26. separately under `maintainers/` and is not part of the public utility interface.
  27. ## Installation
  28. The simplest installer keeps the complete repository under
  29. `~/.local/share/agent-scripts` and symlinks the four core commands into
  30. `~/.local/bin`:
  31. ```bash
  32. curl -fsSL https://raw.githubusercontent.com/ejboy/agent-scripts/main/install.sh | bash
  33. ```
  34. The installer uses Git when available and otherwise downloads a complete
  35. archive snapshot. It does not edit shell startup files. Adding the repository's
  36. full `scripts/` directory to `PATH` remains the recommended setup for access to
  37. all current and future scripts:
  38. ```bash
  39. export PATH="$HOME/.local/share/agent-scripts/scripts:$PATH"
  40. ```
  41. For a manual Git installation, clone the repository and add its `scripts/`
  42. directory to `PATH`:
  43. ```bash
  44. mkdir -p "$HOME/.local/share"
  45. git clone https://github.com/ejboy/agent-scripts.git ~/.local/share/agent-scripts
  46. export PATH="$HOME/.local/share/agent-scripts/scripts:$PATH"
  47. ```
  48. 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.
  49. > [!NOTE]
  50. > Skills and command installation are separate. See
  51. > [`skills/README.md`](skills/README.md) for installing this repository's
  52. > skills, including the optional monitoring experiment. The repository installer installs
  53. > commands only and does not invoke the Skills CLI.
  54. See the [installation guide](docs/installation.md) for shell setup, updates, uninstalling, and optional project-local pinning.
  55. ## mvn-lite
  56. *Introverted Maven for coding agents.*
  57. ```bash
  58. mvn-lite clean verify
  59. mvn-lite -pl app -am test
  60. mvn-lite --full dependency:tree
  61. ```
  62. See the [`mvn-lite` guide](docs/mvn-lite.md) for options, output behavior,
  63. failure logs, scope, and real-project evidence.
  64. ## npm-lite
  65. `npm-lite` reduces successful output for the two supported npm workflows and
  66. direct Node test runs while keeping other invocations unchanged.
  67. ```bash
  68. npm-lite run verify
  69. npm-lite run test:unit
  70. npm-lite node --test path/to/test.js
  71. ```
  72. See the [`npm-lite` guide](docs/npm-lite.md) for supported commands, count
  73. formats, failure diagnostics, logs, limitations, and experiment evidence.
  74. ## go-lite
  75. `go-lite` captures routine `go test` output and reports a compact success line
  76. while retaining complete failure logs. Other Go commands pass through normally.
  77. ```bash
  78. go-lite test ./...
  79. go-lite test ./internal/storage
  80. go-lite --full test ./...
  81. ```
  82. See the [`go-lite` guide](docs/go-lite.md) for cache behavior, failure logs,
  83. limitations, and sandbox expectations.
  84. ## slopstop
  85. `slopstop` reports safe-to-stop Colima, Gradle, and mvnd candidates only after
  86. checking their native status. Old or resource-heavy processes appear under
  87. “Needs review” and are never stopped automatically. The default scan is
  88. read-only; `--stop` confirms once, and `--stop-safe` stops safe candidates
  89. without prompting. Each safe candidate is checked again immediately before
  90. stopping. SlopStop supports macOS only.
  91. ```bash
  92. slopstop
  93. slopstop --stop
  94. ```
  95. The current detector rules and limitations are in the
  96. [SlopStop guide](docs/slopstop.md). During dogfooding, add this
  97. repository's `scripts/` directory to `PATH` as shown above.
  98. ## launch-browser
  99. `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.
  100. ```bash
  101. launch-browser
  102. launch-browser --visible
  103. launch-browser --foreground --isolated
  104. launch-browser --stop
  105. launch-browser --help
  106. ```
  107. 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`.
  108. The temporary launch log is removed when Chrome exits normally; abnormal-exit logs remain available for diagnostics.
  109. ## html-screenshot
  110. `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.
  111. ```bash
  112. html-screenshot examples/page.html
  113. html-screenshot --width 1440 --height 900 --wait 1000 -o /tmp/page.png examples/page.html
  114. html-screenshot --scale 2 https://example.com
  115. ```
  116. 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.
  117. Release maintenance is documented in [maintainers/README.md](maintainers/README.md).
  118. ## vscode-test
  119. `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.
  120. ```bash
  121. vscode-test launch --extension-development-path ./extension ./fixture
  122. vscode-test launch --extension-development-path ./extension ./review.code-workspace
  123. vscode-test inspect page
  124. vscode-test inspect panel
  125. vscode-test text panel --limit 2000
  126. vscode-test controls page --filter "AI Badger"
  127. vscode-test click --aria-label "Source Control"
  128. vscode-test palette "AI Badger: Copy Workspace Changes for Review"
  129. vscode-test wait-control --aria-label "AI Badger: Copy Changes for Review" --count 1
  130. vscode-test activate
  131. vscode-test screenshot /tmp/vscode.png
  132. vscode-test stop
  133. ```
  134. 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).
  135. ## RepoLink
  136. 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.
  137. ```bash
  138. repolink
  139. repolink command html-screenshot
  140. repolink commands
  141. repolink commands --check
  142. repolink add ~/src/aibadger
  143. repolink show aibadger
  144. repolink get aibadger
  145. ```
  146. See [choosing the right tool](docs/choosing-tools.md#targeted-repository-discovery) for efficient discovery guidance, registry details, and measured results.
  147. The old `repo-map` command remains as a deprecated compatibility wrapper for existing scripts and skills. New instructions should use `repolink`.
  148. ## Status
  149. 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.
  150. MIT licensed; see [LICENSE](LICENSE).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.