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/swesmith/davila7__claude-code-templates.734b8a50Wrote 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/commands/swesmith/davila7__claude-code-templates.734b8a50/middleware)<a href="https://agentmods.dev/commands/swesmith/davila7__claude-code-templates.734b8a50/middleware"><img src="https://agentmods.dev/badge/commands/swesmith/davila7__claude-code-templates.734b8a50/middleware.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.00000 | $0.00572 |
| Opus 5 | $0.00000 | $0.00286 |
| Sonnet 5 | $0.00000 | $0.00114 |
| Haiku 4.5 | $0.00000 | $0.00057 |
Grade A, and why
middleware 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 7d 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.
This is a copy
100% identical to middleware — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Express Middleware
Create Express middleware for $ARGUMENTS following project conventions.
Task
Create or optimize Express middleware based on the requirements:
- Analyze existing middleware: Check current middleware patterns, naming conventions, and file organization
- Examine Express setup: Review app configuration, middleware stack order, and TypeScript usage
- Identify middleware type: Determine the middleware category:
- Authentication/Authorization (JWT, sessions, role-based)
- Validation (request body, params, query validation)
- Logging (request/response logging, audit trails)
- Error handling (global error handlers, custom errors)
- Security (CORS, rate limiting, helmet)
- Utility (parsing, compression, static files)
- Check dependencies: Review existing middleware dependencies to avoid duplication
- Implement middleware: Create middleware with proper TypeScript types and error handling
- Test middleware: Write unit and integration tests following project patterns
- Update middleware stack: Integrate middleware into Express app configuration
- Add documentation: Include JSDoc comments and usage examples
Implementation Requirements
- Follow project's TypeScript conventions and interfaces
- Use existing error handling patterns and response formats
- Include proper request/response typing with custom interfaces
- Add comprehensive error handling and logging
- Consider middleware execution order and dependencies
- Implement proper async/await patterns for async middleware
- Follow project's folder structure for middleware files
Middleware Patterns to Consider
Based on the request:
- Authentication: JWT verification, session management, API key validation
- Authorization: Role-based access control, permission checking
- Validation: Schema validation with Joi/Zod, sanitization
- Logging: Request logging, performance monitoring, audit trails
- Error Handling: Global error handlers, custom error classes
- Security: CORS configuration, rate limiting, input sanitization
- Utility: Request parsing, response formatting, caching
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.
- 7d ago First seen · 61 lines · 0 tokens per session scan A 2a7b7a3daaa4
middleware is a command published in the GitHub repository swesmith/davila7__claude-code-templates.734b8a50 (2 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 572 tokens. A static security scan graded it A with 0 findings. It is 100% identical to middleware, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
init
Initialize configurations for Supabase local development.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
start-10-1
A guided lesson on setting up clasp, a command-line tool for managing Google Apps Script projects, and connecting it to Google’s Apps Script API.
api-contract-review
Review an API contract (endpoints, request/response shapes, error codes, auth model) BEFORE implementation for naming consistency, versioning, pagination, idempotency, and alignment with existing endpoints. Distinct from review-hard (post-implementation risk) and repo-consistency-sweep (pattern matching on written…
build
Discover an AI Gateway's models and MCP tools, retrieve a credential, and integrate them into your app — call a model, connect MCP tools, or scaffold a runnable agent.
fastapi
FastAPI application design and implementation conventions. Use this skill when building, updating, or reviewing FastAPI services, routers, dependencies, request/response schemas, streaming endpoints, or API tests. Trigger on FastAPI-specific work such as path operation design, dependency injection, response models…