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/dallay/agents-skills/express-apinpx skills add dallay/agents-skills --skill express-apigit clone --depth 1 https://github.com/dallay/agents-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/dallay/agents-skills/express-api)<a href="https://agentmods.dev/skills/dallay/agents-skills/express-api"><img src="https://agentmods.dev/badge/skills/dallay/agents-skills/express-api.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.00062 | $0.02079 |
| Opus 5 | $0.00031 | $0.01040 |
| Sonnet 5 | $0.00012 | $0.00416 |
| Haiku 4.5 | $0.00006 | $0.00208 |
Grade A, and why
express-api 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 3d 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 — 302 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to Use
- Building or refactoring a REST API with Express.js.
- Setting up middleware chains for authentication, logging, or validation.
- Structuring an Express project for maintainability and testability.
- Adding security headers, rate limiting, or CORS configuration.
- Implementing centralized error handling across routes.
Critical Patterns
- Layered Architecture: Separate routes → controllers → services → repositories. Routes define endpoints, controllers handle HTTP concerns, services contain business logic, repositories handle data access.
- Centralized Error Handling: NEVER scatter
try/catchin every route. Use an async wrapper and a single error-handling middleware at the end of the middleware chain. - Validate at the Edge: Validate ALL incoming data (body, params, query) at the route level using Zod or Joi BEFORE it reaches the controller.
- Security by Default: Always use
helmet, configurecorsexplicitly (never*in production), and apply rate limiting to public endpoints. - Environment Config: Use a validated config module. NEVER access
process.envdirectly throughout the codebase. - Consistent Response Shape: Every API response should follow the same envelope:
{ data, error, meta }.
Project Structure
src/
├── config/
│ └── env.ts # Validated environment config
├── middleware/
│ ├── errorHandler.ts # Centralized error handler
│ ├── validate.ts # Request validation middleware
│ ├── auth.ts # Authentication middleware
│ └── rateLimiter.ts # Rate limiting config
├── routes/
│ ├── index.ts # Route aggregator
│ └── users.routes.ts # /users route definitions
├── controllers/
│ └── users.controller.ts # HTTP concern handling
├── services/
│ └── users.service.ts # Business logic
├── repositories/
│ └── users.repository.ts # Data access
├── errors/
│ └── AppError.ts # Custom error classes
├── utils/
│ └── asyncHandler.ts # Async error wrapper
└── app.ts # Express app setup
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.
- 3d ago First seen · 302 lines · 62 tokens per session scan A fc3165634fd4
express-api is a skill published in the GitHub repository dallay/agents-skills (2 stars, last pushed 11d ago), licensed MIT. It adds 62 tokens to every session and 2,079 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…