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/cypsy1714/cchad/express-skillnpx skills add Cypsy1714/cchad --skill express-skillgit clone --depth 1 https://github.com/Cypsy1714/cchadWrote 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/cypsy1714/cchad/express-skill)<a href="https://agentmods.dev/skills/cypsy1714/cchad/express-skill"><img src="https://agentmods.dev/badge/skills/cypsy1714/cchad/express-skill.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.00017 | $0.00214 |
| Opus 5 | $0.00009 | $0.00107 |
| Sonnet 5 | $0.00003 | $0.00043 |
| Haiku 4.5 | $0.00002 | $0.00021 |
Grade A, and why
express-conventions 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 4d 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
Express conventions
Structure
- Split routes into
Routers per resource; keep handlers thin and put business logic in a service layer. - Validate and parse input at the edge (a schema library) before it reaches logic.
- Centralize configuration; read env once into a typed config object.
Middleware & errors
- Order middleware deliberately: parsers → auth → routes → error handler last.
- Wrap async handlers so rejected promises reach your error middleware (or use a helper / Express 5's built-in async handling) — don't let errors go unhandled.
- Use a single error-handling middleware that maps errors to status codes; don't leak stack traces to clients.
Practical
- Never build SQL or shell strings from user input; use parameterized queries.
- Set security headers (helmet), enable CORS intentionally, and rate-limit public APIs.
- Return consistent JSON shapes and correct status codes.
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.
- 4d ago First seen · 25 lines · 17 tokens per session scan A 087a281f9ce1
express-conventions is a skill published in the GitHub repository Cypsy1714/cchad (1 stars, last pushed 2mo ago), licensed MIT. It adds 17 tokens to every session and 214 once invoked, about $0.0001 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
deploy-setup
Wire up a freshly scaffolded Starter Series project for its first release — detect the template, register required GitHub secrets, set up OIDC trusted publishing where applicable, and trigger the first CD run. Pairs with the create skill (you scaffold first, then run this).
create
Scaffold a new project from the Starter Series templates (MCP server, Discord/Telegram bot, VS Code / browser extension, Electron, React Native, Cloudflare Pages, npm package, Docker deploy).
calibration-onboarding
First-time setup guide for claude-calibration and Claude Code config in general. Detects what config the project already has (CLAUDE.md, .claude/, settings.json, hooks, agents, skills, .mcp.json), names the minimal viable additions for this project's stack, and bridges into /claude-calibration:calibration-doctor…
calibration
Discovery-friendly dispatcher above /calibrate. With no args, prints a menu of every calibration flow — the three /calibrate built-in modes (tighten / harden / cost), the two standalone convenience flows (audit, diff), and the per-feature shortcuts (skills / subagents / claude-md / rules / settings / hooks / mcp /…
calibrate-plugins
Audits installed plugins, registered marketplaces, and (when the project itself is a plugin) the local manifest at .claude-plugin/plugin.json. Flags manifests missing name or version, manifests that don't parse, components misplaced under .claude-plugin/ instead of at the plugin root, plugins that use legacy commands/…
calibration-audit
Read-only audit — runs the calibration planner-init and evaluator-baseline phases, prints the per-feature findings, then stops. No improvement plan, no approval gate, no edits. The same first half of /calibrate. Use this as a periodic health check or a CI gate when you only want to know "what's wrong" without applying…