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.
/plugin marketplace add OpenLinker-ai/openlinker-plugin/plugin install openlinkerWrote 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/openlinker-ai/openlinker-plugin/setup-openlinker-cli)<a href="https://agentmods.dev/skills/openlinker-ai/openlinker-plugin/setup-openlinker-cli"><img src="https://agentmods.dev/badge/skills/openlinker-ai/openlinker-plugin/setup-openlinker-cli/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.
<a href="https://agentmods.dev/skills/openlinker-ai/openlinker-plugin/setup-openlinker-cli"><img src="https://agentmods.dev/badge/skills/openlinker-ai/openlinker-plugin/setup-openlinker-cli.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00059 | $0.00449 |
| Opus 5.5 | $0.00024 | $0.00180 |
| Sonnet 5.5 | $0.00012 | $0.00090 |
| Haiku 4.5 | $0.00006 | $0.00045 |
Grade A, and why
setup-openlinker-cli 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 1mo 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.
What it actually says
Set Up the OpenLinker CLI
Use the Plugin's deterministic resolver and installer. Do not implement an
alternate downloader, install a floating latest, or modify a project file.
Verify First
Resolve the package root from PLUGIN_ROOT, then CLAUDE_PLUGIN_ROOT, or the
installed Skill location. Run scripts/resolve-openlinker-cli from that root.
It checks, in order, OPENLINKER_CLI_BIN, PATH, and the Plugin data directory,
then validates context JSON, surface version, and requested capabilities.
If a compatible CLI is found, report its path, version, and capabilities and
stop. Never print OPENLINKER_USER_TOKEN or other environment values.
Install Only with Explicit Intent
Running this Skill or /openlinker-setup is explicit installation intent.
Before invoking the installer, show:
- the pinned CLI version from
cli-lock.json; - the GitHub release origin;
- the platform/architecture;
- the Plugin data destination.
Then run scripts/install-openlinker-cli from that root on POSIX systems or
scripts/install-openlinker-cli.ps1 on Windows. The installer must select an exact
entry from cli-lock.json, download the archive and adjacent checksum, verify
SHA-256, reject symlink destinations, extract only the expected executable, and
install atomically into Plugin data. A failed check must leave the previous CLI
untouched.
Honor standard HTTP/HTTPS proxy configuration. Do not disable TLS validation, follow a private-network redirect, use credentials from prompts, or fall back to an unverified binary.
After installation, run the resolver again and report only non-sensitive version and capability information. If installation cannot complete, provide the exact failure and the manual fixed-release installation option; do not silently switch the Plugin to remote MCP.
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.
- 1mo ago Changed · -2 tokens per session fdf85cb428be
- 1mo ago First seen · 46 lines · 61 tokens per session scan A 68ef8771c31b
setup-openlinker-cli is a skill published in the GitHub repository OpenLinker-ai/openlinker-plugin (0 stars, last pushed 13d ago), licensed Apache-2.0. It adds 59 tokens to every session and 449 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-08-31.
Other skills, from other repositories
plugin-publish
A release guide for publishing Zhin.js plugins to npm, the JavaScript package registry, and to the Zhin plugin marketplace. It covers package metadata, versioning, release checks, and submission requirements.
plugin-develop
A development guide for adding features to Zhin.js plugins, such as chat commands, AI tools, middleware, scheduled tasks, and console pages. Zhin.js is the plugin system it targets.
commands-create-slash-command
Create or edit reusable Agent Zero /commands with YAML and text/Python templates.
deepseek-harness
Use when building AI agent applications with a plugin-based architecture — Web UI, CLI, Python SDK, Cordis plugin system, multi-model orchestration. DeepSeek Harness (dsh): open-source agent harness by DeepSeek AI where everything is a plugin, powered by Cordis for spatiotemporal composability.
dbt-strategy
Use when creating or modifying dimensional dbt models in warehouse-backed analytics projects. Covers a four-layer warehouse architecture (sources/staging/core/marts), naming conventions, no-alias SQL rule, surrogate-key and missing-record patterns, incremental strategies, deduplication, and common project macros. Use…
data-quality
Use when adding or reviewing data quality tests for dbt models in warehouse-backed analytics projects. Covers dbt generic tests, singular tests (assert.sql), accepted-values macros, dbtutils patterns, cross-system consistency tests, and warehouse-oriented validation. Use when writing data tests, creating assert.sql…