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.
npx agentmods add rules/r-huijts/ethics-check-mcp/development-workflowgit clone --depth 1 https://github.com/r-huijts/ethics-check-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/r-huijts/ethics-check-mcp/development-workflow)<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="Measured on agentmods" 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 | $0.00000 | $0.00590 |
| Opus 5 | $0.00000 | $0.00295 |
| Sonnet 5 | $0.00000 | $0.00118 |
| Haiku 4.5 | $0.00000 | $0.00059 |
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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Development Workflow Guide
Setup & Installation
- Install Dependencies:
npm install- Installs all required packages including MCP SDK, Gemini AI, and TypeScript - Environment Setup: Copy env.example to
.envand add yourGEMINI_API_KEY - Build Project:
npm run build- Compiles TypeScript and sets executable permissions
Development Commands
- Development Mode:
npm run dev- Auto-recompiles and restarts on file changes - Build Only:
npm run build- Compiles TypeScript to build/ directory - Start Server:
npm start- Runs the compiled server (requires GEMINI_API_KEY) - Test Build:
GEMINI_API_KEY=test_key node build/index.js- Test server startup
Code Structure Guidelines
Adding New Tools
- Create tool file in src/tools/ following the pattern of ethicsCheck.ts
- Define Input/Output interfaces
- Implement async tool function with Gemini AI integration
- Register tool in src/index.ts
ListToolsRequestSchemahandler - Add tool execution case in
CallToolRequestSchemahandler
Modifying Ethical Categories
- Update
ETHICAL_CATEGORIESarray in src/utils/storage.ts - Categories are used across all tools for consistency
- Changes affect tool schemas in src/index.ts
AI Prompt Engineering
- Ethical analysis prompts are in individual tool files
- Use structured JSON responses for consistent parsing
- Include fallback handling for non-JSON responses
- Reference ethical frameworks: consequentialism, deontology, virtue ethics, care ethics, justice
Integration Testing
- Build Verification: Ensure
npm run buildcompletes without errors - Server Startup: Test with valid GEMINI_API_KEY
- Claude Desktop: Update claude_desktop_config.json with correct path
- Tool Testing: Use MCP inspector or Claude Desktop to test tool calls
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.
- 5d ago First seen · 50 lines · 0 tokens per session scan A 516cd855d5e4
development-workflow is a cursor rule published in the GitHub repository r-huijts/ethics-check-mcp (5 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 590 tokens. 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
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.