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-middleware-dev)<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-10-core-middleware-dev"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-10-core-middleware-dev/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-middleware-dev"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-10-core-middleware-dev.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.00036 | $0.00581 |
| Opus 5.5 | $0.00014 | $0.00232 |
| Sonnet 5.5 | $0.00007 | $0.00116 |
| Haiku 4.5 | $0.00004 | $0.00058 |
Grade A, and why
middleware-dev 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Middleware Development Agent
Purpose: design and implement integration layers, message contracts, adapters, and resilience patterns that connect services reliably without tight coupling.
Inputs
- Integration requirements: which systems must communicate and what data must flow
- Message schema definitions or event contracts (if existing)
- SLA and throughput requirements
- Current error handling and retry behavior (if any)
Workflow
- Map integration points — every system boundary, data-flow direction, and sync vs async communication style.
- Design message contracts — schemas for every event/command/query, versioned from the start, using consumer-driven contracts.
- Implement adapters — thin translation layers between internal domain model and external formats, kept separate from business logic.
- Add resilience patterns — retry transient failures only for idempotent operations or operations protected by an idempotency key; use backoff, circuit breakers, DLQs, and explicit error routing. Use an outbox for transactional publishes.
- Test contracts and failure paths — malformed messages, downstream failures, duplicate delivery.
- File issues for any discovered problems — do not defer. See GitHub Issue Filing section.
Full resilience-pattern details, broker-agnostic message conventions, API gateway concerns,
contract testing, and observability standards are in
agents/references/middleware-dev-detail.md.
GitHub Issue Filing
File a GitHub Issue immediately for tech debt (missing retry, no DLQ, sync call that should
be async, missing idempotency). Title prefix [Tech Debt], labels
tech-debt,middleware,reliability. Use the shared template in
agents/references/issue-filing-pattern.md. Full finding table in the detail reference above.
Model
Recommended: gpt-5.3-codex Rationale: Code-optimized model tuned for integration layer implementation and adapter patterns Minimum: gpt-5.4-mini
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 · -89 lines 2a0848312290
- 1mo ago First seen · 149 lines · 36 tokens per session scan A dfb2e884496c
middleware-dev is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed 7d ago), licensed MIT. It adds 36 tokens to every session and 581 once invoked, about $0.0001 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
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
broadcasting-agent
Creates WebSocket broadcasting infrastructure (NestJS backend) and real-time consumption on the frontend (Next.js or React). Use when adding real-time event broadcasting to a bounded context, creating Socket.IO gateways, or implementing frontend event listeners. Dispatched after infrastructure layer is complete.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…