fixing-broken-links

fixing-broken-links is a skill for Claude Code from spencerpauly/awesome-cursor-skills. It costs 34 tokens per session (608 once invoked), scanned A, original, CC0-1.0.

A tool for finding URLs and local file links in a file or project, checking whether they work, and reporting or correcting broken links.

In plain words
What is it for?
Use it to scan Markdown, HTML, and related files, test external and local links, then fix or remove links that no longer work.
Why use it?
It prevents users from following links that lead to missing pages, unreachable resources, or incorrect local files.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is | ./docs/missing.md | MISSING | Removed link |.

Good fit Use it to scan Markdown, HTML, and related files, test external and local links, then fix or remove links that no longer work.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/spencerpauly/awesome-cursor-skills
agentmods
npx agentmods add skills/spencerpauly/awesome-cursor-skills/fixing-broken-links

Made for: Claude Code.

Wrote 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.

agentmods badge for fixing-broken-links

README.md
[![agentmods](https://agentmods.dev/badge/skills/spencerpauly/awesome-cursor-skills/fixing-broken-links/github.svg)](https://agentmods.dev/skills/spencerpauly/awesome-cursor-skills/fixing-broken-links)
Your own site
<a href="https://agentmods.dev/skills/spencerpauly/awesome-cursor-skills/fixing-broken-links"><img src="https://agentmods.dev/badge/skills/spencerpauly/awesome-cursor-skills/fixing-broken-links/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.

agentmods 80×15 button for fixing-broken-links

Your own site · 80×15
<a href="https://agentmods.dev/skills/spencerpauly/awesome-cursor-skills/fixing-broken-links"><img src="https://agentmods.dev/badge/skills/spencerpauly/awesome-cursor-skills/fixing-broken-links.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 608 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00034 $0.00608
Opus 5 $0.00017 $0.00304
Sonnet 5 $0.00007 $0.00122
Haiku 4.5 $0.00003 $0.00061

Measured 12d ago against content hash 440768b0c8dd, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

fixing-broken-links scanned grade A with 1 finding 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 12d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- Use `curl -sL -o /dev/null -w "%{http_code}" --max-time 10 "<url>"` to get the HTTP status code
Origin

Copies of this mod

1 near-identical copy found in the catalogue:

resources/fixing-broken-links/SKILL.md · 67 lines

How it starts

The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Scan a file (or set of files) for URLs, test every link, and fix any that are broken.

Workflow

1. Extract All Links

Read the target file(s) and collect every URL:

  • Markdown links: [text](url)
  • Bare URLs: https://...
  • HTML href and src attributes
  • Reference-style link definitions: [id]: url
  • Local relative paths: ./path/to/file, resources/foo/SKILL.md

2. Test Each Link

For external URLs:

  • Use curl -sL -o /dev/null -w "%{http_code}" --max-time 10 "<url>" to get the HTTP status code
  • Batch independent checks for speed (run multiple curl commands in parallel or in quick succession)
  • Classify results:
    • 200299 → OK
    • 301/302 → OK but note the redirect target
    • 403 → Might be valid (some sites block curl); try with a browser user-agent header
    • 404 → Broken
    • 429 → Rate limited; retry once after a short pause
    • 000 or timeout → Retry once; if still failing, mark as unreachable

For local file paths:

  • Check if the file exists on disk with [ -f "path" ]
  • If it's a relative path, resolve it from the file's directory

3. Fix Broken Links

For each broken link:

  1. Search the web for the correct/current URL (the resource may have moved)
  2. If found, replace the old URL with the new one
  3. If the resource no longer exists, note it and either:
    • Remove the link and leave the text
    • Comment it out with a note
    • Replace with an archived version (web.archive.org)

4. Report

Produce a summary table:

| URL | Status | Action |
|-----|--------|--------|
| https://example.com/page | 200 | OK |
| https://old.example.com/moved | 404 → 301 | Updated to https://new.example.com/page |
| ./docs/missing.md | MISSING | Removed link |

Tips

  • For large files with many links, batch curl calls to avoid slowdowns
  • Some sites (GitHub, npm) rate-limit aggressively — space out requests
  • Always re-read the file after making changes to confirm replacements didn't break formatting
  • For Markdown files, verify link syntax is preserved: [text](url) not [text]( url ) (no extra spaces)

Read the full file on GitHub · 67 lines

Changes

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.

  1. 12d ago First seen · 67 lines · 34 tokens per session scan A 440768b0c8dd

Subscribe to this mod's changes

fixing-broken-links is a skill published in the GitHub repository spencerpauly/awesome-cursor-skills (770 stars, last pushed 1mo ago), licensed CC0-1.0. It adds 34 tokens to every session and 608 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

4-phase root cause debugging: understand bugs before fixing.

NousResearch/hermes-agent · 16 tokens

langsmith-observability

LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.

davila7/claude-code-templates · 45 tokens

experimental-code-coverage-local-debugger

Runs code coverage locally via Universal Test Runner (UTR) or helper scripts, mimicking LUCI trybots. Activate when CQ tryjobs fail or underreport coverage, to test local GN/recipe repairs before uploading, or to debug hermetic crashes.

chromium/chromium · 59 tokens

adversarial-reviewer

Adversarial code review that assumes bugs exist and hunts for them. Use when asked to review code, find bugs, audit for correctness, stress-test a PR, or when someone says "tear this apart" or "what's wrong with this". Give no benefit of the doubt — every line is guilty until proven innocent.

emdash-cms/emdash · 71 tokens

cli-e2e

Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.

ComposioHQ/composio · 62 tokens

work

Deliver one maintainer-approved EmDash issue, choosing the bug-fix path for a defect and the direct implementation path for an enhancement or task.

emdash-cms/emdash · 31 tokens