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/hjtrbo/pcmhackmcp/pcmhack-mcpnpx skills add hjtrbo/PcmHackMCP --skill pcmhack-mcpgit clone --depth 1 https://github.com/hjtrbo/PcmHackMCPWrote 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/hjtrbo/pcmhackmcp/pcmhack-mcp)<a href="https://agentmods.dev/skills/hjtrbo/pcmhackmcp/pcmhack-mcp"><img src="https://agentmods.dev/badge/skills/hjtrbo/pcmhackmcp/pcmhack-mcp.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.00129 | $0.02376 |
| Opus 5 | $0.00064 | $0.01188 |
| Sonnet 5 | $0.00026 | $0.00475 |
| Haiku 4.5 | $0.00013 | $0.00238 |
Grade A, and why
pcmhack-mcp 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 3d 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PcmHackMCP run_python - the things that bite
run_python ships a whole Jython 2.7 script to a live Ghidra session and runs it as a GhidraScript in one call, returning only what the script prints. Same interpreter and same Ghidra API as ghidra_bridge, but the transport and a few rules are different.
If you forget everything else:
- It's Jython 2.7 + the Ghidra Flat API. Every Jython/API gotcha from the
ghidra-bridgeskill applies to the script you send. The critical three are inlined below; the full trap shelf + API method-name table live in that skill (Nathan:~/.claude/skills/ghidra-bridge/SKILL.md) - read it for anything non-trivial. - Send one complete script;
printwhat you want back. No return value crosses the wire - only stdout/stderr. Emit results withprint(json.dumps(...)). - The transaction is automatic - and commits even on error. Don't open one. But guard each row (bare
except:), because work done before an uncaught exception is saved, not rolled back. - Imports work directly.
from ghidra.program.model.symbol import SourceTypejust works - you are already server-side. There is noremote_eval,remote_exec, orremote_importhere.
Repo: https://github.com/hjtrbo/PcmHackMCP
The dedicated tools can overflow - page, filter, or summarize
run_python is the bulk workhorse, but the same MCP server also exposes dedicated listing
tools (list_functions, list_data_items, list_strings, list_segments, ...). The trap:
a whole-program listing can return thousands of rows and blow the single tool-response
limit. A typical automotive ECU image has many thousands of functions and tens of thousands
of data items, so an unfiltered list_functions or list_data_items will overflow in one shot.
When you need a slice, do not dump the whole list:
- Use the tool's own paging/filter args, or
search_functions_by_namefor a targeted lookup. - For counts, scans, or aggregates over the whole program, push the work into
run_pythonandprintonly the count plus a bounded sample - never round-trip thousands of rows just to filter them client-side.
What ships with it
1 file 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.
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.
- 3d ago First seen · 178 lines · 129 tokens per session scan A 7652e12a19cd
pcmhack-mcp is a skill published in the GitHub repository hjtrbo/PcmHackMCP (1 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 129 tokens to every session and 2,376 once invoked, about $0.0006 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…