agentmods.dev

development-workflow

A set of project rules for using pnpm, a JavaScript package manager, along with prescribed build, lint, and test commands. It also requires TDD, meaning tests are written before new code.

In plain words
What is it for?
Developing and maintaining a TypeScript package with pnpm, strict type checking, automated formatting, unit and integration tests, and defined build outputs.
Why use it?
It gives contributors one consistent way to install dependencies, check code, and run tests. The rules also require linting and tests to pass before work is considered complete.

Cursor rule for Cursor

1 1y ago A scan 4 tokens original MIT
View the source file bowen31337/expressjs_mcp
Install

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.

agentmods
npx agentmods add rules/bowen31337/expressjs_mcp/development-workflow
Clone the repo
git clone --depth 1 https://github.com/bowen31337/expressjs_mcp

Made for: Cursor.

Per session 4 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 319 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00004 $0.00319
Opus 5 $0.00002 $0.00160
Sonnet 5 $0.00001 $0.00064
Haiku 4.5 $0.00000 $0.00032

Measured yesterday against content hash 45deaeae3b48, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

.cursor/rules/development-workflow.mdc · 48 lines

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 tsup
  • pnpm build - Production build (ESM + CJS + types)
  • pnpm lint - Check code with Biome
  • pnpm lint:fix - Fix linting issues automatically
  • pnpm test - Run tests with Vitest
  • pnpm test:watch - Watch mode testing

Testing Strategy

Follow TDD principles:

  1. Write tests first for new features
  2. Ensure 90%+ coverage on core modules
  3. Test both unit and integration scenarios
  4. 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 build
  • dist/index.mjs - ES Module build
  • dist/index.d.ts - TypeScript declarations
Changes

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.

  1. yesterday First seen · 48 lines · 4 tokens per session scan A 45deaeae3b48

Subscribe to this mod's changes

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. 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.

Code reviewLanguagesTesting
Related

Other cursor rules, from other repositories

angular-20

This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.

angular/angular · 0 tokens

dev-standard

Apache Superset development standards and guidelines for Cursor IDE.

apache/superset · 1,147 tokens

typescript

Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.

streamlit/streamlit · 4,669 tokens

coolify-ai-docs

Master reference to all Coolify AI documentation in .ai/ directory.

coollabsio/coolify · 1,426 tokens

python_lib

Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.

streamlit/streamlit · 0 tokens

specs

This directory contains product and tech specs for Streamlit features.

streamlit/streamlit · 0 tokens