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 kimlawtech/korean-jangbu-for --skill jangbu-connectgit clone --depth 1 https://github.com/kimlawtech/korean-jangbu-forWrote 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/kimlawtech/korean-jangbu-for/jangbu-connect)<a href="https://agentmods.dev/skills/kimlawtech/korean-jangbu-for/jangbu-connect"><img src="https://agentmods.dev/badge/skills/kimlawtech/korean-jangbu-for/jangbu-connect/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/kimlawtech/korean-jangbu-for/jangbu-connect"><img src="https://agentmods.dev/badge/skills/kimlawtech/korean-jangbu-for/jangbu-connect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 11 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 3 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 22 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 111 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 124 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 58 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 120 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 69 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 82 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 83 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 85 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Tool Misuse · line 124 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00098 | $0.01524 |
| Opus 5 | $0.00049 | $0.00762 |
| Sonnet 5 | $0.00020 | $0.00305 |
| Haiku 4.5 | $0.00010 | $0.00152 |
Grade A, and why
jangbu-connect 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 11d 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
jangbu-connect
CODEF 자격증명 설정 가이드 스킬.
왜 CODEF인가
한국에서 홈택스·은행·카드·4대보험 데이터를 합법적·합리적 비용으로 자동 수집할 수 있는 유일한 프록시 API.
- 한국 공공기관·금융기관 통합 API
- 간편인증(카카오·PASS·공동인증서) 지원
- 개인 개발자 샌드박스 무료 (월 1,000건까지)
- 사업자등록 없어도 가입 가능
BYOK 보안 원칙
- 스킬 제작자는 자격증명 취급 안함 — 사용자 본인 계정의 키만 사용
- 키는 로컬에만 저장 (macOS Keychain 기본, 실패 시
~/.jangbu/credentials.env) - 외부 서버 동기화 없음
- 모든 API 호출은 사용자 자신의 비용으로 실행
인터뷰 플로우
Step 1. CODEF 계정 발급 (5분)
CODEF 자동 수집을 쓰려면 개인 개발자 키가 필요합니다.
[1] 브라우저에서 https://developer.codef.io 접속
[2] 우측 상단 "회원가입" → 이메일 인증 (사업자번호 불필요)
[3] 로그인 후 상단 "My Page" → "서비스 관리" → "신규 서비스 등록"
- 서비스 명: 예) korean-jangbu-for
- 서비스 구분: "개발용" 선택
- 이용 서비스: "대한민국" · "공공" · "금융" 체크
[4] 등록 직후 표시되는
- Client ID
- Client Secret
두 값을 복사해 두세요.
[5] (선택) "My Page" → "RSA Public Key" 에서 공개키 PEM도 복사해 두면
프로덕션 API에서 비밀번호 암호화 전송이 가능해요 (샌드박스는 불필요).
준비 끝나면 Enter 누르세요.
Step 2. 자격증명 등록
아래 값을 순서대로 입력받습니다. 값은 로컬에만 저장됩니다.
Client ID: (CODEF My Page에서 복사한 값)
Client Secret: (CODEF My Page에서 복사한 값)
RSA Public Key: (선택, 프로덕션 전환 시만 필요)
샌드박스 사용: Y/n (기본 Y — 개인 체험·테스트)
Keychain 저장: Y/n (기본 Y — 실패 시 envfile로 fallback)
입력이 끝나면 내부적으로 MCP 도구 codef_credentials_save를 호출:
codef_credentials_save(
client_id="...",
client_secret="...",
public_key_pem="...", # 선택
sandbox=True,
use_keyring=True,
)
Step 3. 등록 확인
codef_credentials_status
응답 예시:
{
"CODEF_CLIENT_ID": {"set": true, "source": "keyring", "preview": "abcd...xyz1"},
"CODEF_CLIENT_SECRET": {"set": true, "source": "keyring", "preview": "****...****"},
"CODEF_PUBLIC_KEY": {"set": false, "source": null, "preview": null},
"CODEF_SANDBOX": {"set": true, "source": "keyring", "preview": "1"}
}
Step 4. 연결 테스트
간편인증 테스트를 할 수 있는 메뉴로 이동합니다.
[1] 홈택스 사업자등록증명 1건 발급 테스트 → /korean-jangbu-for → [F]
[2] 지금은 건너뛰기
사용자가 직접 받는 자격증명 4종
| 키 | 필수 | 용도 |
|---|---|---|
CODEF_CLIENT_ID |
필수 | OAuth 클라이언트 ID |
CODEF_CLIENT_SECRET |
필수 | OAuth 시크릿 |
CODEF_PUBLIC_KEY |
선택 | 프로덕션 비밀번호 RSA 암호화용 |
CODEF_SANDBOX |
자동 | "1"=샌드박스, "0"=운영 |
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.
- 11d ago First seen · 151 lines · 98 tokens per session scan A 33a7e9f24d80
jangbu-connect is a skill published in the GitHub repository kimlawtech/korean-jangbu-for (83 stars, last pushed 13d ago), licensed Apache-2.0. It adds 98 tokens to every session and 1,524 once invoked, about $0.0005 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
bookkeeping
Use when a small business needs audit-ready books — a chart of accounts, posting a transaction to the right account and side, clearing an uncategorized bank feed, cash vs accrual, or a ledger that won't tie to the bank. NOT interpreting the numbers — runway, burn, P&L cadence (that is finance-ops), NOT issuing…
countbean-accounting
Rules for writing correct double-entry Beancount transactions when managing a Countbean cloud book — account naming, how to balance postings, categorisation, and safe ingestion. Use whenever recording, importing, or correcting financial data in a Countbean book.
bukio-cli
Drive bukio-cli — agent-first double-entry bookkeeping for SMEs across eleven jurisdictions. Book invoices, archive the originals, keep the books balanced.
QuickBooks Automation
Automate QuickBooks accounting workflows including invoicing, expenses, reporting, and bank reconciliation.
ledger
Use for ANY monetary, accounting, ledger, journal, balance, P&L, fee, FX, invoice, tax, cost-basis, or valuation work. Exact Money.from (never floats or parseFloat), double-entry via JournalEntry + validateEntry + Ledger.apply, MCP moneycompute / ledgerpost, canon citations, Zero-Skip + Canonical Financial Artifact.…
ledger-audit
Whole-repo financial audit. Use for ledger-audit, financial audit, or /ledger-audit. Scan for non-kernel money math, reconstruct flows as JournalEntry sequences, prove with validateEntry + Ledger.apply + runTrace + auditHash.