content-links

A read-only checker for image paths, links, anchors, and alternative text in content files.

In plain words
What is it for?
Use it to scan a set of content files, verify local paths, and optionally check live or external links for HTTP errors.
Why use it?
It helps find missing images, broken internal links, invalid anchors, and weak image descriptions before content is published.

Agent

Install

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.

agentmods
npx agentmods add agents/greglas75/zuvo/content-links
Clone the repo
git clone --depth 1 https://github.com/greglas75/zuvo
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,648 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00024 $0.01648
Opus 5 $0.00012 $0.00824
Sonnet 5 $0.00005 $0.00330
Haiku 4.5 $0.00002 $0.00165

Measured 2d ago against content hash 87e85e343c3d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

content-links 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 2d 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.

skills/content-audit/agents/content-links.md · 216 lines

How it starts

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

Model: Sonnet | Type: Explore (read-only)

Check image paths and link targets in content files. Source-level checks verify file existence via Glob. Live checks (when --live-url is provided) verify HTTP responses.

Mandatory File Loading

Read before starting:

  1. ../../../shared/includes/codesift-setup.md -- CodeSift discovery
  2. ../../../shared/includes/content-check-registry.md -- canonical check slugs
  3. ../../../shared/includes/live-probe-protocol.md -- rate limiting and consent

Print the checklist:

CORE FILES LOADED:
  1. codesift-setup.md          -- [READ | MISSING -> STOP]
  2. content-check-registry.md  -- [READ | MISSING -> STOP]
  3. live-probe-protocol.md     -- [READ | MISSING -> STOP]

Input (from dispatcher)

  • file_manifest: string[] (content files to scan)
  • detected_stack: string
  • codesift_repo: string | null
  • live_url: string | null (base URL for live checks)
  • check_external: boolean (enable external link checking without full live mode)

CC5 — Image Integrity

Check: img-path-broken

  1. Extract all image references from content files:
    • Markdown: ![alt](path) syntax
    • HTML: <img src="path"> in content files
  2. For each path, resolve relative to the file's directory
  3. Check if the resolved path exists via Glob or ls
  4. FAIL for paths that do not resolve to an existing file

Framework-relative paths (@/, ~/, ../assets/) — see img-path-relative-risk.

Check: img-path-relative-risk

Flag image paths using framework-specific conventions:

  • @/ (Vite/Webpack alias)
  • ~/ (Nuxt alias)
  • ../assets/ (content collection relative)

These paths resolve at build time, not in source. Report as img-path-relative-risk (advisory), not hard FAIL.

Check: img-alt-quality

For each image with alt text, check for non-descriptive values:

  • Alt text equals the filename (e.g., alt="IMG_2045.jpg")
  • Alt text is a single word (e.g., alt="image", alt="photo", alt="img")
  • Alt text is empty string with no decorative signal (e.g., alt="" without role="presentation" or aria-hidden="true")

Read the full file on GitHub · 216 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. 2d ago First seen · 216 lines · 24 tokens per session scan A 87e85e343c3d

Subscribe to this mod's changes

content-links is an agent published in the GitHub repository greglas75/zuvo (6 stars, last pushed 2d ago), licensed MIT. It adds 24 tokens to every session and 1,648 once invoked, about $0.0001 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.

Related

Other agents, from other repositories