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 Eilodon/DPS-Superskills-MCP --skill pattern-globalizegit clone --depth 1 https://github.com/Eilodon/DPS-Superskills-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/skills/eilodon/dps-superskills-mcp/pattern-globalize)<a href="https://agentmods.dev/skills/eilodon/dps-superskills-mcp/pattern-globalize"><img src="https://agentmods.dev/badge/skills/eilodon/dps-superskills-mcp/pattern-globalize.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.00032 | $0.01713 |
| Opus 5 | $0.00016 | $0.00856 |
| Sonnet 5 | $0.00006 | $0.00343 |
| Haiku 4.5 | $0.00003 | $0.00171 |
Grade A, and why
pattern-globalize 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 6d 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 — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pattern-Globalize — One Bug Found = Grep Globally
Register: TECHNIQUE Goal: Eliminate the bug class, not just the instance. One confirmed fix triggers a search for siblings. Constraints: Always runs after confirmed fix. In SUBAGENT context: report-only, no fixes outside task scope. Adapt: grep strategy, fix approach, and debt documentation to codebase size and context.
Schema: PATTERN-DEBT entries follow shared/pattern-debt-schema.md.
All entries stored in docs/superskills/pattern-debt.md.
Execution Context — Declare First
EXECUTION_CONTEXT: STANDALONE | SUBAGENT
STANDALONE — called directly: Goal: fix the bug class globally, not just the instance. Constraints: fix top 3 highest-risk instances now; write PATTERN-DEBT for remainder.
SUBAGENT — called from inside subagent-driven-development or executing-plans:
Goal: record that a bug class exists for future remediation.
Constraints: write PATTERN-DEBT ONLY — do not fix anything outside current task scope.
(VHEATM Trust Anchor #1: "Read-only by default. Recommends, never self-executes.")
Idempotency Check
grep -c "PATTERN-DEBT-<slug>" docs/superskills/pattern-debt.md 2>/dev/null
# Count ≥ 1 → update existing entry, do not create duplicate
Step 1 — Extract the structural pattern
Goal: name the class of bug, not the instance.
❌ "null check missing on line 47" (instance)
✅ "return value used without null check" (class)
❌ "forgot await on line 82" (instance)
✅ "async return value consumed synchronously" (class)
Generate a slug: lowercase, hyphenated. e.g. async-no-await, missing-null-guard.
Step 2 — Grep globally
Goal: know the scope of the problem.
grep -rn "<structural pattern>" . --include="*.py" --include="*.ts" --include="*.js"
# Record exact command — it becomes the grep_cmd in PATTERN-DEBT schema
Step 3 — Branch on count
≤ 20 results (STANDALONE):
- Fix all instances in same commit
- Fix Anchor for each:
<file>:<line> — <description> - Re-read each changed file section after fix
- Commit:
fix: <pattern-slug> globally (N instances)
What ships with it
1 file 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.
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.
- 6d ago First seen · 179 lines · 32 tokens per session scan A 1a53281d372d
pattern-globalize is a skill published in the GitHub repository Eilodon/DPS-Superskills-MCP (0 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 32 tokens to every session and 1,713 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.