菜单
Multi-layer virus scanning for Aminet packages. Signature-based detection, heuristic hunk analysis, boot block scanning, quarantine management, and scan orchestration. Use when scanning packages, checking virus status, or managing quarantine.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/Tibsfox/gsd-skill-creator --skill aminet-scanner命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Use the moment a request is underspecified and you are about to act on an ASSUMED goal. Enumerate the candidate goals the request could mean, project the action or artifact each one implies, and check whether they diverge: if two or more plausible goals lead to materially different actions or artifacts, ask exactly ONE targeted clarifying question; otherwise proceed on the most-likely goal and state the assumption in one line. Clarification is an evidence-producing action, not a delay — but one question, never an interrogation. Distinct from gsd-spec-phase (GSD-phase-bound, emits a heavy SPEC.md) and intent-router (fetch strategy, not goal disambiguation). Backed by agent goal-state inference (arxiv 2606.16813v1). Triggers on acting under an assumed goal when the request admits more than one materially different reading.
Use at write time to vector/embedding memory — Grove content-addressed insertion, chroma/pgvector upserts, memory-consolidation promoting session traces to MEMORY.md, or embedding externally-ingested content. Scores each candidate record against a fixed panel of sentinel queries and quarantines any record that would become the nearest neighbor of too many unrelated queries — a hub — whether from adversarial poisoning or accidental over-generality. This is the memory-record-side sibling of skill-injection-guardian (file-side) and the write-side complement of memory-use-warrant (read-side). Quarantine, never silently drop; a human reviews. Backed by the admission-time hubness gate (arxiv 2606.19692v1). Triggers on inserting into vector memory, consolidating memory, and embedding stranger content.
Run this appropriateness check the moment you are about to integrate a retrieved long-term memory — a Grove content-addressed hit, a chroma/pgvector neighbour, a memory-consolidation digest, or a MEMORY.md line — into a response, especially anything touching private origins, Fox Companies IP, credentials, or Center Camp / consent-governed content. It answers a question intent-router never asks: not WHAT to fetch or HOW, but WHETHER a correctly-retrieved item should reach output. Relevance is not appropriateness — a perfect similarity match can still be a boundary violation. Default is FAIL-CLOSED: if in-context authorization is uncertain, the memory may inform behaviour but must not be surfaced. Backed by RBI-Eval (arxiv 2606.06055v1). Triggers on surfacing recalled sensitive memory into a response.
基于 SOC 职业分类
正在显示 SKILL.md
| name | aminet-scanner |
| description | Multi-layer virus scanning for Aminet packages. Signature-based detection, heuristic hunk analysis, boot block scanning, quarantine management, and scan orchestration. Use when scanning packages, checking virus status, or managing quarantine. |
| metadata | {"extensions":{"gsd-skill-creator":{"triggers":{"intents":["scan.*aminet|aminet.*scan","virus.*check|check.*virus","quarantine","heuristic.*scan"],"files":["src/aminet/signature-scanner.ts","src/aminet/heuristic-scanner.ts","src/aminet/scan-orchestrator.ts","src/aminet/quarantine.ts","src/aminet/signature-db.ts"],"contexts":["aminet virus scanning","package security"],"threshold":0.7},"token_budget":"1.5%","version":1,"enabled":true,"plan_origin":"242-aminet-integration","phase_origin":"242"}}} |
Provides multi-layer virus scanning for Aminet packages targeting the Amiga malware landscape. Combines signature-based detection (52 virus signatures in ClamAV .ndb format), heuristic analysis of hunk structures and boot blocks, quarantine management with atomic file isolation, and a scan orchestrator that coordinates all layers into unified scan reports with configurable depth levels.
| Module | Purpose |
|---|---|
src/aminet/signature-db.ts | 52 virus signatures in 3 JSON files with last-wins deduplication |
src/aminet/signature-scanner.ts | Context-aware hex pattern matching with wildcard bitmasks |
src/aminet/heuristic-scanner.ts | 8 heuristic rules for hunk and boot block analysis |
src/aminet/quarantine.ts | Atomic file isolation with metadata sidecars and restore |
src/aminet/scan-orchestrator.ts | Coordinates all scan layers into unified ScanReport |
src/aminet/emulated-scanner.ts | FS-UAE + CheckX emulated scanning with timeout control |
Quick signature scan:
import { scanBuffer } from './signature-scanner.js';
const result = scanBuffer(fileBuffer, { context: 'hunk' });
// result.verdict: 'clean' | 'suspicious' | 'infected'
// result.findings: matched signature details
Full orchestrated scan:
import { scanPackage } from './scan-orchestrator.js';
const report = await scanPackage(filePath, {
depth: 'thorough', // fast | standard | thorough
autoQuarantine: true,
quarantineDir: './quarantine',
});
// report.verdict, report.signatureFindings, report.heuristicFindings
Quarantine management:
import { quarantineFile, restoreFile } from './quarantine.js';
await quarantineFile(infectedPath, { quarantineDir: './quarantine', reason: 'SCA virus' });
await restoreFile(quarantinedId, { quarantineDir: './quarantine', restoreDir: './restored' });
Batch scan with auto-quarantine:
import { batchScan } from './scan-orchestrator.js';
const results = await batchScan(filePaths, {
depth: 'standard',
autoQuarantine: true,
quarantineDir: './quarantine',
});
src/aminet/hunk-parser.ts) for binary analysissrc/aminet/bootblock-parser.ts) for boot sector analysisnode:fs for file I/O and quarantine operations1.5% budget reflects the 6 modules covering the complete multi-layer scanning pipeline. The signature database format, hex pattern matching with wildcards, heuristic rule engine, quarantine atomicity, and orchestrator coordination logic require comprehensive context for correct security operation and troubleshooting.