Skip to main content
Four steps and your agent can check a placement, read its dated evidence and keep watching it. The steps are the same wherever you start: this page, the npm README, or the landing page.
Hosted monitoring needs a pilot invitation; the local check in step 4 needs no account. agentlinkops 0.5.0 is on npm and the skill discovery index is live on both domains, so both install lines below work as written. Availability tracks releases.

​
1. Install the skill

This detects the agent clients on your machine (Claude Code, Codex, Cursor, Gemini CLI, Hermes), installs the AgentLinkOps skill pack at each client’s skills path and writes the MCP entry for the view that client should use. It stores no credential and prints exactly what it changed; agentlinkops agent status shows it again later. If you use the skills CLI, npx -y skills add https://agentlinkops.com installs the same skills; then add https://app.agentlinkops.com/mcp as a remote HTTP MCP server in your client by hand (MCP setup). The skill is a short door. The first time your agent uses AgentLinkOps in a session it reads the full agent reference (also agentlinkops skill), which carries the rules, the observe-act-observe loop and the common mistakes.

​
2. Sign in when your agent asks

Your client opens the AgentLinkOps sign-in in the browser. Pick the account, the workspace and the scopes for the task. The grant stays in the client’s credential store; nothing is pasted into a chat. A terminal or HTTP client uses a scoped API key instead (CLI, HTTP).

​
3. Verify

Ask your agent:
A project list means the connection works. On the CLI, agentlinkops doctor reports the same in one line per check. If nothing comes back, MCP connection help covers the three failure shapes.

​
4. Check a placement

Ask your agent, with real URLs:
The placement workflow creates a monitored watch and requests a check. A queued job is still waiting for a result; your agent waits for the completed observation before reporting what the page contains. No account yet? The same verifier runs locally:
Check one backlink locally explains the result and how to keep it.

​
Read the result

  • present: the completed read found a matching link.
  • absent: that read found no match. Check the URLs and scope before drawing a conclusion.
  • unknown: the verifier could not decide. Read the reason and inspect the page when needed.
One absent observation does not establish confirmed loss. Evidence states explains how repeated observations affect that conclusion. Keep the watch active to monitor changes, or pause it with update_link_watch. Pausing preserves its history.