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/jd-opensource/joysafeter/pentest-ctf-binarynpx skills add jd-opensource/JoySafeter --skill pentest-ctf-binarygit clone --depth 1 https://github.com/jd-opensource/JoySafeterWrote 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/jd-opensource/joysafeter/pentest-ctf-binary)<a href="https://agentmods.dev/skills/jd-opensource/joysafeter/pentest-ctf-binary"><img src="https://agentmods.dev/badge/skills/jd-opensource/joysafeter/pentest-ctf-binary.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.00026 | $0.00207 |
| Opus 5 | $0.00013 | $0.00103 |
| Sonnet 5 | $0.00005 | $0.00041 |
| Haiku 4.5 | $0.00003 | $0.00021 |
Grade A, and why
pentest-ctf-binary 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.
What it actually says
Pentest CTF Binary
Purpose
Analyze binary files to understand their behavior, identify memory corruption vulnerabilities, and develop exploits (ROP, Heap, Format String).
Core Workflow
- Static Analysis: Inspect binary properties, protections (NX, PIE), and code structure using
checksecandghidra. - Dynamic Analysis: Run the binary under a debugger (
gdb) to observe behavior and register states. - Vulnerability Identification: Locate crashes, buffer overflows, or format string bugs.
- Exploit Development: Construct payloads (shellcode, ROP chains) using
pwntools. - Remote Exploitation: Launch the exploit against the target server to retrieve the flag.
References
references/tools.mdreferences/workflows.md
What ships with it
2 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.
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 · 21 lines · 26 tokens per session scan A 1c8a2d6bc366
pentest-ctf-binary is a skill published in the GitHub repository jd-opensource/JoySafeter (305 stars, last pushed 7d ago), licensed Apache-2.0. It adds 26 tokens to every session and 207 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
swarmclaw
AI agent runtime and multi-agent orchestration platform. Teaches agents how to use SwarmClaw's 6 primitive tools, persistent memory, dreaming, delegation, connectors, credentials, and the skill system. Use when an agent is running on SwarmClaw and needs to understand the platform's capabilities.
nemoclaw-maintainer-validate-launchable
Validate the user-facing staging Brev Launchable deployment, NemoClaw image and runtime identity, onboarding, CLI behavior, and inference. Use when a maintainer asks to test the staging Launchable in the Brev web interface, provides a deployed Brev environment URL, hands a Launchable instance to Codex, or needs…
nemoclaw-maintainer-find-review-pr
Find open PRs with the security label and Urgent or High Project Priority. Link each PR to its issue. Identify competing or superseded PRs and report review candidates. Use when looking for the next PR to review. Trigger keywords - find pr, find review, next pr, pr to review, duplicate pr, security pr.
nemoclaw-maintainer-verify-stale
Verifies whether stale NVIDIA/NemoClaw bug reports still reproduce on the newest release tag. Use when maintainers ask to verify stale issues, reproduce old bugs on the newest release tag, or drain the bug backlog. Treats issue reproducers as untrusted, validates them on the reported release before a fixed verdict…
nemoclaw-maintainer-triage
Triage NemoClaw issues and PRs with Issue Type, Project fields, and allowed labels. Support one item or a batch. Show proposed changes and apply only changes the maintainer accepts. Trigger keywords - triage, label issues, suggest labels, batch triage, triage issue, triage PR, label this, what labels.
nemoclaw-maintainer-cross-issue-sweep
Scan open issues to find issues that a PR can also fix or conflict with. Report each relationship with file and line evidence. Use this skill during PR review to find related fixes and risks.