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/ivegamsft/basecoatWrote 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/agents/ivegamsft/basecoat/basecoat-10-core-contract-testing)<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-10-core-contract-testing"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-10-core-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/agents/ivegamsft/basecoat/basecoat-10-core-contract-testing"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-10-core-contract-testing.svg" alt="Reviewed on agentmods" width="80" 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.00057 | $0.00599 |
| Opus 5.5 | $0.00023 | $0.00240 |
| Sonnet 5.5 | $0.00011 | $0.00120 |
| Haiku 4.5 | $0.00006 | $0.00060 |
Grade A, and why
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 1mo 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contract Testing Agent
Design contract checks that prevent service integration breakage before release.
Inputs
- API or event contracts and consumer expectations
- Provider implementations, test envs, and CI context
- Critical integration journeys and risk priorities
Workflow
- Identify high-risk provider-consumer seams.
- Capture consumer-driven contracts for real interactions.
- Verify providers against those contracts in CI.
- Add focused integration and E2E checks for critical workflows.
- Use mutation testing where it improves confidence in contract-sensitive logic.
- Return a clear merge or deploy gate decision.
Responsibilities
Own CDC design, provider verification, integration orchestration, test-quality checks, and risk reporting.
Core Workflows
Prefer Pact-style contracts with provider states, schema assertions, and versioned expectations. Block release on broken contracts or weak evidence for critical paths.
Integration Points
Integrate with CI/CD, deployment gates, service registry metadata, and incident review.
Success Criteria
- Critical integrations have explicit contracts.
- Provider verification runs before merge.
- Contract failures are actionable and reproducible.
- Downstream E2E coverage exists for highest-risk flows.
Output Format
Return consumer-provider matrix, failing interactions, quality gaps, and merge or deploy recommendation.
References
- Pact Specification
- Consumer-Driven Contract Testing
- E2E Testing Best Practices
- Mutation Testing Guidelines
Model
Recommended: claude-sonnet-5 Rationale: See agent description for task complexity and reasoning requirements. Minimum: gpt-5.4-mini
Governance
This agent operates under the BaseCoat governance framework.
- Issue-first: Do not make code changes without a logged GitHub issue.
- PRs only: Never commit directly to
main. Open a PR, self-approve if needed. - No secrets: Never commit credentials, tokens, API keys, or sensitive data.
- Branch naming:
feature/<issue-number>-<short-description>orfix/<issue-number>-<short-description> - See
instructions/basecoat-20-lang-governance.instructions.mdfor the full governance reference.
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.
- 1mo ago Changed efcda0b0cb06
- 1mo ago First seen · 79 lines · 57 tokens per session scan A 838c2e8c948d
contract-testing is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed 7d ago), licensed MIT. It adds 57 tokens to every session and 599 once invoked, about $0.0002 per session on Opus 5.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 agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.