setup

setup is a skill for Claude Code from ololand-ai/ololand-plugins. It costs 55 tokens per session (922 once invoked), scanned A, original, Apache-2.0.

A connection and authentication guide for linking an OloLand account to Claude Code. It explains the browser sign-in process and the alternative agent-key method for automated environments.

In plain words
What is it for?
Use it when first connecting OloLand, reconnecting after an authentication error, or configuring OloLand for headless or continuous-integration environments.
Why use it?
It helps diagnose authentication errors and connection failures when OloLand commands or its server are unavailable.

Skill for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable. Also seen: mentions Claude Code.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the ololand-dd plugin — 22 skills, 54 commands, 3 agents shipped together

Good fit Use it when first connecting OloLand, reconnecting after an authentication error, or configuring OloLand for headless or continuous-integration environments.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add ololand-ai/ololand-plugins
Claude Code
/plugin install ololand-dd

Made for: Claude Code.

Or install ololand-dd, the plugin that ships this one along with the rest of its 22 skills, 54 commands, 3 agents.

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 setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/ololand-ai/ololand-plugins/setup/github.svg)](https://agentmods.dev/skills/ololand-ai/ololand-plugins/setup)
Your own site
<a href="https://agentmods.dev/skills/ololand-ai/ololand-plugins/setup"><img src="https://agentmods.dev/badge/skills/ololand-ai/ololand-plugins/setup/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 setup

Your own site · 80×15
<a href="https://agentmods.dev/skills/ololand-ai/ololand-plugins/setup"><img src="https://agentmods.dev/badge/skills/ololand-ai/ololand-plugins/setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 922 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.
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.00055 $0.00922
Opus 5.5 $0.00022 $0.00369
Sonnet 5.5 $0.00011 $0.00184
Haiku 4.5 $0.00006 $0.00092

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

Security

Grade A, and why

setup 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 12d 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.

plugins/ololand-dd/skills/setup/SKILL.md · 85 lines

How it starts

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

OloLand Setup

OloLand authenticates via OAuth (one-click sign-in) — there is no key to copy for normal use. The plugin's MCP server is OAuth-native: connecting it opens a sign-in page at api.ololand.ai, you approve, and you're done.

Connect (interactive — Claude Desktop / Cowork / Claude Code / Cursor / Grok Bot)

  1. Enable / connect the ololand MCP server in your client's connectors or plugin settings. On Cursor and Grok Bot this is the connector bundled by the Cursor-format plugin (.mcp.json → https://api.ololand.ai/mcp).
  2. The host opens the OloLand sign-in page at https://api.ololand.ai — sign in with email or Google and click Approve.
  3. That's it. Try any OloLand command:
    • /dd-analyze — Run bounded extraction, risk, and financial-snapshot processing for a deal; cross-document reconciliation is a separate explicit tool/workflow
    • /similar-deals — Find comparable transactions

If you see OloLand tools in your tools list, you're connected.

The sign-in runs on a single canonical host and self-heals the browser handoff, so it works in Cowork and Desktop. If a sign-in window doesn't return on the first try, just reconnect the server and approve again.

Headless / CI (no browser)

Automated environments can't do an interactive sign-in, so they use a long-lived agent key as a Bearer token. One command does the wiring — no hand-editing JSON:

  1. Get a key at https://api.ololand.ai/connect (sign in → Generate new key, starts with olo_agent_sk_), and export it:
    export OLOLAND_AGENT_KEY=olo_agent_sk_...
    
  2. Run the setup script — it adds the OloLand MCP server to your .mcp.json, preserving any servers already there:
    "${CLAUDE_PLUGIN_ROOT}/scripts/setup_headless.sh"
    
    The config references ${OLOLAND_AGENT_KEY} rather than the literal key, so the secret stays in your environment, not on disk. Flags: --config <path> targets a different file; --inline-key writes the literal key for ephemeral CI that can't set an env var (gitignore that config).
  3. Restart / reconnect your MCP host and run any OloLand command.

Read the full file on GitHub · 85 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. 12d ago Changed · +1 lines · +7 tokens per session 101377599739
  2. 1mo ago First seen · 84 lines · 48 tokens per session scan A 2de73baa8421

Subscribe to this mod's changes

setup is a skill published in the GitHub repository ololand-ai/ololand-plugins (0 stars, last pushed 3d ago), licensed Apache-2.0. It adds 55 tokens to every session and 922 once invoked, about $0.0002 per session on Opus 5.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-09-03.