Individual skill
pojia-memory
Cross-platform process memory, dump, runtime, heap, pointer-chain, signature, structure, and memory-forensics analysis for Windows, Linux, Android, Unity IL2CPP, Unreal, native applications, crash dumps, and raw memory images. Use when Codex receives a PID, process name, memory dump, module offset, AOB pattern, pointer chain, runtime address, crash dump, Volatility artifact, Frida target, or needs ReadProcessMemory/process_vm_readv code, map/module discovery, structure reconstruction, memory diffing, hooks, watchpoints, dump analysis, or rollback-safe patch tooling.
skills/pojia-memory/SKILL.md
Source commit b6785d53ca5133974b6d9c987f13f606df28cc38
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Local scripts
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 125
- Repository last updated
- Oct 10, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agent Repository topic
- integrity-protection Repository topic
- macos Repository topic
- persona Repository topic
- prompt-injection Repository topic
- workbuddy Repository topic
- automation Repository topic
- codex Repository topic
- codex-cli Repository topic
- no-dependencies Repository topic
- operations Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 2,184 bytesagents/openai.yamlasset · 232 bytesreferences/dump-structures.mddoc · 1,062 bytesreferences/linux-android.mddoc · 768 bytesreferences/windows.mddoc · 895 bytesscripts/aob_scan.pyruns · 1,583 bytesscripts/dump_strings.pyruns · 1,038 bytes
Read excerpt
# Pojia Memory
Resolve runtime addresses and structures from evidence, then produce repeatable tooling.
## Start
1. Establish architecture, pointer width, endianness, target OS/runtime, and artifact type.
2. Distinguish absolute addresses, module-relative offsets, signatures, pointer chains, handles, and generated references.
3. Record module mappings, page protections, thread/heap context, and address provenance.
4. Use `scripts/aob_scan.py` for wildcard byte-pattern scans and `scripts/dump_strings.py` for offset-aware ASCII/UTF-16 extraction.
## Select references
- Windows live process, dumps, WinDbg, RPM/WPM: read `references/windows.md`.