Borrowing it
Nothing to install: this file belongs to davidruzicka/mcp4openapi. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/davidruzicka/mcp4openapi/main/.claude/skills/focus-on-fix-validity-over-pr-process/SKILL.mdgit 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/focus-on-fix-validity-over-pr-process)<a href="https://agentmods.dev/skills/davidruzicka/mcp4openapi/focus-on-fix-validity-over-pr-process"><img src="https://agentmods.dev/badge/skills/davidruzicka/mcp4openapi/focus-on-fix-validity-over-pr-process.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.00036 | $0.00227 |
| Opus 5 | $0.00018 | $0.00113 |
| Sonnet 5 | $0.00007 | $0.00045 |
| Haiku 4.5 | $0.00004 | $0.00023 |
Grade A, and why
focus-on-fix-validity-over-pr-process 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 6d 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.
What it actually says
Goal
Evaluate whether a security fix actually mitigates the intended risk before discussing CI/check status.
When to Use
- User asks whether a security PR/fix is valid.
- User distinguishes process validity from fix validity.
- Review context includes SSRF/auth/security hardening.
Rules
- Start with fix validity: what attack path is blocked, what remains open, and severity.
- Provide code-based evidence with file and line references for each finding.
- Report process status (CI, checks, mergeability) only as secondary context unless explicitly requested first.
- If fix is partial, explicitly describe residual risk and required follow-up.
- Keep recommendations scoped to the target security mechanism (do not broaden to unrelated subsystems).
Output Pattern
- Findings ordered by severity.
- Verdict on fix validity (complete, partial, or invalid).
- Secondary process note (optional).
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.
- 6d ago First seen · 25 lines · 36 tokens per session scan A b87a2a4b972b
focus-on-fix-validity-over-pr-process is a skill published in the GitHub repository davidruzicka/mcp4openapi (0 stars, last pushed 2d ago), licensed MIT. It adds 36 tokens to every session and 227 once invoked, about $0.0002 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.
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…
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…