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 xh/hoist-core --skill xh-update-doc-linksgit clone --depth 1 https://github.com/xh/hoist-coreWrote 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/xh/hoist-core/xh-update-doc-links)<a href="https://agentmods.dev/skills/xh/hoist-core/xh-update-doc-links"><img src="https://agentmods.dev/badge/skills/xh/hoist-core/xh-update-doc-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/xh/hoist-core/xh-update-doc-links"><img src="https://agentmods.dev/badge/skills/xh/hoist-core/xh-update-doc-links.svg" alt="Reviewed on agentmods" width="80" 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.00077 | $0.01681 |
| Opus 5 | $0.00039 | $0.00840 |
| Sonnet 5 | $0.00015 | $0.00336 |
| Haiku 4.5 | $0.00008 | $0.00168 |
Grade A, and why
xh-update-doc-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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
xh-update-doc-links — Documentation Consistency Check
Pre-commit skill to ensure documentation index files, the MCP document registry, inter-doc links, and cross-references stay consistent after editing feature-area docs.
Step 1: Discover Documentation Files
Build a complete inventory of documentation files on disk.
- Use
Globto find all files matchingdocs/*.md(feature-area docs). - Use
Globto find all files matchingdocs/upgrade-notes/*.md. - Exclude
docs/planning/from the doc inventory — those are meta/planning files, not feature-area documentation. - Run
git diff --name-onlyandgit status --porcelainto identify which docs were recently changed or added. - Build a master list of all documentation files, noting which are new or recently modified.
Step 2: Read Index Files
Read the two index files and parse their current entries.
-
Read
docs/README.md— focus on the Feature Documentation section (the tables under "Core Framework", "Core Features", "Infrastructure & Operations", "Grails Platform", "Development & Builds") and the Quick Reference by Task table.- Parse each table row to extract the linked filename and description.
-
Read
docs/planning/docs-roadmap.md— parse all priority tables and the Grails Platform table.- Extract each document name, description, and status value.
- Note which entries are
Planned,Draft, orDone.
Step 3: Reconcile Indexes
Compare documentation on disk against both index files.
docs/README.md Reconciliation
For each feature-area doc on disk:
- Check if it has an entry in the appropriate
docs/README.mdtable (Core Framework, Core Features, Infrastructure & Operations, Grails Platform, or Development & Builds). - Missing entries: Add a new table row in the correct section using this format:
| [`filename.md`](./filename.md) | One-sentence description | Key, Topics, Here | - Stale entries: If an entry links to a doc that no longer exists, remove it.
- Quick Reference: Check if a new doc should have a "If you need to..." entry in the Quick Reference by Task table. Add one if the doc covers a common task.
- AGENTS.md directive: Verify that
AGENTS.mdstill contains the directive pointing todocs/README.md(the "Documentation" section). Do not re-add documentation tables to AGENTS.md.
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 · 142 lines · 77 tokens per session scan A 88c75396d899
xh-update-doc-links is a skill published in the GitHub repository xh/hoist-core (11 stars, last pushed today), licensed Apache-2.0. It adds 77 tokens to every session and 1,681 once invoked, about $0.0004 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-30.
Other skills, from other repositories
Katalon Studio Testing
Comprehensive testing patterns for Katalon Studio including codeless record-and-playback, Groovy scripted testing, custom keywords, data-driven testing, cross-browser execution, and CI/CD integration with Katalon TestOps.
weekly-fno-trade-planner
Weekly F&O trade planning skill for Indian markets. Analyzes news/macro events, identifies trending sectors and instruments, determines probable direction, suggests option strategy with entry/exit levels, and manages stop-loss and profit booking after position entry. Use when user wants a weekly trade idea, F&O…
options-strategy-advisor
Options strategy analysis for Indian F&O markets (NSE). Use when user requests options strategy recommendations, P/L analysis, Greeks calculation, risk management, or F&O strategy planning for Nifty, Bank Nifty, or stock options.
backtest-expert
Expert guidance for systematic backtesting of trading strategies on Indian markets (NSE/BSE). Use when developing strategies, testing robustness, avoiding overfitting, or validating trading ideas.
nse-vcp-screener
Screen Nifty 500 stocks for Mark Minervini's Volatility Contraction Pattern (VCP) — identifying Stage 2 uptrends with tightening price ranges and declining volume before potential breakouts. Use this skill when the user requests VCP screening, Minervini-style setups, Stage 2 breakout candidates, or volatility…
tbank-travel
A travel booking toolset connected to T-Bank for trains and flights, plus search for hotels and marketplace offers. Train and flight tickets can be taken through payment and train tickets can be refunded; hotels and marketplace items are search-only.