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.
npx agentmods add skills/ololand-ai/ololand-plugins/setupnpx skills add ololand-ai/ololand-plugins --skill setupgit clone --depth 1 https://github.com/ololand-ai/ololand-pluginsWrote 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.
[](https://agentmods.dev/skills/ololand-ai/ololand-plugins/setup)<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="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00048 | $0.00872 |
| Opus 5 | $0.00024 | $0.00436 |
| Sonnet 5 | $0.00010 | $0.00174 |
| Haiku 4.5 | $0.00005 | $0.00087 |
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 today.
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.
How it starts
The opening of the file, as written. The whole thing — 84 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)
- Enable / connect the ololand MCP server in your client's connectors or plugin settings.
- Claude opens the OloLand sign-in page at https://api.ololand.ai — sign in with email or Google and click Approve.
- 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:
- 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_... - Run the setup script — it adds the OloLand MCP server to your
.mcp.json, preserving any servers already there:
The config references"${CLAUDE_PLUGIN_ROOT}/scripts/setup_headless.sh"${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-keywrites the literal key for ephemeral CI that can't set an env var (gitignore that config). - Restart / reconnect your MCP host and run any OloLand command.
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.
- today First seen · 84 lines · 48 tokens per session scan A 2de73baa8421
setup is a skill published in the GitHub repository ololand-ai/ololand-plugins (0 stars, last pushed 6d ago), licensed Apache-2.0. It adds 48 tokens to every session and 872 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…