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 xalgorix/xalgorix --skill acquiring-disk-image-with-dd-and-dcflddgit clone --depth 1 https://github.com/xalgorix/xalgorixWrote 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/xalgorix/xalgorix/acquiring-disk-image-with-dd-and-dcfldd)<a href="https://agentmods.dev/skills/xalgorix/xalgorix/acquiring-disk-image-with-dd-and-dcfldd"><img src="https://agentmods.dev/badge/skills/xalgorix/xalgorix/acquiring-disk-image-with-dd-and-dcfldd/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/xalgorix/xalgorix/acquiring-disk-image-with-dd-and-dcfldd"><img src="https://agentmods.dev/badge/skills/xalgorix/xalgorix/acquiring-disk-image-with-dd-and-dcfldd.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.00038 | $0.02807 |
| Opus 5 | $0.00019 | $0.01404 |
| Sonnet 5 | $0.00008 | $0.00561 |
| Haiku 4.5 | $0.00004 | $0.00281 |
Grade B, and why
acquiring-disk-image-with-dd-and-dcfldd scanned grade B with 1 finding 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 8d 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.
- Root/sudo privileges on the forensic workstation This is a copy
77% identical to acquiring-disk-image-with-dd-and-dcfldd — 19 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Acquiring Disk Image with dd and dcfldd
When to Use
- When you need to create a forensic copy of a suspect drive for investigation
- During incident response when preserving volatile disk evidence before analysis
- When law enforcement or legal proceedings require a verified bit-for-bit copy
- Before performing any destructive analysis on a storage device
- When acquiring images from physical drives, USB devices, or memory cards
Detection Gaps & Validation
- Hidden areas a naive
ddsilently drops: an HPA or DCO makes the disk report fewer sectors than it physically has, sodd if=/dev/sdbcaptures less than the full media. Checkhdparm -N /dev/sdb(HPA) andhdparm --dco-identify /dev/sdb(DCO) and compare against the label /smartctl -inative capacity before imaging; document or remove the HPA per policy. conv=noerror,syncmasks bad sectors: zero-padding keeps offsets aligned but the gaps then look like real null data. Always readdcfldd'serrlog(or addrescuemapfile) and record every unreadable LBA - never present a padded region as recovered content.- Hash mismatch is not automatically tampering: a source-vs-image mismatch most often means a missing write-blocker, a failing disk remapping sectors, or a volume that auto-mounted/fsck'd during read. Compare
source_hash_beforevssource_hash_after; if the source changed, the imaging chain is at fault, not the suspect. - Validate independently: confirm with a second tool and a second algorithm (compute SHA-256 and MD5, or re-image with
ewfacquire) and verifydcfldd's per-windowhashwindowhashes match a freshsha256sumpass over the image. - Interpretation pitfalls (false positives): USB bridge/adapter capacity clipping,
.gzcompression hiding read errors, and live-system imaging where mounted-volume timestamps mutate mid-read. Record block size, write-blocker model, and tool version so a reviewer can reproduce the exact hash.
Prerequisites
- Linux-based forensic workstation (SIFT, Kali, or any Linux distro)
dd(pre-installed on all Linux systems) ordcfldd(enhanced forensic version)- Write-blocker hardware or software write-blocking configured
- Destination drive with sufficient storage (larger than source)
- Root/sudo privileges on the forensic workstation
- SHA-256 or MD5 hashing utilities (
sha256sum,md5sum)
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.
- 8d ago First seen · 251 lines · 38 tokens per session scan B 104a73755290
acquiring-disk-image-with-dd-and-dcfldd is a skill published in the GitHub repository xalgorix/xalgorix (972 stars, last pushed 2d ago), licensed Apache-2.0. It adds 38 tokens to every session and 2,807 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). It is 77% identical to acquiring-disk-image-with-dd-and-dcfldd, differing in 19 lines, and is treated as a copy.
Other skills, from other repositories
acquiring-disk-image-with-dd-and-dcfldd
Use when create forensically sound bit-for-bit disk images using dd and dcfldd while preserving evidence integrity through hash verification. Use when createing forensically sound bit-for-bit disk images using dd and dcfldd.
acquiring-disk-image-with-dd-and-dcfldd
Create forensically sound bit-for-bit disk images using dd and dcfldd while preserving evidence integrity through hash verification.
acquiring-disk-image-with-dd-and-dcfldd
Create forensically sound bit-for-bit disk images with dd or dcfldd on a Linux forensic workstation, preserving evidence integrity through hash verification (MD5/SHA) during acquisition. Use when imaging a suspect drive, USB device, or memory card for investigation, preserving volatile disk evidence during incident…
acquiring-disk-image-with-dd-and-dcfldd
Create forensically sound bit-for-bit disk images using dd and dcfldd while preserving evidence integrity through hash verification.
acquiring-disk-image-with-dd-and-dcfldd
Create forensically sound bit-for-bit disk images using dd and dcfldd while preserving evidence integrity through hash verification.
acquiring-disk-image-with-dd-and-dcfldd
A procedure for creating a forensic, bit-for-bit copy of a storage device with Linux tools such as `dd` or `dcfldd`, then checking its hash to verify that the copy is unchanged.