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 skills/soleimanmansouri/debug-bank/pattern-checknpx skills add soleimanmansouri/debug-bank --skill pattern-checkgit clone --depth 1 https://github.com/soleimanmansouri/debug-bankWhat 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.00039 | $0.00458 |
| Opus 5 | $0.00019 | $0.00229 |
| Sonnet 5 | $0.00008 | $0.00092 |
| Haiku 4.5 | $0.00004 | $0.00046 |
Grade A, and why
pattern-check 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 2d 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
Pattern Check — Quick Scan
You are performing a pattern check before debugging. This is Step 1 of the debug trajectory protocol.
Instructions
- Read the symptom/error description provided
- Scan each pattern (P01-P19+) in the pattern bank
- For each pattern, check: "Could this symptom be caused by this root cause type?"
- Report your findings
Output Format
If Match Found
PATTERN MATCH: P[XX] — [Pattern Name]
Confidence: HIGH / MEDIUM / LOW
Reasoning: [Why this pattern matches the symptom]
Suggested checks:
- [ ] [Check 1 from the pattern's check list]
- [ ] [Check 2]
- [ ] [Check 3]
If checks confirm, apply fix strategy from P[XX].
If No Match
NO PATTERN MATCH
Closest patterns considered:
- P[XX]: [Why it was close but doesn't match]
- P[XX]: [Why it was close but doesn't match]
Proceed to Step 2 (Reproduce) of the debug trajectory protocol.
If Multiple Matches
MULTIPLE PATTERN MATCHES (ranked by likelihood):
1. P[XX] — [Name] (CONFIDENCE: HIGH)
Reasoning: [Why]
2. P[XX] — [Name] (CONFIDENCE: MEDIUM)
Reasoning: [Why]
Start with the highest-confidence match. If its checks fail, try the next.
Speed Requirement
This check should take under 60 seconds. Do not investigate, reproduce, or attempt fixes during a pattern check. Only scan and report.
The value of this step is SPEED — a 30-second check that saves hours of re-investigation. If you spend more than 60 seconds, you're over-investigating.
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.
- 2d ago First seen · 69 lines · 39 tokens per session scan A 2522728ee3f0
pattern-check is a skill published in the GitHub repository soleimanmansouri/debug-bank (1 stars, last pushed 3mo ago), licensed MIT. It adds 39 tokens to every session and 458 once invoked, about $0.0002 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 skills, from other repositories
weave
Parallel strand orchestration — decompose a task into 3+ independently scoped strands, fan out real subagents (worktree-isolated when they write files), and coordinate through a session file and Insight Capsules. Use ONLY when the user explicitly invokes it by name or slash command.
coding-agents-farm
To orchestrate parallel coding-agent farms (Claude, Codex, Copilot, Gemini, etc.) on isolated git worktrees.
mcp-media-inbox-triage
Find media, partnership, and high-intent requests buried in a shared Gmail inbox, summarize the useful ones, and route them to the right owner through Zapier MCP.
mcp-sheet-cache-bridge
Keep Zapier Tables or another MCP-connected record store as the source of truth while Google Sheets-based tools read an event-driven cache tab.
customer-deck-builder
Build tailored customer-facing sales or customer success decks from approved account context and generate the presentation with Gamma through Zapier MCP.
premortem
First-principles premortem on a high-stakes plan: assume failure 6–18 months out, reconstruct causal death chains, surface hidden assumptions, deliver a revised reversibility-weighted plan. Use ONLY when the user explicitly invokes it by name or slash command.