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.
git 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/plugins/pactflow/pactflow-agent-skills/swagger-contract-testing)<a href="https://agentmods.dev/plugins/pactflow/pactflow-agent-skills/swagger-contract-testing"><img src="https://agentmods.dev/badge/plugins/pactflow/pactflow-agent-skills/swagger-contract-testing/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/plugins/pactflow/pactflow-agent-skills/swagger-contract-testing"><img src="https://agentmods.dev/badge/plugins/pactflow/pactflow-agent-skills/swagger-contract-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
swagger-contract-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 10d 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
{
"name": "swagger-contract-testing",
"description": "Expert assistant for PactFlow and Pact contract testing — consumer-driven contracts, provider verification, can-i-deploy, BDCT, Drift CLI, and OpenAPI spec parsing. Includes specialized agents for reviewing and generating pact tests.",
"version": "1.3.0",
"author": {
"name": "Kevin Rohan Vaz",
"email": "[email protected]"
},
"skills": "./skills/",
"agents": [
"./agents/pact-generator.md",
"./agents/pact-implementor.md",
"./agents/pact-reviewer.md",
"./agents/bdct-tester.md",
"./agents/pact-maintainer.md",
"./agents/pact-coverage.md"
],
"mcpServers": "./.mcp.json",
"userConfig": {
"pact_broker_base_url": {
"title": "PactFlow Base URL",
"description": "Your PactFlow or Pact Broker URL (e.g. https://yourorg.pactflow.io)",
"type": "string",
"sensitive": false
},
"pact_broker_token": {
"title": "PactFlow API Token",
"description": "PactFlow API token — get it from app.pactflow.io/settings/api-tokens",
"type": "string",
"sensitive": true
}
}
}
What it installs
The manifest is a name and a version. 6 skills, 6 agents, 2 hooks, 1 MCP server travel with it, and installing the plugin installs all of them — 1,696 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill drift-testing A 203 tokens
- Skill pact-coverage A 220 tokens
- Skill asyncapi-generator A 205 tokens
- Skill asyncapi-parser A 160 tokens
- Skill oas-generator A 164 tokens
- Skill openapi-parser A 145 tokens
- Agent pact-implementor A 133 tokens
- Agent bdct-tester A 117 tokens
- Agent pact-coverage A 67 tokens
- Agent pact-maintainer A 109 tokens
- Agent pact-reviewer A 77 tokens
- Agent pact-generator A 96 tokens
- Hook SessionStart A not measured
- Hook PostToolUse A not measured
- MCP server smartbear A not measured
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.
- 10d ago Changed · +7 lines 655276efc645
- 25d ago Changed d6964791c394
- 1mo ago First seen · 27 lines scan A 2ad53303e437
swagger-contract-testing is a plugin published in the GitHub repository pactflow/pactflow-agent-skills (7 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
vibe-engineering
33 engineering discipline skills for Claude Code, OpenAI Codex & Gemini CLI — research, quality gates, reward-hacking checks, testing patterns, deployment, gap analysis, spec sync, and more. Extracted from real-world development.
auto-harness
Run Claude Code like a specialist software team: planning, implementation, QA, fix/retest loops, and durable serial or parallel harness state for long-running project delivery.
forge
Multi-agent collaborative development workflow: Planner → Dev → Test → Learn with automatic bug-fix loops, test layering, and experience accumulation.
swiftui-autotest-skill
AI-powered visual testing and accessibility setup for iOS/SwiftUI apps. Build, launch in Simulator, test with computer use, detect crashes, analyze memory leaks, and add accessibility identifiers.
clean-code-skills
20 skills covering TDD, Refactoring, SOLID, OOP, Functional Programming, Hexagonal Architecture, and Clean Code principles for Claude Code.
gut-skill
Claude Code skill for the GUT (Godot Unit Testing) framework — test structure, assertions, doubles, async helpers, memory management, and CLI usage for GDScript.