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 agentmods add skills/davidruzicka/mcp4openapi/auto-update-skillsnpx skills add davidruzicka/mcp4openapi --skill auto-update-skillsgit clone --depth 1 https://github.com/davidruzicka/mcp4openapiWrote 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/davidruzicka/mcp4openapi/auto-update-skills)<a href="https://agentmods.dev/skills/davidruzicka/mcp4openapi/auto-update-skills"><img src="https://agentmods.dev/badge/skills/davidruzicka/mcp4openapi/auto-update-skills.svg" alt="Measured on agentmods" 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.00000 | $0.01154 |
| Opus 5 | $0.00000 | $0.00577 |
| Sonnet 5 | $0.00000 | $0.00231 |
| Haiku 4.5 | $0.00000 | $0.00115 |
Grade A, and why
auto-update-skills 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 5d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Goal
Capture lessons from corrections by proposing a new skill that preserves existing knowledge, avoids repeated mistakes, and aligns with preferred behavior.
Also ensure existing skills are respected by extending them when they should have applied but lacked a trigger or instruction.
When to Use
- The user corrects a prior proposal, implementation, communication style or different chat pattern.
- The correction reveals a reusable rule, tool, policy, or preferred pattern.
Preconditions
- A correction or review has occurred in the current conversation.
- The correction is relevant beyond the single instance.
- A quick scan of existing skills shows no match, or a near match that can be fixed by updating the existing skill.
Definitions
- Critical issue: A correction that affects UI/UX, API, DB scheme, architecture, safety, compliance, legal risk, financial impact, or major business outcomes. Propose a new skill immediately on first occurrence.
- Trivial pattern: A small or low‑impact correction (formatting, minor naming, minor style preferences). Propose a new skill only after repetition.
Illustrative Categories (Non‑exhaustive)
Critical examples
- Programming: API changes, database schema changes, UI modifications, programming patterns.
- Engineering: Security or compliance rule (e.g., use approved validation utilities, avoid direct credential handling).
- Product: Regulatory constraints or roadmap policy that changes what can be shipped.
- Business: Pricing or contractual commitments that must be enforced.
- HR: Hiring or privacy rules that must be followed.
- Accounting: Tax or audit requirements that change reporting behavior.
- Legal: Contract clauses or jurisdiction requirements that alter guidance.
Trivial examples
- Engineering: Preferred code style or naming convention.
- Product: Template wording or formatting of a status update.
- Business: Slide layout preference.
- HR: Preferred phrasing in internal comms.
- Accounting: Report section ordering.
- Legal: Minor citation format preference.
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.
- 5d ago First seen · 105 lines · 0 tokens per session scan A 411cc2e4e731
auto-update-skills is a skill published in the GitHub repository davidruzicka/mcp4openapi (0 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,154 tokens. 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…
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…