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/sfc-gh-cconner/support-rules-mcp/troubleshootinggit clone --depth 1 https://github.com/sfc-gh-cconner/support-rules-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/sfc-gh-cconner/support-rules-mcp/troubleshooting)<a href="https://agentmods.dev/rules/sfc-gh-cconner/support-rules-mcp/troubleshooting"><img src="https://agentmods.dev/badge/rules/sfc-gh-cconner/support-rules-mcp/troubleshooting.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.00439 | $0.00439 |
| Opus 5 | $0.00219 | $0.00219 |
| Sonnet 5 | $0.00088 | $0.00088 |
| Haiku 4.5 | $0.00044 | $0.00044 |
Grade A, and why
troubleshooting 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 4d 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.
What it actually says
Troubleshooting Workflow - Complete Ruleset
PURPOSE: Complete investigation workflow combining GitHub MCP, Snowflake Docs, Snowhouse querying, and DPO mappings for systematic troubleshooting.
Meta-Rule: This combines all core Snowflake knowledge with troubleshooting-specific guidance.
📦 Included Rules
This meta-rule includes:
- ✅ Core: Source code access (GitHub MCP)
- ✅ Core: Documentation access (Snowflake Docs MCP)
- ✅ Core: DPO to table mappings
- ✅ Core: Snowhouse querying patterns
- ✅ Workflow: Troubleshooting investigation guide
@include core/01-github-mcp.mdc @include core/02-docs-mcp.mdc @include core/04-dpo-mappings.mdc @include core/05-snowhouse-querying.mdc @include workflows/troubleshooting.mdc
🎯 Quick Reference
Investigation Flow
- Documentation → Understand expected behavior
- Snowhouse → Query for data and context
- Source Code → Find implementation details
- Logs → Analyze detailed execution
- Root Cause → Synthesize findings
Key Principles
- Always filter by
account_id - Start with
job_etl_vfor timestamps - Check if objects are stage-backed (image repos, git repos)
- Use GitHub MCP for source code
- Use Snowflake Docs MCP for official documentation
- Correlate across all data sources
Common Objects
| Object | Table | Filter |
|---|---|---|
| Image Repo | stage_etl_v |
stage_type = 'IMAGE_REPOSITORY' |
| Git Repo | stage_etl_v |
stage_type = 'GIT_REPOSITORY' |
| Query | job_etl_v |
start_time range |
| Session | session_etl_v |
session_id |
| Warehouse | warehouse_etl_v |
warehouse_name |
Usage: Load this rule in your troubleshooting project's .cursorrules or via MCP.
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.
- 4d ago First seen · 57 lines · 439 tokens per session scan A 23c734ab8c04
troubleshooting is a cursor rule published in the GitHub repository sfc-gh-cconner/support-rules-mcp (0 stars, last pushed 10mo ago), licensed Apache-2.0. It adds 439 tokens to every session, about $0.0022 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-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.