development-workflow

development-workflow is a cursor rule for Cursor from r-huijts/ethics-check-mcp. It costs 11 tokens per session (226 once invoked), scanned A, original, MIT.

A development guide for an MCP project built with TypeScript, including setup, build, development, testing, code structure, and adding tools.

In plain words
What is it for?
Use it to set up the project, run or test its build, add new tools, change ethical categories, and understand where related code belongs.
Why use it?
It gives contributors a shared workflow for installing dependencies, running the project, and extending its tools consistently.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it to set up the project, run or test its build, add new tools, change ethical categories, and understand where related code belongs.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/r-huijts/ethics-check-mcp/development-workflow
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.

Clone the repo
git clone --depth 1 https://github.com/r-huijts/ethics-check-mcp

Made for: Cursor.

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

agentmods badge for development-workflow

README.md
[![agentmods](https://agentmods.dev/badge/rules/r-huijts/ethics-check-mcp/development-workflow/github.svg)](https://agentmods.dev/rules/r-huijts/ethics-check-mcp/development-workflow)
Your own site
<a href="https://agentmods.dev/rules/r-huijts/ethics-check-mcp/development-workflow"><img src="https://agentmods.dev/badge/rules/r-huijts/ethics-check-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.

agentmods 80×15 button for development-workflow

Your own site · 80×15
<a href="https://agentmods.dev/rules/r-huijts/ethics-check-mcp/development-workflow"><img src="https://agentmods.dev/badge/rules/r-huijts/ethics-check-mcp/development-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 226 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00011 $0.00226
Opus 5.5 $0.00004 $0.00090
Sonnet 5.5 $0.00002 $0.00045
Haiku 4.5 $0.00001 $0.00023

Measured 22d ago against content hash effbbebd63ec, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 22d 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.

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

What it actually says

Development workflow

  1. npm install
  2. Copy env.example → .env (or use ETHICS_PROVIDER=mock for offline work)
  3. npm run build
  4. npm run test:all

Commands

  • npm run dev — build + start stdio server
  • npm run test:session — drift / tags / feedback unit tests
  • npm run test:calibration — false-positive smoke fixtures via mock provider
  • npm run test:calibration:live — same fixtures against whatever ETHICS_PROVIDER is set
  • npm run install-skill — copy companion skill to ~/.cursor/skills

Adding a tool

  1. Implement under src/tools/
  2. Register schema + handler in src/index.ts
  3. Prefer resolveSessionId() for any session-scoped behavior
  4. Keep prompts calibrated: empty/low findings must remain valid
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. 22d ago Changed · -25 lines · +11 tokens per session effbbebd63ec
  2. 2mo ago First seen · 50 lines · 0 tokens per session scan A 516cd855d5e4

Subscribe to this mod's changes

development-workflow is a cursor rule published in the GitHub repository r-huijts/ethics-check-mcp (5 stars, last pushed 22d ago), licensed MIT. It adds 11 tokens to every session and 226 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.