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 skills add soleimanmansouri/debug-bank --skill pattern-checkgit clone --depth 1 https://github.com/soleimanmansouri/debug-bankWrote 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/skills/soleimanmansouri/debug-bank/pattern-check)<a href="https://agentmods.dev/skills/soleimanmansouri/debug-bank/pattern-check"><img src="https://agentmods.dev/badge/skills/soleimanmansouri/debug-bank/pattern-check/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/skills/soleimanmansouri/debug-bank/pattern-check"><img src="https://agentmods.dev/badge/skills/soleimanmansouri/debug-bank/pattern-check.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.00039 | $0.00458 |
| Opus 5.5 | $0.00016 | $0.00183 |
| Sonnet 5.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 1mo 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.
- 1mo 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 5mo ago), licensed MIT. It adds 39 tokens to every session and 458 once invoked, about $0.0002 per session on Opus 5.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
code-context
How to answer codebase questions with the code-context MCP tools (search, sql, reindex): ranked hybrid keyword+semantic search, relevance-ranked SQL aggregation over the index, and index lifecycle. Use when a question spans many files ("how does X work", "where is Y handled"), when ranking or counting code by topic…
support-ticket-triage
Triage support tickets by pulling helpdesk context, searching issue trackers and knowledge bases in parallel, classifying the issue, and giving reps a recommended next action.
recovery
Handle blocked verification outcomes.
tapp
Use Tapp to see, drive, explore, and verify real application surfaces on iOS simulators, Android emulators/devices, or the web. Use when a user asks an agent to test an app or UI change, find bugs, inspect or screenshot a screen, exercise a journey, create a replayable flow, gather release evidence, run the…
fix-issue
Fix a GitHub issue end-to-end. Use when given an issue number to fix, implementing bug fixes, or addressing reported problems.
less-is-more
Reduction-first coding for every change, whether building, fixing, refactoring, or cleaning up. Delete, merge, or replace before adding, so the project ends up smaller and simpler without losing anything the app needs, in code and in the text around it. Matters most for cleanups, refactors, and larger changes.