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.
git 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/commands/openlinker-ai/openlinker-plugin/openlinker)<a href="https://agentmods.dev/commands/openlinker-ai/openlinker-plugin/openlinker"><img src="https://agentmods.dev/badge/commands/openlinker-ai/openlinker-plugin/openlinker/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/commands/openlinker-ai/openlinker-plugin/openlinker"><img src="https://agentmods.dev/badge/commands/openlinker-ai/openlinker-plugin/openlinker.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.00012 | $0.00181 |
| Opus 5.5 | $0.00005 | $0.00072 |
| Sonnet 5.5 | $0.00002 | $0.00036 |
| Haiku 4.5 | $0.00001 | $0.00018 |
Grade A, and why
openlinker 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
Route the user's request to the bundled OpenLinker skills:
- Use
find-and-run-agentfor discovery, task recommendations, Agent details, authorized execution, progress, results, and artifacts. - Use
inspect-openlinker-runwhen the request starts from an existing Run ID, including diagnosis or explicit cancellation. - Use
serve-openlinker-agentwhen the user wants Claude Code to become a callable OpenLinker Agent or asks about Agent Mode/session reuse. - Use
setup-openlinker-clionly when the user asks to install/repair the CLI or a required CLI capability is missing.
Use the bundled local MCP tools. Do not use Hosted MCP or direct Core HTTP as a fallback.
User request: $ARGUMENTS
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 First seen · 20 lines · 12 tokens per session scan A 70519618adfd
openlinker is a command published in the GitHub repository OpenLinker-ai/openlinker-plugin (0 stars, last pushed 13d ago), licensed Apache-2.0. It adds 12 tokens to every session and 181 once invoked, about $0.0000 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 commands, from other repositories
dbt-model-review
Build a new analytics feature or dbt model guided by business requirements and data exploration.
security-audit
Audit agent configuration files for security vulnerabilities and misconfigurations. Classifies findings as P0 or P1.
ci-readout
Generate a comprehensive summary of recent CI runs and failing jobs.
quality-check
Execute a comprehensive quality gate check (lint, test, build, format) before allowing code to merge.
bug-check
Run automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.
quality-gate
Run formatter, linter, and type checks for a file or directory. Report remediation steps.