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 instructions/carsonroell-debug/linkrescue-mcp/agents-mdgit clone --depth 1 https://github.com/carsonroell-debug/linkrescue-mcpWrote 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/instructions/carsonroell-debug/linkrescue-mcp/agents-md)<a href="https://agentmods.dev/instructions/carsonroell-debug/linkrescue-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/carsonroell-debug/linkrescue-mcp/agents-md.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.00689 | $0.00689 |
| Opus 5 | $0.00345 | $0.00345 |
| Sonnet 5 | $0.00138 | $0.00138 |
| Haiku 4.5 | $0.00069 | $0.00069 |
Grade A, and why
linkrescue-mcp AGENTS.md 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 3d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LinkRescue MCP — Agent Instructions
What This Server Does
LinkRescue finds broken links on websites, monitors them over time, and suggests fixes. It's designed for AI agents that help users maintain healthy websites and protect affiliate revenue.
Available Tools
1. check_broken_links — Scan a site for broken links
When to use: User asks to check, scan, audit, or find broken links on a website.
Input:
url(required) — The website URL to scansitemap_url(optional) — Specific sitemap to crawlmax_depth(optional, default 3) — How deep to crawl
Output: Full scan report with broken links, status codes, page locations, link types (affiliate/external/internal), SEO impact, and revenue loss estimates.
Example prompts that should trigger this tool:
- "Check example.com for broken links"
- "Scan my site's affiliate links"
- "Audit https://myblog.com for link rot"
- "Find dead links on this URL"
2. monitor_links — Set up ongoing monitoring
When to use: User wants continuous or scheduled monitoring, not just a one-time scan.
Input:
url(required) — The website URL to monitorfrequency_hours(optional, default 24) — Check interval
Output: Monitoring ID and schedule confirmation.
Example prompts:
- "Monitor my site for broken links daily"
- "Set up weekly link checks for example.com"
- "Watch this URL for dead links"
3. get_fix_suggestions — Get remediation steps
When to use: After a scan, when the user wants to know how to fix the broken links.
Input:
broken_links_report— The full output fromcheck_broken_links, or just thebroken_linksarray
Output: Prioritized list of fix actions with explanations and code snippets.
Example prompts:
- "How do I fix these broken links?"
- "Give me fix suggestions for this scan"
- "What should I do about these dead links?"
Recommended workflow: Run check_broken_links first, then pass the result to get_fix_suggestions.
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.
- 3d ago First seen · 84 lines · 689 tokens per session scan A d3c63624de79
linkrescue-mcp AGENTS.md is an instructions file published in the GitHub repository carsonroell-debug/linkrescue-mcp (0 stars, last pushed 4mo ago), licensed MIT. It adds 689 tokens to every session, about $0.0034 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.