Commit

eeco-claude-plugin

feat: initial eeco Claude Code plugin (v0.1.0)

Three user-triggered slash commands (/eeco:go, /eeco:ask, /eeco:report-bug)
that shell out to the eeco binary. Installable as a single-plugin marketplace.
No SDK, no bundled binary; requires eeco on PATH.

ajhahnde · May 2026 · b9d95bd9745d07f4bc1e1a6ed52b7a6c35833455 · view on GitHub →

added .claude-plugin/marketplace.json

 @@ -0,0 +1,14 @@ 
 + { 
 +   "name": "ajhahnde", 
 +   "owner": { 
 +     "name": "Anton Hahn" 
 +   }, 
 +   "description": "eeco's tools for Claude Code — drive the no-AI-spend knowledge layer from inside your session.", 
 +   "plugins": [ 
 +     { 
 +       "name": "eeco", 
 +       "source": "./", 
 +       "description": "Claude Code commands for eeco — assemble the context brief, run the no-AI-spend knowledge search, and file friction reports straight from the binary." 
 +     } 
 +   ] 
 + } 

added .claude-plugin/plugin.json

 @@ -0,0 +1,12 @@ 
 + { 
 +   "name": "eeco", 
 +   "version": "0.1.0", 
 +   "description": "Claude Code commands for eeco — assemble the context brief, run the no-AI-spend knowledge search, and file friction reports straight from the binary.", 
 +   "author": { 
 +     "name": "Anton Hahn" 
 +   }, 
 +   "homepage": "https://github.com/ajhahnde/eeco", 
 +   "repository": "https://github.com/ajhahnde/eeco-claude-plugin", 
 +   "license": "PolyForm-Noncommercial-1.0.0", 
 +   "keywords": ["eeco", "cli", "knowledge", "workflow", "context"] 
 + } 

added .github/workflows/ci.yml

 @@ -0,0 +1,27 @@ 
 + name: CI 
 +  
 + on: 
 +   push: 
 +     branches: [main] 
 +   pull_request: 
 +     branches: [main] 
 +  
 + jobs: 
 +   validate: 
 +     runs-on: ubuntu-latest 
 +     steps: 
 +       - uses: actions/checkout@v4 
 +  
 +       - name: Validate JSON manifests 
 +         run: | 
 +           jq empty .claude-plugin/plugin.json 
 +           jq empty .claude-plugin/marketplace.json 
 +  
 +       - name: Check required files exist 
 +         run: | 
 +           test -f LICENSE 
 +           test -f README.md 
 +           test -f CHANGELOG.md 
 +           test -f commands/go.md 
 +           test -f commands/ask.md 
 +           test -f commands/report-bug.md 

added .gitignore

@@ -0,0 +1 @@

.DS_Store

