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/bowen31337/expressjs_mcpWrote 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/rules/bowen31337/expressjs_mcp/development-workflow)<a href="https://agentmods.dev/rules/bowen31337/expressjs_mcp/development-workflow"><img src="https://agentmods.dev/badge/rules/bowen31337/expressjs_mcp/development-workflow/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/rules/bowen31337/expressjs_mcp/development-workflow"><img src="https://agentmods.dev/badge/rules/bowen31337/expressjs_mcp/development-workflow.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.00004 | $0.00319 |
| Opus 5.5 | $0.00002 | $0.00128 |
| Sonnet 5.5 | $0.00001 | $0.00064 |
| Haiku 4.5 | $0.00000 | $0.00032 |
Grade A, and why
development-workflow 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.
What it actually says
Development Workflow
Package Management
Use pnpm as the package manager (not npm or yarn):
pnpm install
pnpm add <package>
pnpm add -D <dev-package>
Development Commands
pnpm dev- Watch mode compilation with tsuppnpm build- Production build (ESM + CJS + types)pnpm lint- Check code with Biomepnpm lint:fix- Fix linting issues automaticallypnpm test- Run tests with Vitestpnpm test:watch- Watch mode testing
Testing Strategy
Follow TDD principles:
- Write tests first for new features
- Ensure 90%+ coverage on core modules
- Test both unit and integration scenarios
- Use supertest for HTTP endpoint testing
Code Quality
- Biome handles linting, formatting, and import organization
- TypeScript strict mode enabled
- All code must pass linting before commit
- Run tests before continuing to next task
File Organization
src/ # Source code
tests/ # Test files
examples/ # Usage examples
docs/ # Documentation
.cursor/rules/ # Cursor AI rules
Build Output
dist/index.cjs- CommonJS builddist/index.mjs- ES Module builddist/index.d.ts- TypeScript declarations
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 First seen · 48 lines · 4 tokens per session scan A 45deaeae3b48
development-workflow is a cursor rule published in the GitHub repository bowen31337/expressjs_mcp (1 stars, last pushed 1y ago), licensed MIT. It adds 4 tokens to every session and 319 once invoked, about $0.0000 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 cursor rules, from other repositories
workflow
Development workflow and commit practices.
practices
Engineering practices and definition of done for agent work.
cmd-build
Implement the next task incrementally — build, test, verify, commit.
task-execution
CRITICAL RULE - Task execution workflow. All tasks must follow TDD, be modular, and integrate with GitHub workflow (branch creation, status updates).
mcpnuke-tests
Test conventions for mcpnuke — enforces TDD workflow.
roslyn-mcp-version-bump
Auto-bump Version after successful MCP self-build and reload.