Skip to content

Broken link sweep

Checks every link on your docs or site each week and proposes fixes for the dead ones. A person confirms each fix before it goes live.

EngineeringWorks with Claude Code · Cursor+1Community example
Build your promptSee requirements

What it does

  • Checks every outbound link
  • Confirms each dead link twice
  • Finds the new address when a page moved
  • Opens one pull request with the fixes

Your approval boundaries

Creates drafts

These actions always wait for your yes:

  • Merging the fixes

You decide what happens next.

More about this workflow

This setup is for developers and small engineering teams who want fewer chores. It takes a repeat chore off your plate and hands back something you can check quickly.

First, it checks every outbound link. Next, it confirms each dead link twice. Then it finds the new address when a page moved. Finally, it opens one pull request with the fixes. It works with your git host, web fetch and CI, each on its own login with limited access.

You get the prep work done and waiting for you. The agent stops and asks for your yes before merging the fixes, and says plainly if a step cannot be undone.

“All 7 were checked by hand and confirmed dead.”
its-imad n8n docs on GitHub · Oct 5, 2026
Before you startGit host · Web fetch accessScoped permissionsClaude Code or Cursor
Explore required tools and model recommendations

Tools and access

  • GitHub

    Handles the git host and ci part of this job. Grant a fine-grained token, read code and write comments.

    API required: Yes. Needs a GitHub App or a fine-grained personal access token scoped to the repos it needs.

    Sign up: Create a GitHub account

  • Web fetch

    Handles the web fetch part of this job. Grant public pages, no logged-in sessions.

    API required: No. Built into most agent harnesses. It reads public pages with no login.

    No sign-up needed

Official links only. Not sponsored, no affiliate links.

Model recommendations

Best pick

Claude Opus 5.5

Its maker points to it for long running coding work.

$4 per million input tokens, $20 per million output tokens.

Anthropic docs as of October 11, 2026

Cheaper backup

Claude Sonnet 5.5

Half the price per token and still strong for reviews and docs.

$2 per million input tokens, $10 per million output tokens.

Anthropic docs as of October 11, 2026

Our own picks. Not sponsored, no affiliate links.

Build your prompt

Add your details, then copy the prompt into your tool.

1Your details

Fill these in and the prompt updates as you type.

2Your prompt

3 of 3 still empty
Fill these in before you run it: [YOUR REPO AND DOCS FOLDER] [LINKS TO SKIP] [WHO REVIEWS THE FIXES] You are the Broken link sweep agent. Checks every link on your docs or site each week and proposes fixes for the dead ones. A person confirms each fix before it goes live. Use only the details filled in above. If any [BRACKETED] item is still blank or unclear, stop and ask for it first. Do not guess. What you do on your own: - Checks every outbound link - Confirms each dead link twice - Finds the new address when a page moved - Opens one pull request with the fixes What you must never do without a yes from a person: - Merging the fixes Rules: - Before any step on the list above, stop and ask. Say in plain words what you want to do, who it affects, and whether it can be undone. - If something cannot be undone, say so first, in one short line. - Write drafts, not final actions. A person sends, pays, posts, or deletes. - Keep a short log of every action you took and every source you read. - If you are unsure, ask instead of guessing.
View run instructionsPaste into: Claude Code, Cursor, n8n

Your answers stay in this browser only.

Run your workflow

Connect your tools with only the access this setup needs, then follow these steps.

Steps

Do these in order. Test on old data before it touches live work.

  1. 1Connect GitHub with its own login, not yours. Grant a fine-grained token, read code and write comments.
  2. 2Set up Web fetch. Keep it to public pages, no logged-in sessions.
  3. 3Paste the prompt where your harness takes instructions. See the note under the Copy button.
  4. 4Do a dry run on old or test data first. Check every draft and every stop point by hand before you let it near live work.
  5. 5Read its log after the first real run. Only widen access once a week of runs looks clean.

Safeguards and trust score

The score describes this example setup’s access, approval boundaries, ability to undo changes, and scope.

Access24 / 30

Writes drafts and notes inside your tools, nothing leaves on its own.

Human approval27 / 30

Waits for a yes on: merging the fixes.

Undo and logs14 / 20

Proposes changes to live records, so the setup needs a change log and a way back.

Scope16 / 20

Runs on its own login across 3 tools. Fewer connections means a smaller blast radius.

How to raise it

  • Human approval: Add a second named stop next to "merging the fixes", so every step that leaves your hands waits for a yes, and have the confirm say plainly what cannot be undone +3
  • Undo and logs: Stop it from editing live records. Have it write the change as a proposal you apply, and keep a log of every change with a way to roll it back +3
  • Scope: Cut it down from 3 connected tools to the 2 it needs most, each with its own limited login instead of your full account +2

Do all of these to reach 89, up from 81.

Want help getting there? Get an AI Trust Audit from Pixeldesigns

Reviewed by Trustcase (example setup). How scoring works

Embed badge

Show this trust score on your site or README. It links back here.

Trustcase trust score badge
Markdown
[![Trustcase trust score for Broken link sweep](https://trustcase.dev/badge/broken-link-sweep.svg)](https://trustcase.dev/use-cases/broken-link-sweep)
HTML
<a href="https://trustcase.dev/use-cases/broken-link-sweep"><img src="https://trustcase.dev/badge/broken-link-sweep.svg" alt="Trustcase trust score for Broken link sweep" height="20"></a>

More engineering workflows

  • Weekly codebase review report

    Once a week it reviews the whole repo, focusing on what changed since last time. It tracks each finding as new, still open or fixed, and nothing blocks on it.

  • Small fix pull requests

    Runs on a schedule and opens one small pull request per fix, each proven by a test that failed before and passes after. Changes collect on a dev branch and you decide when they ship.

  • New issue intake sorter

    Reads each new issue on your repo and sorts it as ready to work, needs more info, or too big. You get a clean queue and reporters get asked for missing details.

  • Merged changes digest

    Reads every pull request merged since the last run and writes a short digest of what changed. Each change is sorted by who it matters to and how big it is.