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.
git clone --depth 1 https://github.com/sungjunlee/beopsuny-skillWrote 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/plugins/sungjunlee/beopsuny-skill/beopsuny)<a href="https://agentmods.dev/plugins/sungjunlee/beopsuny-skill/beopsuny"><img src="https://agentmods.dev/badge/plugins/sungjunlee/beopsuny-skill/beopsuny.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
beopsuny 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 2d 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
{
"name": "beopsuny",
"source": "./",
"description": "법순이 — 한국 법령/판례 조사, 계약서 검토, 컴플라이언스 체크를 돕는 법무 어시스턴트",
"version": "0.8.0",
"category": "legal",
"keywords": [
"korean-law",
"legal-research",
"contract-review",
"compliance",
"korea",
"legislation",
"precedent"
],
"homepage": "https://github.com/sungjunlee/beopsuny-skill",
"license": "MIT"
}What ships with it
2 files beside marketplace.json#beopsuny 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.
- 2d ago First seen · 18 lines scan A 96fa17749ec9
beopsuny is a plugin published in the GitHub repository sungjunlee/beopsuny-skill (3 stars, last pushed today), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-04.
Other plugins, from other repositories
claude-grc-engineering marketplace
Plugin marketplace listing 66 plugins: grc-engineer, grc-auditor, grc-internal, grc-tprm, grc-reporter.
eu-nis2
EU NIS2 Directive (Directive (EU) 2022/2555) — Reference plugin: scope determination across essential vs important entities, Article 21 risk-management measure evidence checklist, and the 24h/72h/1mo incident-reporting runbook. SCF-backed gap assessment via the crosswalk.
nist-csf-20
NIST Cybersecurity Framework (v2.0) — Reference plugin with scope determination, evidence checklist, and SCF-backed gap assessment across the six Functions (GV/ID/PR/DE/RS/RC).
poam-automation
FedRAMP POA&M lifecycle management and VDR generation. Converts Nessus, Tenable, Qualys, and Wiz scanner exports into a FedRAMP-compliant POA&M, manages the full finding lifecycle, generates FedRAMP 20x VDR reports with live CISA KEV and EPSS enrichment, and produces per-release Product Vulnerability Disclosure…
au-apra-cps-234
APRA CPS 234 - Reference plugin with scope determination, evidence checklist, and SCF-backed gap assessment for information security.
ch-fadp
Swiss Federal Act on Data Protection (nFADP) plugin - data protection compliance with voluntary DSO, risk-based breach notification, and Swiss transfer mechanisms.