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 ivegamsft/basecoat --skill failure-pattern-processgit clone --depth 1 https://github.com/ivegamsft/basecoatWrote 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/ivegamsft/basecoat/failure-pattern-process)<a href="https://agentmods.dev/skills/ivegamsft/basecoat/failure-pattern-process"><img src="https://agentmods.dev/badge/skills/ivegamsft/basecoat/failure-pattern-process/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/ivegamsft/basecoat/failure-pattern-process"><img src="https://agentmods.dev/badge/skills/ivegamsft/basecoat/failure-pattern-process.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.00071 | $0.00638 |
| Opus 5 | $0.00036 | $0.00319 |
| Sonnet 5 | $0.00014 | $0.00128 |
| Haiku 4.5 | $0.00007 | $0.00064 |
Grade A, and why
failure-pattern-process 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 today.
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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Failure Pattern Process Skill
Use this skill to execute a reusable, evidence-first failure-pattern process:
- Mine failure patterns
- Log raw findings without pruning
- Triage common versus repo-specific patterns
- Build a prioritized enhancement plan with early-detection gates
Process Contract Alignment
This skill is aligned to:
Canonical stage model:
queued -> mining -> raw_logged -> triaged -> planned -> completed
Failure transition:
* -> blocked
Artifact Pack
Required outputs:
A1-source-indexA2-pattern-candidatesB1-raw-findings-log(append-only, no pruning)C1-triage-matrixC2-classification-rationaleD1-enhancement-backlogD2-early-detection-gatesrun-summary
Practical Templates
| Template | Purpose |
|---|---|
templates/source-index-template.md |
Capture evidence sources with provenance and timestamps |
templates/raw-findings-log-template.md |
Append-only raw findings record (duplicates retained) |
templates/triage-matrix-template.md |
Classify findings as common, repo-specific, or unknown with rationale |
templates/enhancement-backlog-template.md |
Prioritized enhancement items with validation methods |
templates/early-detection-gates-template.md |
Define detection triggers, owners, and actions |
templates/run-summary-template.md |
Summarize stage transitions, gate outcomes, and handoff |
Checklists
| Checklist | Purpose |
|---|---|
checklists/gate-validation-checklist.md |
Verify Gate 1 through Gate 4 completion criteria |
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- checklists/gate-validation-checklist.md 1.1 KB
- eval.yaml 890 B
- templates/early-detection-gates-template.md 261 B
- templates/enhancement-backlog-template.md 294 B
- templates/raw-findings-log-template.md 334 B
- templates/run-summary-template.md 516 B
- templates/source-index-template.md 203 B
- templates/triage-matrix-template.md 492 B
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.
- today First seen · 76 lines · 71 tokens per session scan A f6b7648b4c33
failure-pattern-process is a skill published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed today), licensed MIT. It adds 71 tokens to every session and 638 once invoked, about $0.0004 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-09-08.
Other skills, from other repositories
skill-incident-response
Organiza resposta a incidentes técnicos com contenção, evidência, comunicação, recuperação, timeline e postmortem sem culpa.
kubernetes
Kubernetes operations playbook for deploying services: core objects, probes, resource sizing, safe rollouts, and fast kubectl debugging.
epistemic-graph-troubleshooting
Diagnose and recover a live epistemic-graph engine (the AI-native database): engine down / socket refused, host-daemon crash-loop, circuit-breaker open, backend-type errors, zombie containers, duplicate Swarm tasks, slow first boot. Use when the KG is unreachable, ingestion stalls, go tools error, or a deploy left the…
apply-fishbone-diagram
Use when investigating the root cause of a quality defect, recurring process failure, or operational problem — to map all contributing causes across multiple categories simultaneously before selecting which cause to address.
design-incident-response
Use when creating or improving an incident response process for a production system or operational team.
runbook-knowledge
Provides knowledge about operational runbooks, incident response, and troubleshooting procedures.