opencode-skills-collection 4.0.48 → 4.0.49

package/bundled-skills/lovable-cleanup/SKILL.md

@@ -1,13 +1,15 @@
 ---
 name: lovable-cleanup
-description: "Audits and strips Lovable scaffolding from Vite + React projects — removes lovable-tagger, swaps placeholder assets, prunes unused Radix deps, and cleans generated docs so the codebase ships as yours."
+description: "Audits and strips Lovable scaffolding from Vite + React projects — removes lovable-tagger, swaps placeholder assets, prunes unused Radix deps, cleans generated docs, and neutralizes stale favicon/CDN caching so the codebase ships as yours."
 risk: safe
 source: community
 source_repo: whoisabhishekadhikari/lovable-cleanup
 source_type: community
 author: whoisabhishekadhikari
 date_added: "2026-06-13"
-tags: [lovable, cleanup, vite, react, shadcn, devtools]
+date_updated: "2026-08-31"
+version: "2.0.0"
+tags: [lovable, cleanup, vite, react, shadcn, devtools, vercel, favicon]
 tools: [claude, cursor, codex, antigravity, gemini-cli]
 ---
 
@@ -23,7 +25,7 @@ tools: [claude, cursor, codex, antigravity, gemini-cli]
 Lovable (lovable.dev) bootstraps Vite + React + shadcn/ui projects with its own tagger
 dependency, branding, placeholder assets, and generated markdown docs baked in. Most
 developers export from Lovable and want a clean, ownable codebase before shipping or
-open-sourcing. This skill covers all 14 areas where Lovable leaves fingerprints.
+open-sourcing. This skill covers all 15 areas where Lovable leaves fingerprints.
 
 ---
 
@@ -75,6 +77,8 @@ shadcn components via the `asChild` prop.
 6. Environment & Git (Areas 9 & 12) — security sweep
 7. SEO / deploy (Area 11) — usually a no-op; confirm and move on
 8. Unused deps (Area 13) — safe to defer until after ship if on a deadline
+9. Favicon / CDN cache (Area 15) — do ASAP after assets are swapped; browser
+   or CDN caching can keep the old icon visible, so verify the live response
 
 ---
 
@@ -137,7 +141,7 @@ Replace these files (keep filenames, swap content):
 
 | File | Action |
 |---|---|
-| `favicon.ico` | Replace with real icon |
+| `favicon.ico` | Overwrite with real icon — do NOT just delete, see Area 15 |
 | `favicon.png` | Replace with real icon |
 | `og-image.png` / `logo.png` | Replace with real brand assets |
 | `placeholder.svg` | Usually unused — safe to delete |
@@ -292,6 +296,17 @@ grep -in "lovable" components.json eslint.config.js
 
 ---
 
+### Area 15 · Favicon removal & stale CDN caches (Vercel)
+
+Lovable ships a default `favicon.ico` that browsers auto-request from site root
+and that can remain visible after cleanup through browser or CDN caching. Handle
+the four steps — replace the path, link all icon flavours, keep unversioned icon
+URLs revalidatable, and verify after deploy — then purge the confirmed Vercel
+project cache only if the live response stays stale. Full commands/JSON live in
+[references/favicon-vercel-cleanup.md](references/favicon-vercel-cleanup.md).
+
+---
+
 ## Master Scan Command
 
 <!-- security-allowlist: recursive grep across project directory, read-only, no network -->
@@ -342,6 +357,9 @@ Agent:
 - ✅ **Do:** Run dep removal (Areas 2 & 7) before touching source files
 - ✅ **Do:** Skim Lovable-generated docs before deleting — may contain useful arch notes
 - ✅ **Do:** Verify `npm run build` passes after every batch of changes
+- ✅ **Do:** Replace favicons at the existing paths (Area 15), then verify the
+  live response and purge only the confirmed project if it remains stale
+- ✅ **Do:** Deploy replacement favicon content and cache headers in the same commit
 - ✅ **Do:** Replace OG image before launch — it directly affects social sharing previews
 - ❌ **Don't:** Remove `@radix-ui/react-slot` — it's an indirect dep of most shadcn components
 - ❌ **Don't:** Leave empty env vars like `LOVABLE_PROJECT_ID=` — delete the whole line
@@ -350,8 +368,8 @@ Agent:
 
 ## Limitations
 
