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 oaustegard/claude-skills --skill updating-knowledgegit clone --depth 1 https://github.com/oaustegard/claude-skillsWrote 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/oaustegard/claude-skills/updating-knowledge)<a href="https://agentmods.dev/skills/oaustegard/claude-skills/updating-knowledge"><img src="https://agentmods.dev/badge/skills/oaustegard/claude-skills/updating-knowledge/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/oaustegard/claude-skills/updating-knowledge"><img src="https://agentmods.dev/badge/skills/oaustegard/claude-skills/updating-knowledge.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.00085 | $0.01027 |
| Opus 5 | $0.00043 | $0.00513 |
| Sonnet 5 | $0.00017 | $0.00205 |
| Haiku 4.5 | $0.00009 | $0.00103 |
Grade A, and why
updating-knowledge 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 yesterday.
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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Updating Knowledge
Core Principles
- Systematic > ad-hoc - Follow research methodology, don't scatter searches randomly
- Cross-validate - Verify claims across multiple independent sources
- Confidence tracking - Explicitly flag single-source claims and gaps
- Concise output - Present findings efficiently, introspection in thinking blocks
Preflight Check
This skill requires web_search tool access.
Verify it's available before proceeding. If it isn't, tell the user immediately — "I need web search enabled for research tasks. Please toggle on 'Web search' in the feature menu." — and stop there rather than researching from memory alone or spending context on workarounds.
Trigger Disambiguation
Avoid triggering on generic action verbs like "update" (which could mean file/code changes instead) — trigger on the explicit knowledge-gathering requests named in the description above.
Research Workflow
1. Scope Definition (internal)
Identify in thinking block:
- What specifically needs investigation
- Current knowledge baseline
- Known gaps
- Required depth (overview vs comprehensive)
2. Source Gathering (2-10 tool calls)
Source priority:
- Official documentation, project repos, company announcements
- Academic papers, technical blogs with clear expertise
- Community discussions (for ecosystem context only)
Tool selection:
web_search- Find authoritative sourcesweb_fetch- Extract complete content from any URL (no prior search required)- Internal tools (GitHub, Drive, etc.) - Company/personal context
- Multiple tool types as needed
Gather 3-5 diverse sources minimum for cross-validation.
3. Synthesis (internal)
In thinking block:
- Cross-validate major claims across sources
- Note contradictions explicitly
- Track publication dates
- Assess source credibility
- Identify remaining gaps
4. Output (concise)
Present findings concisely:
## [Topic]
**Key findings:**
[2-3 sentence summary with most important updates]
**Current state:**
[Concise description of what's true now]
**Changes since cutoff:**
[Only if relevant - what's different]
**Gaps:**
[Only if user needs to know - what wasn't found]
Sources: [URLs]
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday Changed · -26 lines 241894b8ff1b
- 7d ago First seen · 178 lines · 85 tokens per session scan A d5e8f98a9c63
updating-knowledge is a skill published in the GitHub repository oaustegard/claude-skills (148 stars, last pushed yesterday), licensed MIT. It adds 85 tokens to every session and 1,027 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-09-03.
Other skills, from other repositories
superdesign
Design or redesign frontend UI, presentations, and graphics on the Superdesign canvas with a choice of leading AI models. Use whenever the user wants to design a page, feature, flow, slide deck, or brand-new product; improve or reproduce existing UI; compare design results across top models; explore visual variants…
Linear
Managing Linear issues, projects, and teams. Use when working with Linear tasks, creating issues, updating status, querying projects, or managing team workflows.
chanlun-engine-skill
A Chinese-language stock-analysis skill based on Chan theory, a method for interpreting price-chart structures such as turning points and trading ranges.
youtube-summary
Summarize a YouTube video into structured notes — TL;DR, key takeaways, chapter-by-chapter breakdown, and reference links. Use when the user shares a YouTube URL (or invokes /youtube-summary ) and wants a summary, takeaways, transcript notes, or a write-up of a talk, lecture, or tutorial. Fetches the transcript and…
plangate
Use for any non-trivial task with 2+ open decisions/tradeoffs OR multiple implementation steps — instead of deliberating one question at a time in chat, write a structured plan to a file and let the user review it inline in vim with > Q: / > A: blockquote markers, then revise until agreed before touching any code.…
coinmarketcap
Expert assistant for CoinMarketCap Pro API — price quotes, listings, historical OHLCV, market metrics, Fear & Greed Index, CMC100/CMC20 indices, exchange data, DEX data, airdrops, trending, community sentiment. Covers 10+ endpoint categories across REST + MCP + x402 pay-per-call modes. Use when the user wants: current…