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/gargoyle92/agentify-mcp/01-architecture-overviewgit clone --depth 1 https://github.com/gargoyle92/agentify-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/gargoyle92/agentify-mcp/01-architecture-overview)<a href="https://agentmods.dev/rules/gargoyle92/agentify-mcp/01-architecture-overview"><img src="https://agentmods.dev/badge/rules/gargoyle92/agentify-mcp/01-architecture-overview.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.00606 | $0.00606 |
| Opus 5 | $0.00303 | $0.00303 |
| Sonnet 5 | $0.00121 | $0.00121 |
| Haiku 4.5 | $0.00061 | $0.00061 |
Grade A, and why
01-architecture-overview 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 3d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
01-Architecture-Overview
Project Structure
The main entry point is index.ts, which initializes the AgentifyMCPServer.
Core Components Architecture
src/
├── server/ # Core server modules
│ ├── agentify-mcp.ts # Main MCP server implementation
│ ├── session-manager.ts # Client session management
│ └── state-tracker.ts # File system & state monitoring
├── tools/ # MCP tool implementations
│ └── tool-registry.ts # Tool registration & execution
├── resources/ # MCP resource implementations
│ └── resource-manager.ts # Resource management & serving
├── types/ # TypeScript type definitions
│ └── index.ts # Central type exports
└── utils/ # Utility modules
├── logger.ts # Logging system
└── notification-manager.ts # Alert & notification system
CRITICAL RULES - MUST FOLLOW
✅ ALWAYS DO:
- Import from central types: Always import types from types/index.ts
- Use dependency injection: Pass Logger instance to all modules that need logging
- Follow EventEmitter pattern: All core classes extend EventEmitter for loose coupling
- Implement proper error handling: Use try-catch blocks and emit error events
- Validate client types: Always check AgentClientType before executing client-specific logic
❌ NEVER DO:
- Direct console.log: Always use the Logger instance - never use console.log/error directly
- Hardcode client detection: Use the detectClientType method in AgentifyMCPServer
- Skip error handling: Every async operation must have proper error handling
- Bypass session manager: Always use SessionManager for client operations
- Create circular dependencies: Keep clear separation between server, tools, and resources
Design Patterns Applied
- Observer Pattern: EventEmitter-based communication
- Registry Pattern: Tool and Resource registries for extensibility
- Dependency Injection: Logger and manager instances passed to constructors
- Strategy Pattern: Client-type specific tool and resource handling
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.
- 3d ago First seen · 56 lines · 606 tokens per session scan A fc0aca8c49bb
01-architecture-overview is a cursor rule published in the GitHub repository gargoyle92/agentify-mcp (1 stars, last pushed 1y ago), licensed MIT. It adds 606 tokens to every session, about $0.0030 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-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-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.
family-instance-domain-actions
Family instance domain action implementation patterns.