check-third-party-docs

check-third-party-docs is a skill for Claude Code from jtsternberg/claude-plugins. It costs 66 tokens per session (1,261 once invoked), scanned A, original, MIT.

A maintenance tool for cached documentation about outside software used by this repository's skills.

In plain words
What is it for?
Refreshing stored third-party docs, showing changes, and suggesting updates to the skills and documentation that depend on them.
Why use it?
It helps prevent local instructions from becoming outdated when the upstream tools change.

Skill for Claude Code

Written for Claude Code: when-to-use in frontmatter. Also seen: reads .claude/ paths.

Part of the jtsternberg plugin — 6 skills, 31 plugins shipped together

Good fit Refreshing stored third-party docs, showing changes, and suggesting updates to the skills and documentation that depend on them.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jtsternberg/claude-plugins/check-third-party-docs
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.

Any agent
npx skills add jtsternberg/claude-plugins --skill check-third-party-docs
Clone the repo
git clone --depth 1 https://github.com/jtsternberg/claude-plugins

Made for: Claude Code.

Or install jtsternberg, the plugin that ships this one along with the rest of its 6 skills, 31 plugins.

Wrote 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.

agentmods badge for check-third-party-docs

README.md
[![agentmods](https://agentmods.dev/badge/skills/jtsternberg/claude-plugins/check-third-party-docs.svg)](https://agentmods.dev/skills/jtsternberg/claude-plugins/check-third-party-docs)
Your own site
<a href="https://agentmods.dev/skills/jtsternberg/claude-plugins/check-third-party-docs"><img src="https://agentmods.dev/badge/skills/jtsternberg/claude-plugins/check-third-party-docs.svg" alt="Measured on agentmods" height="20"></a>
Per session 66 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,261 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00066 $0.01261
Opus 5 $0.00033 $0.00630
Sonnet 5 $0.00013 $0.00252
Haiku 4.5 $0.00007 $0.00126

Measured 7d ago against content hash 2ac364679463, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

check-third-party-docs 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 7d 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.

.claude/skills/check-third-party-docs/SKILL.md · 109 lines

How it starts

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

Check third-party docs

We vendor copies of the upstream docs for the external tools our skills wrap (e.g. the MacWhisper mw CLI behind work-with-media:macwhisper-cli). This skill re-fetches those upstream docs, shows what changed since the last cache, and proposes edits to the local skills/docs that the change affects — so our wrapper docs never silently drift behind the tool.

Cached docs live in docs/third-party/cached/*.md. Each is self-describing — its frontmatter names the upstream source URL, when it was last_updated, and the local skills/docs it informs (related). There is no separate manifest; the cache dir is the registry. Run everything from the repo root.

Frontmatter contract (every cached doc)

---
source: <upstream URL>                     # what to re-fetch
cached_from: research-tools:fetch-docs --md # how it was fetched (for a matching refetch)
last_updated: <YYYY-MM-DD>                  # bumped on every refresh
related:                                    # what this doc informs, so review is mechanical
  - work-with-media:macwhisper-cli          # a skill (plugin:skill) …
  # - plugins/<plugin>/README.md            # … or an explicit repo-relative doc path
---

Refresh workflow

Do this for each cached doc (all of them, or the one the user named). The order matters — overwrite the cached file before diffing so git diff naturally shows the committed (old upstream) version against the working-tree (new) version.

  1. Read the cached doc's frontmatter to get its source, cached_from, and related.

  2. Re-fetch the source with the research-tools:fetch-docs skill, matching cached_from (use --md when the cached copy is markdown). It writes the fresh copy to a /tmp/fetch-docs-*.md path and returns that path. Pass --ttl=0 to force a live refetch and bypass fetch-docs' 24h cache.

  3. Overwrite the cached file — replace its body with the fresh /tmp fetch and refresh the frontmatter: keep source/cached_from/related, bump last_updated to today (date +%F). Store the fetch body exactly as fetched — never hand-clean it — so the next refresh diffs against the same pipeline output instead of fighting your edits. Example, run from the repo root:

Read the full file on GitHub · 109 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. 7d ago First seen · 109 lines · 66 tokens per session scan A 2ac364679463

Subscribe to this mod's changes

check-third-party-docs is a skill published in the GitHub repository jtsternberg/claude-plugins (5 stars, last pushed 2d ago), licensed MIT. It adds 66 tokens to every session and 1,261 once invoked, about $0.0003 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 skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens