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 reluctantfuturist/loyal-wingman --skill validate-linksgit clone --depth 1 https://github.com/reluctantfuturist/loyal-wingmanWrote 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/reluctantfuturist/loyal-wingman/validate-links)<a href="https://agentmods.dev/skills/reluctantfuturist/loyal-wingman/validate-links"><img src="https://agentmods.dev/badge/skills/reluctantfuturist/loyal-wingman/validate-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.
<a href="https://agentmods.dev/skills/reluctantfuturist/loyal-wingman/validate-links"><img src="https://agentmods.dev/badge/skills/reluctantfuturist/loyal-wingman/validate-links.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00041 | $0.00801 |
| Opus 5 | $0.00020 | $0.00400 |
| Sonnet 5 | $0.00008 | $0.00160 |
| Haiku 4.5 | $0.00004 | $0.00080 |
Grade A, and why
validate-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 11d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validate Links
The Iron Law
LINKS MUST BE BIDIRECTIONAL. If A links to B, B must reference A.
When to Use
- After creating new entity (called by world-bible)
- After major vault reorganization
- When checking vault health
- When user asks about link integrity
The Process
Phase 1: Identify Scope
Determine what to validate:
- Single file: Check all links in/out of one file
- Folder: Check all files in a folder
- Full vault: Check entire
02_World/structure
Phase 2: Extract Links
For each file in scope:
Outgoing links:
- All
[[wikilinks]]in content - All links in frontmatter (related_characters, etc.)
Incoming links:
- All files that link TO this file
- Search vault for
[[Filename]]
Phase 3: Check Link Resolution
For each outgoing link:
- Does target file exist?
- Is filename spelled correctly?
- Is path correct?
Mark as:
- ✓ Valid (resolves to file)
- ✗ Broken (no target file)
- ⚠ Possible typo (similar file exists)
Phase 4: Check Bidirectionality
For each relationship:
- If A links to B, does B reference A?
- Reference can be wikilink OR text mention in appropriate section
Mark as:
- ✓ Bidirectional
- ⚠ One-way (needs backlink)
Phase 5: Identify Orphans
Find files with:
- No incoming links (nothing references them)
- No outgoing links (reference nothing)
Orphan types:
- Isolated: No links in either direction
- Dead-end: Has incoming but no outgoing
- Unreferenced: Has outgoing but no incoming
Phase 6: Report Findings
## Link Validation: [Scope]
### Broken Links
- [File]: [[Missing Target]] ✗
### Missing Backlinks
- [File A] links to [File B]
But [File B] doesn't reference [File A]
→ Add to [section] in [File B]
### Orphaned Files
- [File]: No incoming links (unreferenced)
### Summary
- Files checked: X
- Valid links: Y
- Broken links: Z
- Missing backlinks: N
- Orphaned files: M
Phase 7: Fix Issues (with approval)
For each issue, offer:
- Broken link: Delete link or create target file?
- Missing backlink: Add backlink to [section]?
- Orphan: Delete or find appropriate link?
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.
- 11d ago First seen · 133 lines · 41 tokens per session scan A 0011b02ea4d5
validate-links is a skill published in the GitHub repository reluctantfuturist/loyal-wingman (7 stars, last pushed 8mo ago), licensed MIT. It adds 41 tokens to every session and 801 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…