kraken-autonomy-levels

kraken-autonomy-levels is a skill for Claude Code from krakenfx/kraken-cli. It costs 22 tokens per session (1,267 once invoked), scanned A, original, MIT.

A staged plan for moving from manually checking Kraken, a cryptocurrency exchange, to letting an agent trade automatically. It defines several permission levels, starting with read-only access and paper trading.

In plain words
What is it for?
Use it to inspect market and account data, test trading strategies with simulated money, and gradually prepare for automated Kraken trading.
Why use it?
It helps reduce the risk of giving an agent trading and money-moving access too soon. Each stage lets you test behavior before increasing its permissions.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: built for openclaw.

Part of the kraken-cli plugin — 59 skills, 1 MCP server shipped together

Good fit Use it to inspect market and account data, test trading strategies with simulated money, and gradually prepare for automated Kraken trading.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/krakenfx/kraken-cli/kraken-autonomy-levels
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.

Any agent
npx skills add krakenfx/kraken-cli --skill kraken-autonomy-levels
Clone the repo
git clone --depth 1 https://github.com/krakenfx/kraken-cli

Made for: Claude Code.

Or install kraken-cli, the plugin that ships this one along with the rest of its 59 skills, 1 MCP server.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for kraken-autonomy-levels

README.md
[![agentmods](https://agentmods.dev/badge/skills/krakenfx/kraken-cli/kraken-autonomy-levels/github.svg)](https://agentmods.dev/skills/krakenfx/kraken-cli/kraken-autonomy-levels)
Your own site
<a href="https://agentmods.dev/skills/krakenfx/kraken-cli/kraken-autonomy-levels"><img src="https://agentmods.dev/badge/skills/krakenfx/kraken-cli/kraken-autonomy-levels/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for kraken-autonomy-levels

Your own site · 80×15
<a href="https://agentmods.dev/skills/krakenfx/kraken-cli/kraken-autonomy-levels"><img src="https://agentmods.dev/badge/skills/krakenfx/kraken-cli/kraken-autonomy-levels.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,267 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 5 findings, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Excessive Agency · line 83
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
  • low Privilege Escalation · line 20
    Skill requests more permissions than appear necessary for its stated functionality. Review if elevated access is justified.
    Fix: Request only the minimum permissions required. Document why each permission is needed. Remove broad permissions like '*' or 'all'.
  • low Privilege Escalation · line 51
    Skill requests more permissions than appear necessary for its stated functionality. Review if elevated access is justified.
    Fix: Request only the minimum permissions required. Document why each permission is needed. Remove broad permissions like '*' or 'all'.
  • low Privilege Escalation · line 76
    Skill requests more permissions than appear necessary for its stated functionality. Review if elevated access is justified.
    Fix: Request only the minimum permissions required. Document why each permission is needed. Remove broad permissions like '*' or 'all'.
  • low Privilege Escalation · line 113
    Skill requests more permissions than appear necessary for its stated functionality. Review if elevated access is justified.
    Fix: Request only the minimum permissions required. Document why each permission is needed. Remove broad permissions like '*' or 'all'.
How audits are shown
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.1 $0.00022 $0.01267
Opus 5 $0.00011 $0.00633
Sonnet 5 $0.00004 $0.00253
Haiku 4.5 $0.00002 $0.00127

Measured 10d ago against content hash 1f8bac1c3341, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

kraken-autonomy-levels 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 10d ago.

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.

skills/kraken-autonomy-levels/SKILL.md · 135 lines

How it starts

The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.

kraken-autonomy-levels

Use this skill to help a trader move from hands-on CLI usage to fully autonomous agent trading in safe, incremental steps.

Level 1: Read-Only Agent

The agent reads market data and account state. No API key needed for public data; a query-only key for account data.

Kraken API key permissions: Query Funds, Query Open Orders & Trades

export KRAKEN_API_KEY="query-only-key"
export KRAKEN_API_SECRET="query-only-secret"

kraken ticker BTCUSD -o json 2>/dev/null
kraken balance -o json 2>/dev/null
kraken open-orders -o json 2>/dev/null

The agent can inform, alert, and recommend. It cannot place orders, cancel orders, or move funds.

Level 2: Paper Trading Agent

The agent tests strategies against live prices with zero risk. No API key needed.

kraken workspace create sandbox --capital 10000 --mode paper -o json 2>/dev/null
export KRAKEN_WORKSPACE=sandbox
kraken paper buy BTCUSD 0.01 -o json 2>/dev/null
kraken workspace status -o json 2>/dev/null
kraken workspace reset -o json --yes 2>/dev/null

Run paper strategies repeatedly. Compare results across parameter changes. Only move to Level 3 after consistent paper performance.

Level 3: Supervised Trading Agent

The agent places real orders, but a human confirms each one. The API key has trading permissions, but the agent validates before executing and waits for human approval.

Kraken API key permissions: Query Funds, Create & Modify Orders, Cancel/Close Orders

export KRAKEN_API_KEY="trade-key"
export KRAKEN_API_SECRET="trade-secret"

# Step 1: Agent validates the order (no submission)
kraken order buy BTCUSD 0.001 --type limit --price 50000 --validate -o json 2>/dev/null

# Step 2: Agent presents the validated order to the human
# Step 3: Human approves or rejects

# Step 4: Agent executes only after approval
kraken order buy BTCUSD 0.001 --type limit --price 50000 -o json 2>/dev/null

Safety controls at this level:

  • Always --validate before executing
  • Always enable the dead man's switch for the session: kraken order cancel-after 300 -o json
  • Check open-orders after every trade to verify state

Read the full file on GitHub · 135 lines

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. 10d ago First seen · 135 lines · 22 tokens per session scan A 1f8bac1c3341

Subscribe to this mod's changes

kraken-autonomy-levels is a skill published in the GitHub repository krakenfx/kraken-cli (714 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 1,267 once invoked, about $0.0001 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-30.

Related

Other skills, from other repositories