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/pactflow/pactflow-agent-skills/drift-testingnpx skills add pactflow/pactflow-agent-skills --skill drift-testinggit clone --depth 1 https://github.com/pactflow/pactflow-agent-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/pactflow/pactflow-agent-skills/drift-testing)<a href="https://agentmods.dev/skills/pactflow/pactflow-agent-skills/drift-testing"><img src="https://agentmods.dev/badge/skills/pactflow/pactflow-agent-skills/drift-testing.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 | $0.00158 | $0.03526 |
| Opus 5 | $0.00079 | $0.01763 |
| Sonnet 5 | $0.00032 | $0.00705 |
| Haiku 4.5 | $0.00016 | $0.00353 |
Grade A, and why
drift-testing 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 — 378 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Drift Skill
Never modify the openapi spec that you are testing.
Reference Files
references/test-cases.md— Full test case YAML schema, all patterns, datasets, expressionsreferences/auth.md— Authentication config, dynamic tokens, non-standard schemes, 401/403 testingreferences/mock-server.md— Local testing with Prism: setup, Prefer header, spec quality issuesreferences/lua-api.md— Complete Lua API: lifecycle events,http(),dbg(), exported functionsreferences/cli-reference.md— All CLI commands/flags, configuration, parallel execution, exit codesreferences/pactflow-and-cicd.md— BDCT publishing workflow, GitHub Actions, GitLab CI
Scripts
scripts/extract_endpoints.py— Reads the spec and outputs all operations + response codes. Summary mode flags parameters with no spec example. Scaffold mode (--scaffold) emits a ready-to-filloperations:YAML block with correct auth patterns, nil UUIDs for 404s,ignore.schemafor 4xx, andFILL_INmarkers. Use--only-missing <drift.yaml>to generate only the gaps not yet covered by an existing test file. Requirespyyaml.scripts/check_coverage.py— Coverage checker: diffs an OpenAPI spec against Drift test files and reports which operations and response codes are missing tests. Requirespyyaml.scripts/run_loop.sh/scripts/run_loop.ps1— Feedback loop runner: retriesdrift verify --faileduntil all tests pass, then runscheck_coverage.py. Both gates must pass for exit 0. Dependencies are installed automatically via uv. Use the.ps1version on Windows.scripts/start_mock.sh/scripts/start_mock.ps1— Starts a Prism mock server from an OpenAPI spec. Installs Prism if needed. Supports--portand--dynamicflags. Use the.ps1version on Windows.
Full docs: https://support.smartbear.com/swagger/contract-testing/docs/en/drift.html
To discover all available pages, fetch the sitemap: https://support.smartbear.com/swagger/contract-testing/docs/sitemap.xml
What ships with it
17 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.
- evals/01-basic-get-endpoint.json 1.1 KB
- evals/02-stateful-delete-endpoint.json 1.2 KB
- evals/03-debug-failing-test.json 1.1 KB
- evals/fixtures/products-api-with-failures.md 576 B
- evals/fixtures/simple-products-api.yaml 1.2 KB
- references/auth.md 4.2 KB
- references/cli-reference.md 5.2 KB
- references/lua-api.md 6.1 KB
- references/mock-server.md 4.1 KB
- references/pactflow-and-cicd.md 8.2 KB
- references/test-cases.md 9.8 KB
- scripts/check_coverage.py 12 KB runs code
- scripts/extract_endpoints.py 20 KB runs code
- scripts/run_loop.ps1 4.5 KB runs code
- scripts/run_loop.sh 4.7 KB runs code
- scripts/start_mock.ps1 1.9 KB runs code
- scripts/start_mock.sh 1.7 KB runs code
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 · 378 lines · 158 tokens per session scan A 0346ba7fae61
drift-testing is a skill published in the GitHub repository pactflow/pactflow-agent-skills (6 stars, last pushed 5d ago), licensed MIT. It adds 158 tokens to every session and 3,526 once invoked, about $0.0008 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
codex-setup
Initialize sd0x-dev-flow infrastructure for Codex CLI and other non-Claude agents. Generates AGENTS.md, installs the commit-msg hook, copies runner scripts. The pre-push gate is opt-in via --with-push-gate. Use when setting up a new project or after updating skills.
codex-implement
Implement features via Codex exec. Use when: writing new code from specs, implementing features, Codex-driven development. Not for: code review (use codex-code-review), architecture advice (use codex-architect). Output: implemented code + review loop.
smart-rebase
Smart partial rebase for squash-merge repositories. Auto-detect which commits to keep/drop when base branch was squash-merged into target. Use when: user says 'rebase', 'partial rebase', 'base already merged', 'smart rebase', or /smart-rebase. Not for: simple git rebase (the developer runs it — Claude never executes…
orchestrate
Agent-driven workflow orchestration (v1 report-only). Use when: declaring an intent (audit/research/feature shape) and wanting a planner agent to derive the skill workflow, preview it, and run read-only fanout with fail-closed no-change verification. Not for: executing mutating steps (v1 emits them as…
recap-doc
Post-development recap document generator. Use when: AI/Codex has implemented a feature and the user needs a guided walkthrough of what changed and why, with blind-spot detection and anticipated questions. Not for: Q&A follow-up (use /recap-ask), technical share-out for teammates (use /tech-brief), or generic code…
runbook
Generate and update feature release runbooks from existing docs and codebase. Use when: creating operational runbook, release handbook, deployment checklist, pre-release preparation. Not for: incident response (v2), code review (use codex-code-review), architecture design (use architecture).