-- This skill does not create or source brand assets (favicons, OG images) — it only flags
-  what needs replacing. The user must supply real assets.
+- This skill does not create or source real brand assets (favicons, OG images). Area 15
+  generates a transparent placeholder ICO only — the user must supply genuine artwork.
 - Dep pruning (Area 13) is safe but not foolproof — some Radix packages are indirect deps
   not caught by a direct `grep`. Always verify with `npm run build`.
 - The skill does not modify `components.json` aliases automatically — it only scans and
@@ -380,6 +398,14 @@ the `from '@radix-ui/...'` import to find which component depends on it.
 **Solution:** Check for a `<Helmet>` or `<Head>` component in `src/App.tsx` or a layout
 wrapper — React-level title tags override `index.html` at runtime.
 
+### Problem: Old favicon still serving after deletion (Vercel)
+
+**Symptoms:** `curl -sI https://<domain>/favicon.ico` returns the old ETag with
+`x-vercel-cache: HIT` after the replacement deployment.
+**Solution:** Overwrite `public/favicon.ico` with replacement content (a transparent
+1×1 ICO if no real asset yet), verify the custom domain, then use the explicit
+Vercel CDN purge only if the response remains stale — see Area 15.
+
 ---
 
 ## Related Skills

package/bundled-skills/lovable-cleanup/references/favicon-vercel-cleanup.md

