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/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/04-error-handling-logging)<a href="https://agentmods.dev/rules/gargoyle92/agentify-mcp/04-error-handling-logging"><img src="https://agentmods.dev/badge/rules/gargoyle92/agentify-mcp/04-error-handling-logging/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/04-error-handling-logging"><img src="https://agentmods.dev/badge/rules/gargoyle92/agentify-mcp/04-error-handling-logging.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.01644 |
| Opus 5.5 | $0.00000 | $0.00658 |
| Sonnet 5.5 | $0.00000 | $0.00329 |
| Haiku 4.5 | $0.00000 | $0.00164 |
Grade A, and why
04-error-handling-logging 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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
04-Error-Handling-Logging
Logging System Architecture
The project uses a centralized logging system implemented in logger.ts with configurable log levels.
Logger Integration
All classes receive a Logger instance via dependency injection and must use it for all logging operations.
CRITICAL LOGGING RULES - MUST FOLLOW
✅ ALWAYS DO:
- Use Logger instance: Never use console.log - always use the injected Logger
- Appropriate log levels: Use error/warn/info/debug according to severity
- Structured logging: Include relevant context (clientId, operation, etc.)
- Log before errors: Log context before throwing exceptions
- Event emission: Emit events for error conditions to enable monitoring
❌ NEVER DO:
- Direct console output: Never use console.log, console.error, etc.
- Silent failures: Never catch errors without logging them
- Expose sensitive data: Don't log passwords, tokens, or sensitive information
- Generic error messages: Avoid vague messages like "Error occurred"
- Log flooding: Don't log inside tight loops without throttling
Error Handling Patterns
✅ PROPER Error Handling:
// Class with proper logging setup
export class SessionManager extends EventEmitter {
constructor(private logger: Logger) {
super();
}
public registerClient(client: AgentClient): void {
try {
this.logger.info(`Registering client: ${client.id} (${client.type})`);
this.clients.set(client.id, client);
this.emit('clientConnected', client);
this.logger.info(`Client registered successfully: ${client.id}`);
} catch (error: unknown) {
this.logger.error(`Failed to register client ${client.id}:`, error);
this.emit('error', { operation: 'registerClient', clientId: client.id, error });
throw error;
}
}
}
❌ INCORRECT Patterns:
// Bad - no logging
public registerClient(client: AgentClient): void {
this.clients.set(client.id, client); // Silent operation
}
// Bad - console usage
public registerClient(client: AgentClient): void {
console.log('Registering client:', client.id); // Wrong logging method
}
// Bad - swallowing errors
public registerClient(client: AgentClient): void {
try {
this.clients.set(client.id, client);
} catch (error) {
// Silent failure - very bad!
}
}
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 · 222 lines · 0 tokens per session scan A 87f10d4b8d34
04-error-handling-logging 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 1,644 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
error-handling-and-validation
A code-quality guide for handling errors, invalid inputs, edge cases, preconditions, logging, and user-friendly error messages.
css-render-blocking-diagnosis
Cursor rule "css-render-blocking-diagnosis" from adobecom/da-express-milo, covering css render-blocking diagnosis & resolution, critical learning from 98 pagespeed achievement, primary diagnostic protocol, step 1: css blocking symptom recognition and step 2: css loading sequence audit.
modus-checkbox-value-inversion-react-short
Critical bug fix for ModusWcCheckbox value property inversion.
javascript-expert-performance
Profile first. Measure before and after. Never optimize without data.
kiss-ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
5-bug-finder
APPLY WHEN investigating a bug.