Agent Stuff is a personal package of reusable skills, extensions, prompt commands, themes, and utilities for the Pi Coding Agent. Its author uses these tools across projects, and the catalogue entries are components from this package that support that workflow.
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 agentmods add skills/mitsuhiko/agent-stuff/ghidranpx skills add mitsuhiko/agent-stuff --skill ghidragit clone --depth 1 https://github.com/mitsuhiko/agent-stuffWrote 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/mitsuhiko/agent-stuff/ghidra)<a href="https://agentmods.dev/skills/mitsuhiko/agent-stuff/ghidra"><img src="https://agentmods.dev/badge/skills/mitsuhiko/agent-stuff/ghidra.svg" alt="Measured on agentmods" 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 | $0.00035 | $0.01938 |
| Opus 5 | $0.00017 | $0.00969 |
| Sonnet 5 | $0.00007 | $0.00388 |
| Haiku 4.5 | $0.00003 | $0.00194 |
Grade A, and why
ghidra scanned grade A with 0 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 5d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ghidra Headless Analysis Skill
Perform automated reverse engineering using Ghidra's analyzeHeadless tool. Import binaries, run analysis, decompile to C code, and extract useful information.
Quick Reference
| Task | Command |
|---|---|
| Full analysis with all exports | ghidra-analyze.sh -s ExportAll.java -o ./output binary |
| Decompile to C code | ghidra-analyze.sh -s ExportDecompiled.java -o ./output binary |
| List functions | ghidra-analyze.sh -s ExportFunctions.java -o ./output binary |
| Extract strings | ghidra-analyze.sh -s ExportStrings.java -o ./output binary |
| Get call graph | ghidra-analyze.sh -s ExportCalls.java -o ./output binary |
| Export symbols | ghidra-analyze.sh -s ExportSymbols.java -o ./output binary |
| Find Ghidra path | find-ghidra.sh |
Prerequisites
- Ghidra must be installed. On macOS:
brew install --cask ghidra - Java (OpenJDK 17+) must be available
The skill automatically locates Ghidra in common installation paths. Set GHIDRA_HOME environment variable if Ghidra is installed in a non-standard location.
Main Wrapper Script
./scripts/ghidra-analyze.sh [options] <binary>
Wrapper that handles project creation/cleanup and provides a simpler interface to analyzeHeadless.
Options:
-o, --output <dir>- Output directory for results (default: current dir)-s, --script <name>- Post-analysis script to run (can be repeated)-a, --script-args <args>- Arguments for the last specified script--script-path <path>- Additional script search path-p, --processor <id>- Processor/architecture (e.g.,x86:LE:32:default)-c, --cspec <id>- Compiler spec (e.g.,gcc,windows)--no-analysis- Skip auto-analysis (faster, but less info)--timeout <seconds>- Analysis timeout per file--keep-project- Keep the Ghidra project after analysis--project-dir <dir>- Directory for Ghidra project (default: /tmp)--project-name <name>- Project name (default: auto-generated)-v, --verbose- Verbose output
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- scripts/find-ghidra.sh 1.6 KB runs code
- scripts/ghidra_scripts/ExportAll.java 11 KB
- scripts/ghidra_scripts/ExportCalls.java 5.3 KB
- scripts/ghidra_scripts/ExportDecompiled.java 3.1 KB
- scripts/ghidra_scripts/ExportFunctions.java 4.8 KB
- scripts/ghidra_scripts/ExportStrings.java 4.4 KB
- scripts/ghidra_scripts/ExportSymbols.java 5.7 KB
- scripts/ghidra-analyze.sh 5.9 KB runs code
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.
- 5d ago First seen · 255 lines · 35 tokens per session scan A d93aa0f847e7
ghidra is a skill published in the GitHub repository mitsuhiko/agent-stuff (3,056 stars, last pushed today), licensed Apache-2.0. It adds 35 tokens to every session and 1,938 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…