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/AxiosLeo/node-koappWrote 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/axiosleo/node-koapp/development-workflow)<a href="https://agentmods.dev/rules/axiosleo/node-koapp/development-workflow"><img src="https://agentmods.dev/badge/rules/axiosleo/node-koapp/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/axiosleo/node-koapp/development-workflow"><img src="https://agentmods.dev/badge/rules/axiosleo/node-koapp/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.00471 | $0.00471 |
| Opus 5.5 | $0.00188 | $0.00188 |
| Sonnet 5.5 | $0.00094 | $0.00094 |
| Haiku 4.5 | $0.00047 | $0.00047 |
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 today.
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 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.jssuffix - Run tests:
npm test - Coverage reports:
npm run test-cov
Development Scripts
Available in package.json:
npm run dev- Development server with nodemonnpm run lint- ESLint + TypeScript checkingnpm test- Run test suitenpm run test-cov- Tests with coveragenpm 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/monorepo/, assets/skills/)
- Template files use
.tmplextension;${name}is replaced with the app name duringkoapp init assets/skills/is copied verbatim into generated projects (.agents/skills/)- 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.)
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.
- today Changed · +1 lines · +44 tokens per session baa4b43c7733
- 1mo ago First seen · 74 lines · 427 tokens per session scan A 97c4381dbef6
development-workflow is a cursor rule published in the GitHub repository AxiosLeo/node-koapp (143 stars, last pushed yesterday), licensed MIT. It adds 471 tokens to every session, about $0.0019 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-30.
Other cursor rules, from other repositories
no-bare-casts
No bare as casts in production TypeScript. Use blindCast (value) from @internal/utils/casts as the auditable escape hatch, castAs (value) for declarative-only assertions, or rewrite to eliminate the cast. as const is exempt. Test files are exempt.
use-ast-factories
Use factory functions for creating AST nodes instead of manual object creation.
test-mocking-patterns
Test-only type assertions and mocking patterns (avoid brittle mocks).
tsdown-dist-layout-in-tests
Use tsdown dist root paths in TS test mappings.
jest-unit-testing-cursorrules-prompt-file
Cursor rules for Jest development with unit testing.
javascript
JavaScript and TypeScript conventions for this ESM monorepo.