@@ -0,0 +1,106 @@
+# Favicon removal & stale CDN caches (Vercel)
+
+Lovable ships a default `favicon.ico`, and browsers auto-request it from site
+root even when `index.html` links a different icon. Browser and CDN layers can
+therefore keep showing the old icon after a replacement deployment. Treat the
+cleanup as both a file-path and cache-verification problem.
+
+## 1 · Overwrite in place, don't delete
+
+Prefer replacing the same path in the deployment instead of deleting it. The
+production URL then keeps returning a valid icon while the new bytes establish
+a new content identity; browsers that request `/favicon.ico` implicitly do not
+fall back to an old cached asset merely because the HTML link changed.
+
+If no real brand icon is ready, use the bundled helper to write a valid
+transparent 1×1 ICO. It resolves the physical project root, rejects a symlinked
+`public/` directory or favicon target, writes an exclusive same-directory
+temporary file with no-follow semantics where available, then atomically
+renames it into place.
+
+<!-- security-allowlist: writes a 70-byte ICO into the project's public/, local only -->
+```bash
+node "<skill-dir>/scripts/write-transparent-favicon.js" "$PWD"
+```
+
+## 2 · Link all icon flavours in `index.html`
+
+Browsers may request `/favicon.ico` even without a link, so keep that path and
+the modern/Apple entry points available:
+
+```html
+<link rel="icon" type="image/x-icon" href="/favicon.ico" />
+<link rel="icon" type="image/svg+xml" href="/favicon.svg" />
+<link rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon.png" />
+```
+
+`apple-touch-icon.png` must be a real PNG (recommended 180×180). A solid brand-
+colour square is an acceptable placeholder; flag it for later replacement.
+
+## 3 · Keep unversioned icon URLs revalidatable (`vercel.json`)
+
+Vercel documents `public, max-age=0, must-revalidate` as its default response
+policy and recommends long-lived `immutable` caching for content-hashed assets.
+The standard favicon entry points below are not content-hashed, so keep them
+revalidatable unless the HTML points at a versioned filename:
+
+- `/favicon.ico`, `/favicon.svg`, `/apple-touch-icon.png` →
+  `public, max-age=0, must-revalidate`
+- A content-hashed asset such as `/favicon-a1b2c3.svg` may use
+  `public, max-age=31536000, immutable`.
+
+```json
+{
+  "headers": [
+    {
+      "source": "/favicon.ico",
+      "headers": [{ "key": "Cache-Control", "value": "public, max-age=0, must-revalidate" }]
+    },
+    {
+      "source": "/favicon.svg",
+      "headers": [{ "key": "Cache-Control", "value": "public, max-age=0, must-revalidate" }]
+    },
+    {
+      "source": "/apple-touch-icon.png",
+      "headers": [{ "key": "Cache-Control", "value": "public, max-age=0, must-revalidate" }]
+    }
+  ]
+}
+```
+
+Never mark an unversioned icon URL `immutable`: it tells browsers not to
+revalidate for the max-age lifetime, so a replacement may not propagate for up
+to a year. Use `immutable` only on content-hashed URLs.
+
+## 4 · Verify after deploy
+
+<!-- security-allowlist: remote curl header check of own domain, read-only -->
+```bash
+curl -sI https://YOUR-DOMAIN/favicon.ico \
+  | grep -i "cache-control\|etag\|x-vercel-cache"
+```
+
+Expect the replacement ETag and `Cache-Control: public, max-age=0,
+must-revalidate` on the unversioned icon URLs.
+
+If the confirmed production domain still serves the old edge response, verify
+the linked Vercel project and team first, ask for explicit approval, then purge
+that project's CDN cache:
+
+<!-- security-allowlist: explicit remote cache purge for the confirmed Vercel project; requires user approval -->
+```bash
+vercel cache purge --type cdn
+```
+
+Re-run the header check after the purge. Do not purge a project inferred only
+from the current directory or a preview URL.
+
+**Gotcha — the staging URL:** a `*.vercel.app` preview may be SSO-protected
+(`_vercel_sso_nonce` 302) and wrap deploys in a provider frame that injects
+platform branding. Always verify icons on the real custom domain.
+
+## Official references
+
+- [Vercel Cache-Control headers](https://vercel.com/docs/caching/cache-control-headers)
+- [Vercel CDN cache](https://vercel.com/docs/caching/cdn-cache)
+- [Vercel cache purge CLI](https://vercel.com/docs/cli/cache)

package/bundled-skills/lovable-cleanup/scripts/write-transparent-favicon.js

@@ -0,0 +1,88 @@
+#!/usr/bin/env node
+"use strict";
+
+const crypto = require("node:crypto");
+const fs = require("node:fs");
+const path = require("node:path");
+
+function fail(message) {
+  throw new Error(`Refusing favicon write: ${message}`);
+}
+
+function existingStat(target) {
+  try {
+    return fs.lstatSync(target);
+  } catch (error) {
+    if (error && error.code === "ENOENT") return null;
+    throw error;
+  }
+}
+
+function transparentIco() {
+  const bytes = Buffer.alloc(6 + 16 + 40 + 8);
+  bytes.writeUInt16LE(1, 2);
+  bytes.writeUInt16LE(1, 4);
+  bytes.writeUInt8(1, 6);
+  bytes.writeUInt8(1, 7);
+  bytes.writeUInt16LE(1, 10);
+  bytes.writeUInt16LE(32, 12);
+  bytes.writeUInt32LE(40 + 8, 14);
+  bytes.writeUInt32LE(22, 18);
+  bytes.writeUInt32LE(40, 22);
+  bytes.writeInt32LE(1, 26);
+  bytes.writeInt32LE(2, 30);
+  bytes.writeUInt16LE(1, 34);
+  bytes.writeUInt16LE(32, 36);
+  bytes.writeUInt32LE(0, 38);
+  bytes.writeUInt32LE(8, 42);
+  return bytes;
+}
+
+function main() {
+  const requestedRoot = path.resolve(process.argv[2] || process.cwd());
+  const projectRoot = fs.realpathSync(requestedRoot);
+  const publicDirectory = path.join(projectRoot, "public");
+  const publicStat = fs.lstatSync(publicDirectory);
+  if (publicStat.isSymbolicLink() || !publicStat.isDirectory()) {
+    fail("public/ must be a real directory, not a symlink or special file");
+  }
+  if (fs.realpathSync(publicDirectory) !== publicDirectory) {
+    fail("public/ resolves outside the physical project path");
+  }
+
+  const target = path.join(publicDirectory, "favicon.ico");
+  const targetStat = existingStat(target);
+  if (targetStat && targetStat.isSymbolicLink()) {
+    fail("public/favicon.ico is a symbolic link");
+  }
+  if (targetStat && !targetStat.isFile()) {
+    fail("public/favicon.ico is not a regular file");
+  }
+
+  const temporary = path.join(
+    publicDirectory,
+    `.favicon.ico.${process.pid}.${crypto.randomBytes(8).toString("hex")}.tmp`,
+  );
+  const flags =
+    fs.constants.O_WRONLY |
+    fs.constants.O_CREAT |
+    fs.constants.O_EXCL |
+    (fs.constants.O_NOFOLLOW || 0);
+  let descriptor;
+  try {
+    descriptor = fs.openSync(temporary, flags, 0o600);
+    fs.writeFileSync(descriptor, transparentIco());
+    fs.fsyncSync(descriptor);
+    fs.fchmodSync(descriptor, 0o644);
+    fs.closeSync(descriptor);
+    descriptor = undefined;
+    fs.renameSync(temporary, target);
+  } finally {
+    if (descriptor !== undefined) fs.closeSync(descriptor);
+    const temporaryStat = existingStat(temporary);
+    if (temporaryStat && temporaryStat.isFile()) fs.unlinkSync(temporary);
+  }
+  process.stdout.write(`Wrote ${target}\n`);
+}
+
+main();

package/bundled-skills/multi-source-search/scripts/validate_report.py

@@ -21,6 +21,11 @@ def canonical_url(value):
     """Return a conservative identity for an HTTP(S) URL, or None if invalid."""
     if not nonempty(value):
         return None
+    if any(
+        character.isspace() or ord(character) < 0x20 or ord(character) == 0x7F
+        for character in value
+    ):
+        return None
     try:
         parsed = urlsplit(value)
         hostname = parsed.hostname

package/bundled-skills/omp-delegate/SKILL.md

@@ -2,7 +2,7 @@
 name: omp-delegate
 description: Delegate coding tasks to Oh My Pi (`omp`) only when the user explicitly
   requests it, while the orchestrator retains review and landing responsibility.
-risk: safe
+risk: critical
 category: agent-orchestration
 source: https://github.com/amElnagdy/delegate-skills
 source_repo: amElnagdy/delegate-skills

package/bundled-skills/opencode-delegate/SKILL.md

@@ -2,7 +2,7 @@
 name: opencode-delegate
 description: Delegate coding tasks to the OpenCode CLI only when the user explicitly
   requests it, while the orchestrator retains review and landing responsibility.
-risk: safe
+risk: critical
 category: agent-orchestration
 source: https://github.com/amElnagdy/delegate-skills
 source_repo: amElnagdy/delegate-skills

package/bundled-skills/pentest-tools/references/pentest-ai-agents-matrix.md

@@ -10,11 +10,14 @@
 
 ## 安装方式（外部可选）
 
-```bash
-curl -fsSL https://raw.githubusercontent.com/0xSteph/pentest-ai-agents/main/install.sh | bash  # security-allowlist: curl-pipe-bash
-```
-
-或者只参考其 prompt 模式，不实际安装。
+默认只参考其 prompt 模式，不安装外部代码。不得从可变的 `main` 分支
+下载并直接执行安装脚本，也不得把下载内容通过管道交给 shell。
+
+如果用户明确要求安装，先在仓库页面选择并记录一个完整的 40 位 commit
+SHA，在私有审查目录中下载该 commit 的完整源码，核对仓库身份、许可证、
+文件清单、安装脚本及其后续下载。只有在展示确切变更和命令并获得单独批准
+后，才可从已审查的本地副本执行；任一依赖仍指向分支、标签、`latest` 或未审查
+远程脚本时必须停止。
 
 ---
 

package/bundled-skills/pi-delegate/SKILL.md

@@ -2,7 +2,7 @@
 name: pi-delegate
 description: Delegate coding tasks to the Pi coding agent CLI (`pi`) only when the
   user explicitly requests it, while the orchestrator retains review and landing responsibility.
-risk: safe
+risk: critical
 category: agent-orchestration
 source: https://github.com/amElnagdy/delegate-skills
 source_repo: amElnagdy/delegate-skills

package/bundled-skills/prompt-caching/SKILL.md

@@ -34,7 +34,7 @@ Caching strategies for LLM prompts including Anthropic prompt caching, response
 ### Primary_tools
 
 - Anthropic Prompt Caching - Native prompt caching in Claude API
-- Redis - In-memory cache for responses
+- Redis - In-memory cache for responses (ioredis on servers; @upstash/redis over HTTP on serverless, see `upstash-redis`)
 - OpenAI Caching - Automatic caching in OpenAI API
 
 ## Patterns
@@ -91,6 +91,8 @@ import { createHash } from 'crypto';
 import Redis from 'ioredis';
 
 const redis = new Redis(process.env.REDIS_URL);
+// Serverless/edge alternative without a persistent connection:
+// import { Redis } from '@upstash/redis'; const redis = Redis.fromEnv();  // then use redis.set(key, value, { ex: ttl })
 
 class ResponseCache {
     private ttl = 3600;  // 1 hour default

package/bundled-skills/qoder-delegate/SKILL.md

@@ -2,7 +2,7 @@
 name: qoder-delegate
 description: Delegate coding tasks to the Qoder CLI (`qodercli`) only when the user
   explicitly requests it, while the orchestrator retains review and landing responsibility.
-risk: safe
+risk: critical
 category: agent-orchestration
 source: https://github.com/amElnagdy/delegate-skills
 source_repo: amElnagdy/delegate-skills

package/bundled-skills/screen-adverse-media/SKILL.md

@@ -0,0 +1,100 @@
+---
+name: screen-adverse-media
+description: Screen a person or organisation for adverse media coverage, PEP status, and sanctions exposure — corroboration-gated, returns "review" never "guilty". Use when the user asks to screen someone before onboarding, partnership, or investment; for AML/CTF flows; or for ongoing counterparty monitoring.
+category: document-verification
+risk: critical
+source: community
+source_repo: Sketchjar/stipple-agent-skills
+source_type: community
+date_added: "2026-08-31"
+author: Sketchjar
+tags: [document-verification, fact-checking, stipple, authenticity]
+tools: [claude, cursor, gemini, codex]
+license: "Apache-2.0"
+license_source: "https://github.com/Sketchjar/stipple-agent-skills/blob/main/LICENSE"
+---
+
+# Screen Adverse Media
+
+Screen a person or organisation for adverse media coverage, PEP (Politically Exposed Person) status, and sanctions exposure. Every hit is **corroboration-gated**: the screen returns "review", never "guilty", and "nothing found" is never a clean record. Uses the Stipple API (free anonymous tier).
+
+## When to use
+
+- AML/CTF onboarding (Tranche 2 reforms make this mandatory for more Australian businesses)
+- Vendor/supplier due diligence before signing
+- Investor or LP vetting
+- Ongoing counterparty monitoring (re-run periodically, compare warrant IDs)
+
+## Instructions
+
+1. **Get the target.** Name of the person or organisation. For document-based screening, a PDF/image of their ID or company extract can also be submitted.
+
+2. **Run the screen.**
+
+   Name-based (via MCP — the REST intake is document-based):
+   ```bash
+   # Via any MCP client pointed at https://www.stipple.sh/mcp:
+   # tool: screen_adverse_media
+   # args: {"name": "John Citizen", "entity_type": "person"}
+   ```
+
+   Document-based (REST — screens the person/org named in the uploaded document):
+   ```bash
+   curl -X POST https://www.stipple.sh/v1/adverse-media \
+     -F "file=@company-extract.pdf" \
+     -H "Authorization: Bearer $STIPPLE_API_KEY"
+   ```
+
+3. **Interpret the response.**
+
+   - `rating` — the overall screening result ("review", "clear", etc.)
+   - `hits[]` — adverse media articles: date, title, source, URL, summary
+   - `pep[]` — PEP signals (empty = none found)
+   - `sanctions[]` — sanctions list signals (empty = none found)
+
+4. **Report with the right framing.** Non-negotiable framing rules:
+
+   | Finding | Correct framing |
+   |---|---|
+   | Hits found | "Review recommended — see articles below" (never "guilty") |
+   | Nothing found | "No corroborated adverse media found — this is NOT a clean record; coverage is bounded by the source list" |
+   | PEP signal | "PEP status identified — enhanced due diligence may apply" |
+
+5. **Contextualize.** Every hit is corroborated across sources before inclusion — but the screen is the start of human review, not the end of it. Date-range and source-coverage limitations are real.
+
+## Output format
+
+```
+screening rating: review
+
+adverse media hits:
+  - [2025-11-02] Court action over unpaid supplier debts
+      source: The Age  https://...
+  - [2024-06-18] ASIC disqualification
+      source: ASIC media releases  https://...
+
+PEP signals: 0
+sanctions list signals: 0
+
+This screen returns "review", never "guilty" — every hit is corroboration-gated.
+```
+
+## Limitations and Safety
+
+- Screening processes personal data and potentially damaging allegations through a
+  hosted third party. Confirm a lawful purpose, obtain any required approval, send
+  only the minimum identifiers needed, and verify current retention, residency,
+  access, and deletion terms before transmission.
+- Name matches, PEP signals, sanctions hits, and media reports can be incomplete,
+  stale, misattributed, or false. Corroborate every consequential result with the
+  original source and authoritative registers; never publish an allegation as fact.
+- This is not a legal AML/CTF determination. A qualified human reviewer must resolve
+  identity ambiguity, document the reasoning, and provide an appropriate correction
+  or appeal path before rejecting or restricting a person or organization.
+
+## Notes
+
+- Costs 3 credits per screen; free weekly allowance applies
+- For AML flows, pair with `check-identity-pack` (identity) and `verify-document` (document genuineness)
+- "Nothing found" ≠ "clean record" — always state this in reports
+- Free key at https://www.stipple.sh for metering beyond the anonymous allowance