development-workflow

A set of development standards and scripts for a Node.js and TypeScript project. It covers code organization, linting, type checks, tests, coverage reports, examples, templates, and continuous integration.

In plain words
What is it for?
Running the development server, checking code and types, running Mocha and Chai tests, measuring coverage, cleaning build files, maintaining examples, and updating project templates.
Why use it?
It makes routine quality checks repeatable and documents where code, tests, and templates belong. A single CI command can combine linting and test coverage checks.

Cursor rule for Codex

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/axiosleo/node-koapp/development-workflow
Clone the repo
git clone --depth 1 https://github.com/AxiosLeo/node-koapp

Made for: Codex.

Per session 427 This file is loaded in full into every session.
When invoked 427 The same file — it is already loaded in full.
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.00427 $0.00427
Opus 5 $0.00214 $0.00214
Sonnet 5 $0.00085 $0.00085
Haiku 4.5 $0.00043 $0.00043

Measured yesterday against content hash 97c4381dbef6, 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.

.agents/rules/development-workflow.mdc · 74 lines

What it actually says

Development Workflow and Standards

Code Quality

Linting

  • ESLint configuration in eslint.config.mjs
  • Run linting: npm run lint
  • TypeScript checking included in lint process

Testing

  • Mocha + Chai testing framework
  • Test files in tests/ directory with .tests.js suffix
  • Run tests: npm test
  • Coverage reports: npm run test-cov

Development Scripts

Available in package.json:

  • npm run dev - Development server with nodemon
  • npm run lint - ESLint + TypeScript checking
  • npm test - Run test suite
  • npm run test-cov - Tests with coverage
  • npm run ci - Full CI pipeline (lint + test-cov)
  • npm run clear - Clean build artifacts

File Organization

Source Code (src/)

  • Keep related functionality grouped in subdirectories
  • Use clear, descriptive file names
  • Follow existing patterns for consistency

Templates (assets/tmpl/)

  • Template files use .tmpl extension
  • Maintain template structure for project scaffolding
  • Update templates when adding new features

Examples

  • Comprehensive examples in tests/bootstrap.js
  • Simple examples in examples/ directory
  • Keep examples up-to-date with API changes

Dependencies

Runtime Dependencies

  • Koa.js ecosystem (koa, koa-bodyparser, koa-session, etc.)
  • Validation with validatorjs
  • WebSocket support with ws
  • UUID generation
  • CLI tools from @axiosleo/cli-tool

Development Dependencies

  • TypeScript for type checking
  • ESLint for code quality
  • Mocha/Chai for testing
  • NYC for coverage reporting

Version Requirements

  • Node.js >= 16.0.0
  • Use modern JavaScript features (async/await, destructuring, etc.)
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 · 74 lines · 427 tokens per session scan A 97c4381dbef6

Subscribe to this mod's changes

development-workflow is a cursor rule published in the GitHub repository AxiosLeo/node-koapp (129 stars, last pushed 18d ago), licensed MIT. It adds 427 tokens to every session, about $0.0021 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-30.