added CHANGELOG.md

 @@ -0,0 +1,25 @@ 
 + # Changelog 
 +  
 + All notable changes to the eeco Claude Code plugin are documented in this 
 + file. 
 +  
 + The format is based on 
 + [Keep a Changelog](https://keepachangelog.com/en/1.1.0/). This plugin 
 + follows [Semantic Versioning](https://semver.org/spec/v2.0.0.html). 
 +  
 + ## [0.1.0] - 2026-05-30 
 +  
 + ### Added 
 +  
 + - Initial release. Three user-triggered slash commands that shell out to the 
 +   [`eeco`](https://github.com/ajhahnde/eeco) binary: 
 +   - `/eeco:go` — assemble and read the deterministic context brief. 
 +   - `/eeco:ask` — run the no-AI-spend ranked search over the knowledge layer. 
 +   - `/eeco:report-bug` — file a friction report and print a pre-filled 
 +     issue URL. 
 + - Installable from this repository as a single-plugin marketplace 
 +   (`/plugin marketplace add ajhahnde/eeco-claude-plugin` → 
 +   `/plugin install eeco@ajhahnde`). 
 + - Requires the `eeco` binary on `PATH`; the plugin bundles no binary. 
 +  
 + [0.1.0]: https://github.com/ajhahnde/eeco-claude-plugin/releases/tag/v0.1.0 

added LICENSE

 @@ -0,0 +1,75 @@ 
 + Required Notice: Copyright 2026 ajhahnde (https://github.com/ajhahnde/eeco-claude-plugin) 
 +  
 + # PolyForm Noncommercial License 1.0.0 
 +  
 + <https://polyformproject.org/licenses/noncommercial/1.0.0> 
 +  
 + ## Acceptance 
 +  
 + In order to get any license under these terms, you must agree to them as both strict obligations and conditions to all your licenses. 
 +  
 + ## Copyright License 
 +  
 + The licensor grants you a copyright license for the software to do everything you might do with the software that would otherwise infringe the licensor's copyright in it for any permitted purpose.  However, you may only distribute the software according to [Distribution License](#distribution-license) and make changes or new works based on the software according to [Changes and New Works License](#changes-and-new-works-license). 
 +  
 + ## Distribution License 
 +  
 + The licensor grants you an additional copyright license to distribute copies of the software.  Your license to distribute covers distributing the software with changes and new works permitted by [Changes and New Works License](#changes-and-new-works-license). 
 +  
 + ## Notices 
 +  
 + You must ensure that anyone who gets a copy of any part of the software from you also gets a copy of these terms or the URL for them above, as well as copies of any plain-text lines beginning with `Required Notice:` that the licensor provided with the software.  For example: 
 +  
 + > Required Notice: Copyright Yoyodyne, Inc. (http://example.com) 
 +  
 + ## Changes and New Works License 
 +  
 + The licensor grants you an additional copyright license to make changes and new works based on the software for any permitted purpose. 
 +  
 + ## Patent License 
 +  
 + The licensor grants you a patent license for the software that covers patent claims the licensor can license, or becomes able to license, that you would infringe by using the software. 
 +  
 + ## Noncommercial Purposes 
 +  
 + Any noncommercial purpose is a permitted purpose. 
 +  
 + ## Personal Uses 
 +  
 + Personal use for research, experiment, and testing for the benefit of public knowledge, personal study, private entertainment, hobby projects, amateur pursuits, or religious observance, without any anticipated commercial application, is use for a permitted purpose. 
 +  
 + ## Noncommercial Organizations 
 +  
 + Use by any charitable organization, educational institution, public research organization, public safety or health organization, environmental protection organization, or government institution is use for a permitted purpose regardless of the source of funding or obligations resulting from the funding. 
 +  
 + ## Fair Use 
 +  
 + You may have "fair use" rights for the software under the law. These terms do not limit them. 
 +  
 + ## No Other Rights 
 +  
 + These terms do not allow you to sublicense or transfer any of your licenses to anyone else, or prevent the licensor from granting licenses to anyone else.  These terms do not imply any other licenses. 
 +  
 + ## Patent Defense 
 +  
 + If you make any written claim that the software infringes or contributes to infringement of any patent, your patent license for the software granted under these terms ends immediately. If your company makes such a claim, your patent license ends immediately for work on behalf of your company. 
 +  
 + ## Violations 
 +  
 + The first time you are notified in writing that you have violated any of these terms, or done anything with the software not covered by your licenses, your licenses can nonetheless continue if you come into full compliance with these terms, and take practical steps to correct past violations, within 32 days of receiving notice.  Otherwise, all your licenses end immediately. 
 +  
 + ## No Liability 
 +  
 + ***As far as the law allows, the software comes as is, without any warranty or condition, and the licensor will not be liable to you for any damages arising out of these terms or the use or nature of the software, under any kind of legal claim.*** 
 +  
 + ## Definitions 
 +  
 + The **licensor** is the individual or entity offering these terms, and the **software** is the software the licensor makes available under these terms. 
 +  
 + **You** refers to the individual or entity agreeing to these terms. 
 +  
 + **Your company** is any legal entity, sole proprietorship, or other kind of organization that you work for, plus all organizations that have control over, are under the control of, or are under common control with that organization.  **Control** means ownership of substantially all the assets of an entity, or the power to direct its management and policies by vote, contract, or otherwise.  Control can be direct or indirect. 
 +  
 + **Your licenses** are all the licenses granted to you for the software under these terms. 
 +  
 + **Use** means anything you do with the software requiring one of your licenses. 

added README.md

 @@ -0,0 +1,68 @@ 
 + <div align="center"> 
 +  
 + <h1>eeco — Claude Code plugin</h1> 
 +  
 +   <p><i>Drive eeco's knowledge layer from inside Claude Code.</i></p> 
 +  
 + <p> 
 +     <a href="https://github.com/ajhahnde/eeco-claude-plugin/actions/workflows/ci.yml"><img src="https://img.shields.io/badge/CI-passing-brightgreen" alt="CI"></a> 
 +     <a href="LICENSE"><img src="https://img.shields.io/badge/license-source--available-orange" alt="License"></a> 
 +     <a href="https://github.com/ajhahnde/eeco"><img src="https://img.shields.io/badge/requires-eeco-blue" alt="Requires eeco"></a> 
 +   </p> 
 +  
 + </div> 
 +  
 + --- 
 +  
 + This plugin adds three user-triggered slash commands to Claude Code that shell 
 + out to the [`eeco`](https://github.com/ajhahnde/eeco) binary. It bundles no 
 + binary and makes no AI calls of its own — each command runs `eeco` locally and 
 + brings its output into your conversation. 
 +  
 + ## Prerequisites 
 +  
 + The `eeco` binary must be installed and on your `PATH` (any `v1.x`). See the 
 + [eeco repository](https://github.com/ajhahnde/eeco) for install instructions. 
 + Verify with: 
 +  
 + ``` 
 + eeco --version 
 + ``` 
 +  
 + ## Install 
 +  
 + From inside Claude Code: 
 +  
 + ``` 
 + /plugin marketplace add ajhahnde/eeco-claude-plugin 
 + /plugin install eeco@ajhahnde 
 + ``` 
 +  
 + ## Commands 
 +  
 + - **`/eeco:go`** — assemble and read eeco's deterministic context brief (the 
 +   knowledge layer distilled). Pass through `--brief`, `--json`, `--metrics`, 
 +   `--copy`, `--write PATH`. Example: `/eeco:go --metrics`. 
 + - **`/eeco:ask`** — a deterministic, no-AI-spend ranked search over memory and 
 +   project knowledge. Pass through `--limit N`, `--json`. Example: 
 +   `/eeco:ask deployment steps --limit 5`. 
 + - **`/eeco:report-bug`** — file a friction report; writes a local record and 
 +   prints a pre-filled GitHub-issue URL (nothing is sent automatically). Pass 
 +   through `--note TEXT`, `--cmd CMD`. Example: 
 +   `/eeco:report-bug --note "brief was slow" --cmd "eeco go"`. 
 +  
 + ## Feedback 
 +  
 + Hit a rough edge? Use **`/eeco:report-bug`** — it records the friction locally 
 + and hands you a pre-filled issue URL. 
 +  
 + ## See also 
 +  
 + - [eeco](https://github.com/ajhahnde/eeco) — the AI-agnostic knowledge layer and 
 +   workflow companion this plugin drives. 
 +  
 + ## License 
 +  
 + PolyForm Noncommercial 1.0.0 — free for noncommercial use; commercial use 
 + requires a separate license. See [LICENSE](LICENSE) and the 
 + [eeco commercial-license terms](https://github.com/ajhahnde/eeco/blob/main/COMMERCIAL-LICENSE.md). 

added commands/ask.md

 @@ -0,0 +1,25 @@ 
 + --- 
 + description: Search eeco's knowledge layer with a deterministic, no-AI-spend ranked search over memory and project knowledge. Flags --limit N, --json. 
 + argument-hint: "[query] [--limit N] [--json]" 
 + --- 
 +  
 + Run eeco's knowledge search for the user's query. 
 +  
 + Use the Bash tool to run: 
 +  
 + ``` 
 + eeco ask $ARGUMENTS 
 + ``` 
 +  
 + `eeco ask` runs a deterministic ranked search over memory facts and project 
 + knowledge. No AI call is made and nothing is sent anywhere — it is a local, 
 + zero-spend lookup. Read the ranked results and use them to answer the user. 
 +  
 + Notable flags you can pass through `$ARGUMENTS`: 
 +  
 + - `--limit N` — cap results at N (default 10). 
 + - `--json` — emit results as JSON. 
 +  
 + If the command fails because `eeco` is not found, tell the user the plugin 
 + requires the `eeco` binary on `PATH` and point them to the install instructions 
 + at https://github.com/ajhahnde/eeco — do not attempt to install it yourself. 

added commands/go.md

 @@ -0,0 +1,29 @@ 
 + --- 
 + description: Assemble and read eeco's deterministic context brief (knowledge layer distilled). Flags --brief, --json, --metrics, --copy, --write PATH. 
 + argument-hint: "[--brief] [--json] [--metrics] [--copy] [--write PATH]" 
 + --- 
 +  
 + Run eeco's context brief and bring it into the conversation. 
 +  
 + Use the Bash tool to run: 
 +  
 + ``` 
 + eeco go $ARGUMENTS 
 + ``` 
 +  
 + `eeco go` assembles a deterministic brief from the project's knowledge layer 
 + (memory facts, queue, notes) and prints it to stdout. No AI call is made by the 
 + command itself. Read the brief, then use it as grounding for whatever the user 
 + asks next. 
 +  
 + Notable flags you can pass through `$ARGUMENTS`: 
 +  
 + - `--brief` — print only the brief body, without header/footer chrome. 
 + - `--json` — emit the brief as JSON (nine frozen top-level keys). 
 + - `--metrics` — print an assembly-metrics readout to stderr after the brief. 
 + - `--copy` — copy the brief to the system clipboard. 
 + - `--write PATH` — write the brief to PATH instead of stdout. 
 +  
 + If the command fails because `eeco` is not found, tell the user the plugin 
 + requires the `eeco` binary on `PATH` and point them to the install instructions 
 + at https://github.com/ajhahnde/eeco — do not attempt to install it yourself. 

added commands/report-bug.md

 @@ -0,0 +1,26 @@ 
 + --- 
 + description: File an eeco friction report. Writes a local record and prints a pre-filled GitHub issue URL — nothing is sent automatically. Flags --note TEXT, --cmd CMD. 
 + argument-hint: "[--note \"TEXT\"] [--cmd \"CMD\"]" 
 + --- 
 +  
 + File a friction report for eeco. 
 +  
 + Use the Bash tool to run: 
 +  
 + ``` 
 + eeco report-bug $ARGUMENTS 
 + ``` 
 +  
 + `eeco report-bug` records a local friction report and prints a pre-filled 
 + GitHub-issue URL. Nothing is sent anywhere automatically — the user decides 
 + whether to open the URL. After running it, show the user the printed URL so they 
 + can file the issue if they choose. 
 +  
 + Notable flags you can pass through `$ARGUMENTS`: 
 +  
 + - `--note TEXT` — attach a longer note to the report. 
 + - `--cmd CMD` — record the command that triggered the friction. 
 +  
 + If the command fails because `eeco` is not found, tell the user the plugin 
 + requires the `eeco` binary on `PATH` and point them to the install instructions 
 + at https://github.com/ajhahnde/eeco — do not attempt to install it yourself. 