agentmods.dev

setup

setup is a command for Claude Code from manymee/claude-plugins. It costs 24 tokens per session (980 once invoked), scanned B, original, MIT.

A command for installing or updating exline's background status service, checking its requirements, building it, starting it, and registering it.

In plain words
What is it for?
Use it after installing or updating exline to verify dependencies and prepare the daemon.
Why use it?
It provides the setup sequence needed for the status service to work with the installed plugin version.

Command for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable. Also seen: reads .claude/ paths; mentions Claude Code.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the exline plugin — 2 commands, 4 hooks shipped together

not rated 2repo 8d ago B scan 24 tokens original MIT

Good fit Use it after installing or updating exline to verify dependencies and prepare the daemon.

Compare 6 commands from other repositories ↓
View source ↗ manymee/claude-plugins
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add manymee/claude-plugins
Claude Code
/plugin install exline

Made for: Claude Code.

Or install exline, the plugin that ships this one along with the rest of its 2 commands, 4 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for setup

README.md
[![agentmods](https://agentmods.dev/badge/commands/manymee/claude-plugins/setup/github.svg)](https://agentmods.dev/commands/manymee/claude-plugins/setup)
Your own site
<a href="https://agentmods.dev/commands/manymee/claude-plugins/setup"><img src="https://agentmods.dev/badge/commands/manymee/claude-plugins/setup/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for setup

Your own site · 80×15
<a href="https://agentmods.dev/commands/manymee/claude-plugins/setup"><img src="https://agentmods.dev/badge/commands/manymee/claude-plugins/setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 980 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00024 $0.00980
Opus 5.5 $0.00010 $0.00392
Sonnet 5.5 $0.00005 $0.00196
Haiku 4.5 $0.00002 $0.00098

Measured 2mo ago against content hash dafdf1cde885, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade B, and why

setup scanned grade B with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

`~/.claude/settings.json` (ask first, and show the change):
plugins/exline/commands/setup.md · 93 lines

How it starts

The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Set up (or update) the exline statusline daemon on this machine. This command is idempotent: run it after installing the plugin, and again after every plugin update (the statusline shows a "run /exline:setup" warning line when the installed plugin version differs from the running daemon).

Work through the steps below in order. Stop and tell the user what's missing if a prerequisite fails; don't half-install.

1. Resolve paths

  • Plugin root: ${CLAUDE_PLUGIN_ROOT}. If that literal string appears unexpanded above, resolve it instead from ~/.claude/plugins/installed_plugins.json: the entry whose key starts with exline@ has an installPath.
  • Data dir (survives plugin updates; the versioned plugin root does not): ~/.claude/plugins/data/exline-<marketplace> where <marketplace> is the part after @ in that registry key. Create it if missing.

2. Check dependencies

  • jq and nc must be on PATH (the client uses both).
  • elixir and mix must be on PATH. Elixir ~> 1.19 on OTP 28 is what's tested (mise.toml records the exact versions); mix.exs rejects older Elixir at build time.
  • Only check — never install anything on the user's behalf. If something is missing, report exactly what's needed (e.g. brew install jq; Elixir via brew/mise/asdf — their choice) and stop.

3. Build the release

From the plugin root:

mix deps.get --only prod
MIX_ENV=prod mix release --overwrite --path "<DATA>/rel"

Then install the client at a stable path:

install -m 755 "<PLUGIN_ROOT>/client" "<DATA>/client"

4. Start the daemon

If ~/Library/LaunchAgents/com.manymee.exline.plist already exists, the user has already chosen launchd: refresh and restart it (steps below) without asking. Otherwise this is first-time setup — ask before touching launchd: launchd (recommended — starts at login, restarts on crash) or a one-off manual start, and respect a decline.

launchd (macOS): render <PLUGIN_ROOT>/launchd/com.manymee.exline.plist.template — replace __BIN__ with <DATA>/rel/bin/exline, __WORKDIR__ with <DATA>, __LOG__ with $HOME/Library/Logs/exline.launchd.log (absolute paths, no ~) — and write it to ~/Library/LaunchAgents/com.manymee.exline.plist. Then:

Read the full file on GitHub · 93 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2mo ago First seen · 93 lines · 24 tokens per session scan B dafdf1cde885

Subscribe to this mod's changes

setup is a command published in the GitHub repository manymee/claude-plugins (2 stars, last pushed 8d ago), licensed MIT. It adds 24 tokens to every session and 980 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

DevOps and cloud
Related

setup compared with commands from other repositories

setup next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
setupmanymee/claude-pluginsCommand28d agoMITB24Claude Code
checklistgithub/spec-kitCommand148ktodayMITA13Claude Code
clarifygithub/spec-kitCommand148ktodayMITA27Claude Code
specifygithub/spec-kitCommand148ktodayMITA13Claude Code
convergegithub/spec-kitCommand148ktodayMITA35Claude Code
speckit.bug.testgithub/spec-kitCommand148ktodayMITA13Claude Code
analyzegithub/spec-kitCommand148ktodayMITA26Claude Code