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/runbooksgit 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/runbooks)<a href="https://agentmods.dev/rules/sfc-gh-cconner/support-rules-mcp/runbooks"><img src="https://agentmods.dev/badge/rules/sfc-gh-cconner/support-rules-mcp/runbooks.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.1 | $0.02070 | $0.02070 |
| Opus 5 | $0.01035 | $0.01035 |
| Sonnet 5 | $0.00414 | $0.00414 |
| Haiku 4.5 | $0.00207 | $0.00207 |
Grade A, and why
runbooks 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 — 372 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Runbook Development Standards
PURPOSE: Standards for writing and maintaining troubleshooting runbooks with clear procedures and reproducibility.
📋 Runbook Structure
Every runbook must include these sections:
1. Purpose and Scope
# {Feature/Component} Troubleshooting Runbook
## Purpose
Clear statement of what this runbook helps troubleshoot
## Scope
- What issues this covers
- What issues this does NOT cover
- When to use this runbook
2. Preconditions
## Preconditions
### Required Access
- Role: SUPPORT_ENGINEER (or specific role)
- Warehouse: SUPPORT_ENG_POWER
- Database: SNOWHOUSE_IMPORT
### Required Tools
- Snow CLI installed and configured
- Snowhouse connection configured
- GitHub MCP access (optional, for source code review)
### Required Information
- Account locator and deployment
- Time window of the issue
- Error message or symptom
- Request ID, query ID, or session ID (if available)
3. Step-by-Step Procedure
## Investigation Procedure
### Step 1: Identify Account and Deployment
**Purpose**: Determine which deployment to query
**Command**:
```bash
snow sql --query "
SELECT account_name, account_locator, deployment, region, cloud
FROM temp.support_sp_dev.accounts
WHERE name ILIKE '%{ACCOUNT}%' OR locator ILIKE '%{ACCOUNT}%'
" --format=JSON --connection snowhouse
Expected Output:
[{
"account_name": "CUSTOMER_ACCOUNT",
"account_locator": "AB12345",
"deployment": "prod3",
"region": "us-west-2",
"cloud": "aws"
}]
Next Steps:
- If found: Note deployment and account_id, proceed to Step 2
- If not found: Verify account locator spelling, check alternate deployments
### 4. Verification
```markdown
## Verification
### Success Indicators
- [ ] Root cause identified
- [ ] Error reproduced or explained
- [ ] Solution tested and confirmed
- [ ] Customer can implement fix
### Validation Queries
```bash
# Verify fix was applied
snow sql --query "SHOW PARAMETERS LIKE 'CLIENT_SESSION_KEEP_ALIVE' IN ACCOUNT" --format=JSON --connection snowhouse
Expected: Parameter value matches recommended setting
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 · 372 lines · 2,070 tokens per session scan A 4216120e2053
runbooks is a cursor rule published in the GitHub repository sfc-gh-cconner/support-rules-mcp (0 stars, last pushed 11mo ago), licensed Apache-2.0. It adds 2,070 tokens to every session, about $0.0103 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
error-handling-and-validation
在所有代码中优先考虑错误处理和边缘情况。定义如何管理错误、处理前置条件和实现日志记录。.
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.
workflow-level1
Streamlined workflow for Level 1 Quick Bug Fix tasks.
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.
5-bug-finder
APPLY WHEN investigating a bug.