Package Exports

@atbash/atbash-plugin
@atbash/atbash-plugin/dist/index.js

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@atbash/atbash-plugin) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

ATBASH Plugin

OpenClaw plugin that checks tool calls against an ATBASH policy API and can block execution when the verdict is BLOCKED.

Install

From a local directory:

openclaw plugins install /path/to/atbash-plugin

From npm:

openclaw plugins install @atbash/atbash-plugin

Note: OpenClaw may flag this plugin as unsafe during installation because it reads a private key file to identify the agent on the ATBASH platform. This is expected behaviour. Use the --dangerously-force-unsafe-install flag to proceed:

openclaw plugins install @atbash/atbash-plugin --dangerously-force-unsafe-install

The private key is used solely to sign requests to the ATBASH judge API and is never transmitted beyond that.

Setup

The plugin requires an agent key file to authenticate requests to the ATBASH API. By default it reads from:

~/.config/atbash/guard-client-key

The file can be JSON:

{
  "privKey": "your-hex-private-key",
  "pubKey": "your-hex-public-key"
}

Or key=value format:

privkey=your-hex-private-key
pubkey=your-hex-public-key

Optional helper script for skill-based checks

If you want a reusable skill to perform a one-shot guard check without exposing shell-level key extraction, install a helper script at:

~/.config/atbash/judge_via_api.js

The helper should:

read ~/.config/atbash/guard-client-key internally
call the judge API directly
print only the safe JSON result

A reference implementation is included in this repo at:

tools/judge_via_api.js

This repo path is a reference implementation, not the path that a reusable skill should hardcode.

Config

Configure it under plugins.entries["atbash-plugin"]:

{
  "plugins": {
    "entries": {
      "atbash-plugin": {
        "enabled": true,
        "config": {
          "enabled": true,
          "enforceDecision": true,
          "chromiaSecretPath": "~/.config/atbash/guard-client-key"
        }
      }
    }
  }
}

Config fields

Option	Description
`enabled`	Enable plugin logic
`enforceDecision`	If `true`, BLOCKED verdicts block tool execution. Default: `false`
`chromiaSecretPath`	Path to agent key file. Default: `~/.config/atbash/guard-client-key`
`debug`	Extra logging

How it works

Before each tool call, the plugin:

Loads the agent key pair from the key file
POSTs to the ATBASH judge API with the tool name and arguments
Waits for the API to return a verdict (the API handles all on-chain interaction)
Interprets the verdict:
- blocked → block tool execution (if enforceDecision: true)
- hold → allow
- allowed → allow

If the API is unreachable or returns an error, the plugin fails closed (blocks execution).

Fail-closed behaviour

The plugin blocks tool execution in the following cases:

Key file missing or unreadable
Judge API unreachable or returns a non-2xx status
Verdict is block

To make failures block instead, set enforceDecision: true and handle key/network issues before deployment.

@atbash/atbash-plugin