green-setup

A repository setup command detects the project's test and type or compile commands and saves them in .green-keeper/config.json. It can also identify a faster quick test command.

In plain words
What is it for?
Use it when configuring a project so Green Keeper and its hooks can run tests and type checks consistently.
Why use it?
It gives automated checks the exact commands needed for this project instead of making them guess. It asks for confirmation before saving and checks whether the repository currently passes.

Command

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/localplugins/plugins/green-setup
Clone the repo
git clone --depth 1 https://github.com/localplugins/plugins
Per session 34 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 293 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00034 $0.00293
Opus 5 $0.00017 $0.00147
Sonnet 5 $0.00007 $0.00059
Haiku 4.5 $0.00003 $0.00029

Measured yesterday against content hash 73f1294899ed, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

green-setup scanned grade A with 0 findings 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 yesterday.

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.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

green-keeper/commands/green-setup.md · 18 lines

What it actually says

Green Setup

Configure Green Keeper for this repo. Arguments: $ARGUMENTS

Steps

  1. Apply the runner-detection skill to infer the test, typecheck, and (if possible) a fast quickTest command from the project files. Honor any explicit --test/--typecheck/--quick overrides in the arguments.
  2. Show the detected commands and confirm with the user before saving (these will run automatically via hooks).
  3. Write .green-keeper/config.json with the schema from runner-detection (test, typecheck, quickTest, enforce: true, maxAttempts: 3, postToolUseTypecheck: false). Never overwrite an existing config without confirming.
  4. Tell the user to add .green-keeper/state/ to their .gitignore (config.json itself is safe to commit and share with the team).
  5. Do a quick sanity run of typecheck and quickTest and report whether the repo currently starts green or red.

Never access the network.

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. yesterday First seen · 18 lines · 34 tokens per session scan A 73f1294899ed

Subscribe to this mod's changes

green-setup is a command published in the GitHub repository localplugins/plugins (5 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 293 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.