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 trilwu/secskills --skill analyzing-disk-imagesgit clone --depth 1 https://github.com/trilwu/secskillsWrote 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/trilwu/secskills/analyzing-disk-images)<a href="https://agentmods.dev/skills/trilwu/secskills/analyzing-disk-images"><img src="https://agentmods.dev/badge/skills/trilwu/secskills/analyzing-disk-images/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/trilwu/secskills/analyzing-disk-images"><img src="https://agentmods.dev/badge/skills/trilwu/secskills/analyzing-disk-images.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.00119 | $0.04955 |
| Opus 5 | $0.00060 | $0.02478 |
| Sonnet 5 | $0.00024 | $0.00991 |
| Haiku 4.5 | $0.00012 | $0.00496 |
Grade D, and why
analyzing-disk-images scanned grade D with 3 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 10d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo ewfacquire -t /evidence/host01 -f encase6 -c deflate:fast \ Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
# /etc/{crontab,cron.d,rc.local}, /etc/systemd, ~/.ssh/authorized_keys Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
grep -aiE "sudo|ssh|useradd|wget|curl" /mnt/evidence/var/log/auth.log How it starts
The opening of the file, as written. The whole thing — 389 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyzing Disk Images
A disk image is a frozen crime scene, and the whole discipline is preserving that. Work only from a verified, read-only copy, prove nothing changed with hashes at every step, and remember that the deleted and the unallocated often say more than the live file system — because that is exactly what someone tried to remove.
When to Use
- You have an acquired disk image (
.E01,.dd/.raw,.aff4,.vmdk,.vhdx) to examine - Recovering deleted files, or reconstructing what was on a wiped or reformatted volume
- Building a file-system timeline or a full super-timeline across the whole image
- Carving files and artifacts out of unallocated space, slack, and free clusters
- Mining registry hives, browser data, logs, or other artifacts offline from a mounted image
- Confirming or refuting anti-forensics — timestomping, wiping, hidden or encrypted containers
When NOT to Use
- You have a RAM capture, not a disk image — use
analyzing-memory-images - You have a live or triage Windows host and want the artifact-by-artifact
investigation, not raw image handling — use
investigating-windows-endpoints - You are sweeping a live Linux host for persistence — use
analyzing-linux-persistence - You need the wider incident-response process — scoping, containment,
eradication — use
responding-to-incidents - You recovered a specific sample and want to detonate it — use
analyzing-malware
Acquisition and Integrity
Everything downstream is worthless if the image is not provably the disk. Never touch the original media without a write blocker, and never analyze the original image — work on a copy.
# Acquire to E01 (EWF) with built-in compression and hashing — preferred format
sudo ewfacquire -t /evidence/host01 -f encase6 -c deflate:fast \
-C "IR-2026-014" -E "1" -D "Dell OptiPlex sda" /dev/sda
# Raw acquisition alternative — dd with error handling, hash inline
sudo dd if=/dev/sda bs=4M conv=noerror,sync status=progress \
| tee /evidence/host01.dd | sha256sum
# Verify an existing E01 against its stored hashes
ewfverify /evidence/host01.E01
# Hash the working copy and record it — MD5 and SHA-256 both, for legacy tooling
md5sum /evidence/host01.dd
sha256sum /evidence/host01.dd
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.
- 10d ago First seen · 389 lines · 119 tokens per session scan D c483e064f874
analyzing-disk-images is a skill published in the GitHub repository trilwu/secskills (137 stars, last pushed 5d ago), licensed MIT. It adds 119 tokens to every session and 4,955 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it D with 3 findings (asks for root, reaches for credential files, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
claude-md-improver
Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintenance" or "project…
agent-platform-rag-engine-management
Manage and query Agent Platform RAG Engine Corpora and retrieve grounded contexts using the Google GenAI SDK. Use when listing RAG corpora or files, inspecting a corpus, retrieving contexts, or generating content grounded in a RAG corpus. Do not use for standard database queries (use SQL/Spanner skills), Google…
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
agent-platform-model-registry
Agent Platform Model Registry Management. Use when you need to upload, list, describe, update, or delete machine learning models (and their versions) in the Agent Platform Model Registry. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform models.
google-cloud-solution-agentic-analytics-spark-knowledge-catalog
Discovers requirements and generates guidance to design and deploy a governed, secure agentic-analytics solution for data that's distributed across Google Cloud, other cloud providers, or on-premises. Data that's outside Google Cloud (such as data from Databricks, Snowflake, Salesforce, SAP, or Oracle systems) is…