Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/gargoyle92/agentify-mcpnpx agentmods add rules/gargoyle92/agentify-mcp/07-development-workflowWrote 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/gargoyle92/agentify-mcp/07-development-workflow)<a href="https://agentmods.dev/rules/gargoyle92/agentify-mcp/07-development-workflow"><img src="https://agentmods.dev/badge/rules/gargoyle92/agentify-mcp/07-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/gargoyle92/agentify-mcp/07-development-workflow"><img src="https://agentmods.dev/badge/rules/gargoyle92/agentify-mcp/07-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.00000 | $0.02171 |
| Opus 5.5 | $0.00000 | $0.00868 |
| Sonnet 5.5 | $0.00000 | $0.00434 |
| Haiku 4.5 | $0.00000 | $0.00217 |
Grade A, and why
07-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 2mo 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 — 322 lines — stays where its author put it; the contents beside it link to each section on GitHub.
07-Development-Workflow
Development Environment Setup
The project uses TypeScript with ESNext modules and strict type checking as configured in tsconfig.json.
Required Tools and Scripts
- Development:
npm run dev- Uses tsx for hot reloading - Building:
npm run build- TypeScript compilation - Testing:
npm run test- Jest test runner - Linting:
npm run lint- ESLint with TypeScript rules - Formatting:
npm run format- Prettier code formatting
CRITICAL DEVELOPMENT RULES - MUST FOLLOW
✅ ALWAYS DO:
- Run type checking: Use
npm run typecheckbefore committing - Follow code formatting: Use
npm run formatto maintain consistency - Write tests first: Implement tests alongside or before implementation
- Validate MCP compliance: Test all tools and resources against MCP standards
- Update documentation: Keep README and code comments current
❌ NEVER DO:
- Commit without linting: Never commit code that fails ESLint checks
- Skip type checking: Never ignore TypeScript errors or warnings
- Commit failing tests: All tests must pass before committing
- Mix concerns: Keep tools, resources, and server logic separate
- Ignore deprecation warnings: Address all deprecation warnings immediately
Pre-commit Checklist
✅ REQUIRED Before Every Commit:
# 1. Format code
npm run format
# 2. Lint and fix issues
npm run lint:fix
# 3. Type check
npm run typecheck
# 4. Run all tests
npm run test
# 5. Check coverage
npm run test:coverage
# 6. Build verification
npm run build
Git Commit Standards
# Use conventional commit format
feat: add new tool for Gemini CLI client status
fix: resolve session cleanup memory leak
docs: update MCP protocol documentation
test: add integration tests for state tracker
refactor: extract common client validation logic
Code Review Guidelines
✅ REVIEW CHECKLIST:
- Type Safety: All types properly defined and used
- Error Handling: Proper try-catch blocks and error emission
- Logging: Appropriate use of Logger instead of console
- Testing: Adequate test coverage for new functionality
- MCP Compliance: Tools and resources follow MCP protocol
- Documentation: Code is self-documenting with clear comments
- Performance: No obvious performance bottlenecks
- Security: No sensitive data exposure in logs
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.
- 2mo ago First seen · 322 lines · 0 tokens per session scan A c1f1fea8e5b6
07-development-workflow is a cursor rule published in the GitHub repository gargoyle92/agentify-mcp (1 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,171 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
vue-typescript-patterns
A set of coding rules for Vue 3 projects using TypeScript, a language that adds type checking to JavaScript. It covers component structure, file locations, TypeScript usage, and Pinia, a library for shared application state.
nextjs-typescript-app-cursorrules-prompt-file
Cursor rules for Next.js development with TypeScript integration.
ts
A set of TypeScript coding rules covering types, naming, file organization, error handling, and strict type checking. TypeScript is JavaScript with checks that help catch many mistakes before the program runs.
typescript-security
A secret scanner owns hardcoded keys. Read secrets from the environment and fail startup when a required one is missing.
general-rule
Cursor rule "general-rule" from vinhnx/vtchat, covering development guidelines, tech stack & project overview, package management, code style and ui/ux design principles.
naming-conventions-rule
A small set of naming rules for TypeScript, Node.js, and Next.js projects. It defines how directories and React components should be named and exported.