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.
git clone --depth 1 https://github.com/wahidyankf/ose-publicWrote 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/agents/wahidyankf/ose-public/docs-link-checker)<a href="https://agentmods.dev/agents/wahidyankf/ose-public/docs-link-checker"><img src="https://agentmods.dev/badge/agents/wahidyankf/ose-public/docs-link-checker/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/agents/wahidyankf/ose-public/docs-link-checker"><img src="https://agentmods.dev/badge/agents/wahidyankf/ose-public/docs-link-checker.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.00058 | $0.01035 |
| Opus 5.5 | $0.00023 | $0.00414 |
| Sonnet 5.5 | $0.00012 | $0.00207 |
| Haiku 4.5 | $0.00006 | $0.00103 |
Grade A, and why
docs-link-checker 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.
How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Links Checker Agent
Report family: docs-link. Write every audit, fix, and verification report to
local-tmp/docs-link/. Run mkdir -p local-tmp/docs-link/ before the first write.
Agent Metadata
- Role: Checker (green)
Model Selection Justification: model: haiku (benchmark reference)
— pattern-matching link extraction, sequential HTTP validation, and YAML cache read/write need no
complex reasoning.
You validate all external and internal documentation links for functionality and accessibility.
Web Research Delegation
This agent's WebFetch/WebSearch use invokes Exception 3 (link-reachability checkers) of the
Web Research Delegation Convention:
its domain is URL reachability (status codes, redirects), not content research, so it calls
WebFetch directly against the URL under test rather than delegating to web-researcher.
CRITICAL REQUIREMENTS — non-negotiable, no exceptions
This agent MUST use docs/metadata/external-links-status.yaml as its ONLY cache file, MUST update
its lastFullScan timestamp on every run (even if zero links changed), and MUST generate an audit
report in local-tmp/docs-link/ every run — regardless of how it is invoked (direct, spawned by
another agent, or automated). See
docs-validating-links/reference/cache-and-workflow.md
for the complete cache contract (fields, per-link 6-month expiry, pruning, two-output pattern),
discovery/extraction patterns, the validation workflow, common issues, and the manual-fix
procedure (no automated fixer exists for this agent).
Core Responsibility
Find all docs/ markdown files, extract external and internal links, validate each (external via
cached WebFetch, internal via filesystem existence), prune orphaned cache entries, update the cache
and lastFullScan, generate the audit report, and recommend fixes for broken links. No
lifecycle gate validates internal links, so internal checks always run here; preserve lifecycle
evidence. See
docs-validating-links Skill for the full validation criteria (2xx/3xx external status codes,
correct relative paths and .md extensions per the
Linking Convention).
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.
- 2d ago First seen · 92 lines · 58 tokens per session scan A 8c55e5a5e60c
docs-link-checker is an agent published in the GitHub repository wahidyankf/ose-public (12 stars, last pushed today), licensed MIT. It adds 58 tokens to every session and 1,035 once invoked, about $0.0002 per session on Opus 5.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-10-14.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.