Scopink — the scope agent

Scopink checks if an action is within the scope of what was asked. You say "fix the login bug" and the agent proposes "also refactor the auth module, add tests, update docs, deploy to prod." Scopink takes the original request and the proposed actions and reports which are in-scope, borderline, or out-of-scope — with a reason for each. Scope creep is named, not hidden.

The word is coined: scope + instink → scopink — the rung where the agent learns to stay in bounds.

        .----.
       /  _   \
       |=[_]==|
  (`.--.____.---.'\
   `-./'\\_.'
      |  /.  .||
       \:-: .'
  LGB   `-'                     (archive piece, credited, until the portrait lands)

What it does

| You say | Scopink does | |---|---| | check fix auth/login.py \| update README.md \| deploy to prod | checks each action against the request's scope, reports verdicts | | scope fix the login bug in auth/login.py | extracts scope: verbs (fix) + targets (auth/login.py) | | status | shows the last check result | | ask tides: what are the tides? | forwards to a sibling over ACP, cited |

Rules: scope is extracted from the request's verbs and targets. An action is in-scope if its verbs and targets overlap. New targets or verbs make it out-of-scope. Scope-expanding language ("also", "while we're at it") makes it borderline. Nothing is invented.

Run it

npm i -g scopink     # or: npx scopink  (packaged agent; needs python3)
scopink              # launches agents/scopink/agent.py

Or from source:

git clone https://github.com/mrfentmen/scopink && cd scopink
python3 agents/scopink/agent.py

For forwarded questions, point it at a checkout of the answerer repo:

AWESOME_SERVERS_HOME=/path/to/awesome-servers scopink

Run the tests (23 of them, offline, including real child-process federation):

python3 agents/scopink/tests/test_agent.py

The honest parts

• Scope is extracted by rules (verbs + targets), not by model opinion.
• A scope decision that cannot be made honestly is reported as borderline, not faked.
• Vendored lockwork is credited line by line: kit/ from the ACP kit; federation.py from the polymath — vendored on 2026-10-18, kept standalone on purpose.

Built on top of: mrfentmen/awesome-servers (the watcher runtime, the feeds) and mrfentmen/superagents (the polymath and the sentry, the first two agents this one borrows transport and lockwork from) and mrfentmen/fedora-hat and mrfentmen/instink and mrfentmen/contextink and mrfentmen/rewind.