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 skills add richfrem/agent-plugins-skills --skill link-checker-agentgit clone --depth 1 https://github.com/richfrem/agent-plugins-skillsWrote 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/skills/richfrem/agent-plugins-skills/link-checker-agent)<a href="https://agentmods.dev/skills/richfrem/agent-plugins-skills/link-checker-agent"><img src="https://agentmods.dev/badge/skills/richfrem/agent-plugins-skills/link-checker-agent.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00046 | $0.01526 |
| Opus 5 | $0.00023 | $0.00763 |
| Sonnet 5 | $0.00009 | $0.00305 |
| Haiku 4.5 | $0.00005 | $0.00153 |
Grade A, and why
link-checker-agent 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 4d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Identity: The Link Checker 🔗
You are the Quality Assurance Operator. Your goal is to ensure documentation hygiene by identifying and resolving broken references. You follow a strict 5-phase pipeline: Inventory → Extract → Audit → Fix → Report.
🛠️ The 5-Step Pipeline
The plugin provides a numbered suite of scripts that must be run in order:
| Step | Script | Role |
|---|---|---|
| 1 | 01_build_file_inventory.py |
The Mapper — indexes all valid filenames in the repo |
| 2 | 02_extract_link_references.py |
The Extractor — finds all link/path strings (with line numbers) |
| 3 | 03_audit_broken_links.py |
The Auditor — cross-refs Step 2 against Step 1 to identify gaps |
| 4 | 04_autofix_unique_links.py |
The Fixer — auto-corrects unambiguous matches; writes remaining_broken_links.json |
| 5 | 05_report_unfixable_links.py |
The Reporter — generates a structured review of remaining issues |
📂 Execution Protocol
Script path note: All scripts are at
scripts/relative to the skill root (symlinked from the plugin's canonicalscripts/directory). Always run from the repository root you want to scan — not from inside the plugin folder.
Quick Reference: Full Pipeline (one-liner)
python ./scripts/01_build_file_inventory.py && \
python ./scripts/02_extract_link_references.py && \
python ./scripts/03_audit_broken_links.py && \
python ./scripts/04_autofix_unique_links.py --dry-run && \
python ./scripts/04_autofix_unique_links.py --backup && \
python ./scripts/05_report_unfixable_links.py
1. Initialization (Mapping & Extraction)
Run the first two steps to build the knowledge base.
python ./scripts/01_build_file_inventory.py
python ./scripts/02_extract_link_references.py
2. Auditing
Identify what is broken. This produces broken_links.log and broken_links.json.
python ./scripts/03_audit_broken_links.py
3. Automated Repair
Always verify the git working tree is clean before this step (git status), so that git restore . is available as a safe rollback if the fixer introduces any unexpected changes.
What ships with it
25 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- acceptance-criteria.md 2.3 KB
- assets/diagrams/link-checker-workflow.mmd 53 B
- assets/diagrams/logic.mmd 37 B
- assets/diagrams/workflow.mmd 40 B
- evals/evals.json 707 B
- evals/results.tsv 301 B
- fallback-tree.md 2.0 KB
- references/acceptance-criteria.md 42 B
- references/best-practices.md 37 B
- references/docs_index.md 33 B
- references/fallback-tree.md 36 B
- references/link_checker_workflow.mmd 45 B
- references/link_checker_workflow.png 45 B
- references/link-checker-standards.md 45 B
- references/link-checker-workflow.mmd 45 B
- references/logic.mmd 29 B
- references/specification.md 36 B
- references/unpacking.mmd 33 B
- references/workflow.mmd 32 B
- requirements.txt 22 B
- scripts/01_build_file_inventory.py 43 B runs code
- scripts/02_extract_link_references.py 46 B runs code
- scripts/03_audit_broken_links.py 41 B runs code
- scripts/04_autofix_unique_links.py 43 B runs code
- scripts/05_report_unfixable_links.py 45 B runs code
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.
- 4d ago First seen · 131 lines · 46 tokens per session scan A b638c99b3e07
link-checker-agent is a skill published in the GitHub repository richfrem/agent-plugins-skills (6 stars, last pushed yesterday), licensed MIT. It adds 46 tokens to every session and 1,526 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
test-verification
Requires behavioral, failure-path, and durable-seam evidence for tests and review. Use when writing tests, reviewing test coverage, assessing behavioral test quality, or accepting high-risk behavior on test evidence.
test-writing
Write comprehensive tests for code including unit tests, integration tests, and end-to-end tests. Use this to ensure code quality, catch bugs, and validate functionality.
fortify
Testing infrastructure, coverage, and verified test quality for any project. Detects stack, installs testing ecosystem, audits untested critical paths, writes thorough tests weighted toward error paths, runs them, verifies via mutation testing. Use when user says '/fortify', 'add tests', 'set up testing', 'I need…
tdd-xfail
Use when fixing a bug through strict xfail reproduction and needing proof that the test fails for the intended reason.
a11y-testing
Use this skill when the user asks about accessibility testing, axe-core, jest-axe, "@testing-library", "@axe-core/playwright", "Playwright accessibility testing", "WAVE", "Lighthouse accessibility", "automated a11y tests", "accessibility CI/CD", "eslint-plugin-jsx-a11y", "a11y linting", "axe DevTools", setting up…
pytest-optimizer
Use when a pytest suite or its fixtures are slow and need measured, safety-gated optimization across the full pipeline.