Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add dariushoule/x64dbg-skills/plugin install x64dbg-skillsWrote 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/dariushoule/x64dbg-skills/yara-sigs)<a href="https://agentmods.dev/skills/dariushoule/x64dbg-skills/yara-sigs"><img src="https://agentmods.dev/badge/skills/dariushoule/x64dbg-skills/yara-sigs/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/dariushoule/x64dbg-skills/yara-sigs"><img src="https://agentmods.dev/badge/skills/dariushoule/x64dbg-skills/yara-sigs.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.00028 | $0.01073 |
| Opus 5 | $0.00014 | $0.00536 |
| Sonnet 5 | $0.00006 | $0.00215 |
| Haiku 4.5 | $0.00003 | $0.00107 |
Grade A, and why
yara-sigs 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 13d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
yara-sigs
Scan debuggee memory (via a state snapshot) against a large YARA signature database to identify packers, crypto constants, anti-debug tricks, malware families, and more.
Instructions
Follow these steps exactly:
1. Check prerequisites
Run pip show yara-python via Bash. If not installed, tell the user to run pip install yara-python and stop.
Run git --version via Bash. If not installed, tell the user to install Git and stop.
2. Ensure the YARA signature database is available
Check if the directory ${CLAUDE_PLUGIN_ROOT}\yarasigs exists (use dir). If it does not exist, clone it:
git clone --recurse-submodules https://github.com/x64dbg/yarasigs "${CLAUDE_PLUGIN_ROOT}\yarasigs"
If the directory exists but looks incomplete (missing Yara-Rules or citizenlab subdirectories), update submodules:
git -C "${CLAUDE_PLUGIN_ROOT}\yarasigs" submodule update --init --recursive
3. Determine what to scan for
The YARA database contains many rule categories. If the user specified what they want to scan for in their invocation, use that. Otherwise, ask the user what they want to scan for using AskUserQuestion with these options:
- Packers & compilers — Detect packers (UPX, Themida, etc.) and compiler signatures
- Crypto constants — Find cryptographic algorithm constants (AES S-boxes, RSA, MD5, etc.)
- Anti-debug / anti-VM — Detect anti-debugging and anti-virtualization techniques
- All signatures — Scan with every available rule (slower, more noise)
Map the selection to rule category paths:
| Selection | Rule paths (relative to yarasigs/) |
|---|---|
| Packers & compilers | packer.yara, packer_compiler_signatures.yara, Yara-Rules/packers/ |
| Crypto constants | crypto_signatures.yara, Yara-Rules/crypto/ |
| Anti-debug / anti-VM | Yara-Rules/antidebug_antivm/ |
| All signatures | All .yar and .yara files recursively |
4. Obtain a snapshot to scan
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.
- 13d ago First seen · 85 lines · 28 tokens per session scan A 16c458a925e4
yara-sigs is a skill published in the GitHub repository dariushoule/x64dbg-skills (206 stars, last pushed 6mo ago), licensed MIT. It adds 28 tokens to every session and 1,073 once invoked, about $0.0001 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
performance-optimization
Optimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.
gke-ai-troubleshooting-jobset-interruption
Diagnoses GKE JobSet interruptions, restarts, and preemptions for AI/ML training workloads autonomously. Use when troubleshooting JobSet restart loops, spot VM preemptions, node readiness failures, host VM issues, or coordinator worker crashes. Don't use for general GKE cluster creation, basic workload deployment, or…
gke-node-notready
Diagnoses GKE nodes reporting NotReady or Unknown status by inspecting node conditions, events, kubelet/containerd logs, and node metrics, then proposing safe remediations. Use when nodes show NotReady, when the kubelet stops posting node status, or when workloads are evicted or stuck Pending due to node health. Don't…
gke-ai-troubleshooting-tpu-vbar-oom
Diagnoses and prevents vbarcontrolagent segfaults, out-of-memory (OOM) errors, and TPU device initialization failures on TPU v6e nodes in GKE caused by race conditions during TPU device resets or high-frequency metrics polling. Use when troubleshooting vbarcontrolagent crashes, memory cgroup OOMs in serial console…
systematic-debugging
A step-by-step method for finding the underlying cause of technical problems before changing code. It covers reading errors, reproducing failures, checking recent changes, and tracing data across system components.
fixing-motion-performance
Audit and fix animation performance issues including layout thrashing, compositor properties, scroll-linked motion, and blur effects. Use when animations stutter, transitions jank, or reviewing CSS/JS animation performance.