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 Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI --skill binary-analysis-patternsgit clone --depth 1 https://github.com/Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLIWrote 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/dokhacgiakhoa/agent-skills-4-vibe-coding-cli/binary-analysis-patterns)<a href="https://agentmods.dev/skills/dokhacgiakhoa/agent-skills-4-vibe-coding-cli/binary-analysis-patterns"><img src="https://agentmods.dev/badge/skills/dokhacgiakhoa/agent-skills-4-vibe-coding-cli/binary-analysis-patterns/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/dokhacgiakhoa/agent-skills-4-vibe-coding-cli/binary-analysis-patterns"><img src="https://agentmods.dev/badge/skills/dokhacgiakhoa/agent-skills-4-vibe-coding-cli/binary-analysis-patterns.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.00043 | $0.00581 |
| Opus 5 | $0.00022 | $0.00291 |
| Sonnet 5 | $0.00009 | $0.00116 |
| Haiku 4.5 | $0.00004 | $0.00058 |
Grade A, and why
binary-analysis-patterns 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 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.
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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
What ships with it
19 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.
- sub-skills/analysis-workflow.md 477 B
- sub-skills/arithmetic-patterns.md 484 B
- sub-skills/arm-assembly-patterns.md 623 B
- sub-skills/array-access.md 297 B
- sub-skills/bit-manipulation.md 464 B
- sub-skills/common-pitfalls.md 309 B
- sub-skills/conditional-branches.md 328 B
- sub-skills/function-signature-recovery.md 293 B
- sub-skills/idapython-analysis.md 810 B
- sub-skills/improving-decompilation.md 463 B
- sub-skills/linked-list-traversal.md 265 B
- sub-skills/loop-patterns.md 382 B
- sub-skills/pattern-matching-scripts.md 347 B
- sub-skills/string-operations.md 381 B
- sub-skills/structure-access.md 419 B
- sub-skills/switch-statement-patterns.md 289 B
- sub-skills/type-recovery.md 438 B
- sub-skills/variable-recovery.md 302 B
- sub-skills/x86-64-instruction-patterns.md 1.4 KB
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 · 51 lines · 43 tokens per session scan A a13f7816fa80
binary-analysis-patterns is a skill published in the GitHub repository Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI (510 stars, last pushed 3mo ago), with no licence file. It adds 43 tokens to every session and 581 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-09-03.
Other skills, from other repositories
printing-press-polish
Polish a generated CLI to pass verification and become publish-ready. Runs diagnostics (dogfood, verify, scorecard, go vet, gosec), automatically fixes all issues (verify failures, static-analysis findings, dead code, descriptions, README, MCP tool quality), reports the before/after delta, and offers to publish. Use…
printing-press-output-review
Internal sub-skill: agentic review of a printed CLI's sampled command output for plausibility issues that rule-based checks can't encode (substring-match relevance, format bugs, silent source drops, ranking failures). Invoked via the Skill tool by the main printing-press skill at Phase 4.85 and printing-press-polish…
eslint-fix
A project-aware assistant for finding and fixing ESLint errors, warnings, and configuration compatibility problems. ESLint is a tool that checks JavaScript and TypeScript code for style and common mistakes.
fix
Dispatch fix subagent for FIX-FIRST gaps from review, re-review, then diagnose unresolved failures after 2 loops.
dtctl
Investigate incidents, debug performance issues, analyze logs, and manage observability resources in Dynatrace using the dtctl CLI. Use this skill whenever the user asks about error rates, latency spikes, service health, crash-looping pods, web vitals, SLO status, open problems, root cause analysis, log patterns…
debug
Systematic 4-phase debugging with escalation protocol. Use when saying "debug", "investigate bug", "find root cause", "why is this failing", or "fix this bug".