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 skills add OpenLinker-ai/openlinker-plugin --skill serve-openlinker-agentgit clone --depth 1 https://github.com/OpenLinker-ai/openlinker-pluginWrote 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/serve-openlinker-agent)<a href="https://agentmods.dev/skills/openlinker-ai/openlinker-plugin/serve-openlinker-agent"><img src="https://agentmods.dev/badge/skills/openlinker-ai/openlinker-plugin/serve-openlinker-agent.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.1 | $0.00058 | $0.00822 |
| Opus 5 | $0.00029 | $0.00411 |
| Sonnet 5 | $0.00012 | $0.00164 |
| Haiku 4.5 | $0.00006 | $0.00082 |
Grade A, and why
serve-openlinker-agent 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Serve This Host as an OpenLinker Agent
Agent Mode is disabled by default. Use the local Agent-control MCP tools inside
the Plugin. For a standalone installation use openlinker agent commands.
Configure Without Secrets
Collect and save only:
- provider:
codexorclaude; - an existing OpenLinker Agent UUID;
- a minimal workspace directory;
- the public OpenLinker platform URL;
- optional state directory, model, capacity, timeout, sandbox/permission, web search and session-reuse preferences;
- optional
execution_profile: browserfor a dedicated private Browser Agent, which requires capacity 1, session reuse, and private Runtime paths; - for that Browser Agent, the local declaration
browser_interaction_policy: restricted|full. Configure it throughconfigure_agent_mode,openlinker agent configure --browser-interaction-policy, orOPENLINKER_BROWSER_INTERACTION_POLICY; - for Codex only, an optional validated OpenAI-compatible
codex_base_urlwithout credentials, a query, or a fragment.
Use configure_agent_mode or openlinker agent configure. Never accept an
Agent Token, Provider API key, secret file contents, or Provider session ID in
tool arguments, prompts, config JSON, shell history, or Run metadata.
Core's Owner-only Agent setting is authoritative and is the only place to
configure the one to 32 exact HTTPS mutation origins for full. Origins are
never Plugin tool arguments or Runtime environment/config fields. Change the
Core setting only while no Browser Run, paused human-control state, or Runtime
Session is active, then configure the Runtime with the same policy name. Core
supplies the immutable generation and exact Origin list per Run. A generation
change fences existing Attachments and never silently falls back to
restricted.
The operator supplies OPENLINKER_AGENT_TOKEN or
OPENLINKER_AGENT_TOKEN_FILE outside model context. Provider authentication
uses the provider's supported local login state or CODEX_API_KEY /
ANTHROPIC_API_KEY and their optional _FILE alternatives. Direct and file
forms are mutually exclusive.
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.
- 8d ago First seen · 78 lines · 58 tokens per session scan A 8ae7357c7354
serve-openlinker-agent is a skill published in the GitHub repository OpenLinker-ai/openlinker-plugin (0 stars, last pushed yesterday), licensed Apache-2.0. It adds 58 tokens to every session and 822 once invoked, about $0.0003 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-31.
Other skills, from other repositories
plugin-init
A project starter for creating Zhin.js plugins, which are installable packages that extend the Zhin.js bot framework. It sets up the required files, folders, package metadata, entry point, and documentation.
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 update Agent Zero slash commands for the built-in Commands plugin. Use when the user asks to add, edit, duplicate, or refine a reusable /command backed by YAML config plus text/python content files.
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.
research-extraction
Deep extraction of research corpora into structured knowledge documents using a Workflow-driven subagent/reviewer pattern. Use when you have raw source documents (theses, papers, reports) and need structured extraction across multiple axes (architecture, messages, algorithms, forms, etc.) with confidence-annotated…