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.
npx agentmods add skills/localplugins/plugins/runner-detectionnpx skills add localplugins/plugins --skill runner-detectiongit clone --depth 1 https://github.com/localplugins/pluginsWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00038 | $0.00572 |
| Opus 5 | $0.00019 | $0.00286 |
| Sonnet 5 | $0.00008 | $0.00114 |
| Haiku 4.5 | $0.00004 | $0.00057 |
Grade A, and why
runner-detection 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.
What it actually says
Runner Detection
Green Keeper needs two concrete shell commands for a repo: how to run the tests, and how to run the type/compile check. Detect them, confirm with the user, and cache them to .green-keeper/config.json.
Use when
- Running
/green-setupon a new repo. - A configured command is wrong and needs re-detecting.
- Writing or editing
.green-keeper/config.json.
Decision guide
- Identify the ecosystem from the manifest present:
package.json(Node/TS),pyproject.toml/setup.cfg/tox.ini(Python),go.mod(Go),Cargo.toml(Rust),Makefile(any). - Read the real commands, don't guess them. Prefer
scripts/targets already defined; CI config (.github/workflows) usually names the exact commands the team runs. - Pick a fast
quickTest. The hooks run it on every turn end and session start, so choose a changed-files or single-package subset when one exists; otherwise fall back to the fulltest. - Honor explicit overrides from
--test/--typecheck/--quickarguments — they win over detection. - Confirm before saving. These commands run automatically via hooks. Show them and get a yes.
- Never guess a destructive command. If you can't detect one, ask the user.
Quick reference
| Ecosystem | Typical test |
Typical typecheck |
|---|---|---|
| Node / TS | npm test / vitest run / jest |
tsc --noEmit |
| Python | pytest |
mypy . or pyright |
| Go | go test ./... |
go build ./... or go vet ./... |
| Rust | cargo test |
cargo check |
| Make-based | make test |
make check / make lint |
Deep references
references/ecosystem-detection.md— per-ecosystem detection walkthroughs (where to look, which runner to infer, how to pick a fastquickTest), plus Make/CI fallbacks.references/config-schema.md— the full.green-keeper/config.jsonschema: every field, type, default, validation notes, and worked examples per ecosystem.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 39 lines · 38 tokens per session scan A 4255e0ed8dc3
runner-detection is a skill published in the GitHub repository localplugins/plugins (5 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 572 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.
Other skills, from other repositories
brainstorm-okrs
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
pre-mortem
Run a pre-mortem risk analysis on a PRD or launch plan. Categorizes risks as Tigers (real problems), Paper Tigers (overblown concerns), and Elephants (unspoken worries), then classifies as launch-blocking, fast-follow, or track. Use when preparing for launch, stress-testing a product plan, or identifying what could go…
ab-test-analysis
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
dummy-dataset
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
retro
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.