Borrowing it
Nothing to install: this file belongs to prolific-oss/cli. 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/prolific-oss/cli/main/.claude/skills/schema-drift-fix/SKILL.mdgit clone --depth 1 https://github.com/prolific-oss/cliWrote 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/prolific-oss/cli/schema-drift-fix)<a href="https://agentmods.dev/skills/prolific-oss/cli/schema-drift-fix"><img src="https://agentmods.dev/badge/skills/prolific-oss/cli/schema-drift-fix.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.00052 | $0.01035 |
| Opus 5 | $0.00026 | $0.00517 |
| Sonnet 5 | $0.00010 | $0.00207 |
| Haiku 4.5 | $0.00005 | $0.00103 |
Grade A, and why
schema-drift-fix 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 2d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Schema Drift Fix
When to Use This Skill
Invoke this skill when the user:
- References a
schema-drift-labeled issue - Asks to "fix schema drift", "check for API drift", or similar
- Uses the slash command /schema-drift-fix
Check whether the CLI's client package still matches the live Prolific API spec, and propose the fix if it doesn't — following the same checklist a human would use when adding a new API method. This skill investigates and drafts; it does not commit, push, or open a PR. The engineer reviews and does that themselves.
Arguments
issue-number (optional) — a schema-drift issue filed by .github/workflows/schema-drift-check.yml.
This skill does not depend on an issue existing. An issue is a convenient shortcut when CI already found and described drift, but the real source of truth is always a fresh go test ./contract_test/... run (Phase 1, step 1) — an issue's captured output can be stale by the time someone picks it up.
- If
issue-numberis given:gh issue view <issue-number> --json title,body,state— confirm it's an open issue with a title matchingAPI schema drift detected (...), and use its body as corroborating context. - If omitted: skip the issue lookup entirely and just run the check directly. This is the default, everyday way to invoke this skill — proactively, not only after CI has already filed something.
Phase 1: Investigate
- Run
go test ./contract_test/...locally (this downloads the live Prolific OpenAPI spec itself, same as the workflow). If it passes: report "no drift detected" and stop here — there's nothing to do, regardless of whether an issue was given. If it fails, continue. - If an issue number was given, cross-check its body against this fresh result — same operation(s) failing? Anything CI's snapshot called out that isn't reproducing now? Flag any mismatch rather than trusting either source silently.
- Identify which operation(s)/test case(s) are failing from the fresh output.
- Cross-reference
contract_test/contract_test.go'soperationstable entry for the affected operation(s) against the live spec to determine exactly what changed (new/renamed/removed field, changed type, new required param, etc.).
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.
- 2d ago First seen · 80 lines · 52 tokens per session scan A a41b7a27deee
schema-drift-fix is a skill published in the GitHub repository prolific-oss/cli (13 stars, last pushed 4d ago), licensed Apache-2.0. It adds 52 tokens to every session and 1,035 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-09-03.
Other skills, from other repositories
platform-apex-generate
Primary Apex authoring skill for class generation, refactoring, and review. ALWAYS ACTIVATE when the user mentions Apex, .cls, triggers, or asks to create/refactor a class (service, selector, domain, batch, queueable, schedulable, invocable, DTO, utility, interface, abstract, exception, REST resource). Use this skill…
flow-next-impl-review
Carmack-level implementation review of changes via the configured backend. Use when asked to review code or a diff in a flow-next repo.
flow-next-resolve-pr
Resolve PR review feedback. Fetches unresolved threads, triages, fixes, replies and resolves via GraphQL. Use when asked to address review comments.
api-contract-review
Use when auditing CloudBase cloud API wrappers, MCP tools, generated action metadata, or related docs for outdated or incorrect action names, parameters, casing, request shapes, or missing contract tests, especially during periodic quality review or before preparing corrective PRs.
principle-model-the-domain
Apply when writing stateful logic, or when code branches a lot or repeats a shape assumption across files. Encode the domain in a structure instead of scattered conditionals.
code-review-nodejs
Applies Node.js-specific code review patterns for async I/O, streams, security, process management, and dependency hygiene. Use when reviewing Node.js server code, route handlers, middleware, or any JavaScript file alongside package.json without TypeScript. Triggers on sync I/O in request paths, missing stream…