At the Supreme Court Internet Registry Office (IROS), corporate/real estate register copieswhen they need to be issued in batch units, this safely assists with cart, viewing, and saving within a flow where the user logs in and pays directly. It is used for due diligence, legal review, and bulk corporate management.
This skill is
NomaDamas/k-skill(MIT) via porting, and the original author ischallengekim/iros-registry-automation(MIT) reference implementation. This is a guide organized with cowork conventions applied, and attribution is recorded at the repository rootNOTICE§1.4 and §1.5.
Hard Limits — the user must perform these directly
- Login is performed directly by the user in the browser. The agent does not enter or store ID/PW, joint certificate passwords, simple authentication, OTP, security cards, or card numbers.
- Payment is performed directly by the user. Card approval, payment confirmation, and handling payment failures are processed by a person in the browser.
- We do not provide legal advice, interpretation of rights relationships, or guarantee of the legal validity of issuance results — this is a reference automation guide.
- If IROS security programs (TouchEn nxKey, etc.) are required, install them first, restart the browser/PC, and then start again.
- Corporate payment has a constraint of 10 items per pageFor more than that, repeat payment in units of 10.
- For real estate, IROS provides bulk payment under 100,000 KRW and bulk view print/bulk save UI while logged in, so in v1 we automate only repeated cart operations.
When to use / When not to use
Use: Bulk registration issuance for 30 or more corporate items, client due diligence/KYC, organizing 100 real estate registrations per batch, mapping corporate information based on business registration numbers, and creating comprehensive reports from downloaded PDFs.
Do not use: Single registration (issued directly in the browser), rights relationship analysis/legal opinions, registration forgery/alteration, and asserting issuance results as legally effective.
Prerequisites
- Environment where Chrome/Chromium can run, Python 3.10+, Playwright/Chromium installed
- IROS login method (one of ID, joint certificate, or simple authentication)
- Payment card, TouchEn nxKey pre-installed
- Clone the upstream reference implementation and pin to the reviewed SHA
macOS / Linux — in the terminal:
git clone https://github.com/challengekim/iros-registry-automation.git
cd iros-registry-automation
git checkout 7c6924b2ff88d693a12556659188cb91041e5097
python3 -m venv .venv
source .venv/bin/activate
pip install -r requirements.txt
playwright install chromium
cp config.json.example config.json
Windows — in PowerShell (the virtual environment activation path and Python command name differ):
git clone https://github.com/challengekim/iros-registry-automation.git
cd iros-registry-automation
git checkout 7c6924b2ff88d693a12556659188cb91041e5097
python -m venv .venv
.\.venv\Scripts\Activate.ps1
pip install -r requirements.txt
playwright install chromium
copy config.json.example config.json
Why two versions:
source .venv/bin/activateis a macOS/Linux-only path, and Windows is.venv\Scripts\Activate.ps1. Also, thepython3command does not exist in the Windows python.org installer (pythonorpy -3). See the execution example of the workflow belowpython ...on macOS/Linux, read it aspython3.If PowerShell blocks script execution, first run
Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypassand then activate it.
When changing the upstream pin (SHA), the trust boundary changes, so review the new upstream diff and update it in the same PR.
Caution about script origin: the
iros_*.pyin the workflow below is not a file bundled with this skill (plugin) but rathera script inside the upstream repository cloned above (iros-registry-automation). You can run it in that directory only after completing the clone and pin review; if you have not cloned it or automation is blocked, replace it with the manual procedure in the IROS web UI for each step IROS web UI manual procedure. Login and payment are handled directly by the user in the browser in either path (Principle C — non-automatable sections are handled honestly with manual guidance).
Workflow
1. Place input files in a safe folder outside the repository
Never put sensitive information such as corporate registration numbers, company names, addresses, or unit numbers into public repositories, PRs, or test logs.
macOS / Linux:
workdir="$(mktemp -d "${TMPDIR:-/tmp}/iros-registry.XXXXXX")"
chmod 700 "$workdir"
mkdir -p "$workdir/downloads" "$workdir/logs" "$workdir/output" "$workdir/tmp-downloads"
Windows — in PowerShell:
$stamp = [guid]::NewGuid().ToString("N").Substring(0,8)
$workdir = Join-Path $env:TEMP "iros-registry-$stamp"
New-Item -ItemType Directory -Path $workdir | Out-Null
foreach ($sub in "downloads","logs","output","tmp-downloads") {
New-Item -ItemType Directory -Path (Join-Path $workdir $sub) | Out-Null
}
$workdir
Windows의
%TEMP%is under the user profile, so it is already accessible only to that account —chmod 700, so no separate action corresponding to that is needed. In the subsequent instructions,$workdir/...paths should be read in PowerShell as$workdir\....
Corporate input example ($workdir/corp-input.json):
{
"1101111234567": "예시 주식회사",
"1101117654321": "샘플 주식회사"
}
config.jsonshould be kept as a local file that is not committed to the repository, and all sensitive input, log, and output paths should be directed under $workdir (corpnum_list, companies_list, realty_list, excel_path, save_dir, pdf_dir, report_output, cart_log, download_log 등).
2. Check TouchEn nxKey and login method
- Open the IROS login page directly in the browser.
- If TouchEn nxKey installation instructions appear, install it and then restart the browser/PC.
- Log in directly using the method selected by the user (certificate/simple authentication/ID).
- Check whether card payment is available.
3. Add corporate registry certificate to cart
If you cloned upstream — in the clone directory, you can use the script below to assist with adding to the cart. If you have a corporate registration number, use the more accurate iros_cart_by_corpnum.py, and if you only have the company name, use iros_cart.py, but retry failures due to company name changes or special characters with the corporate registration number.
# ↓ 클론한 iros-registry-automation 디렉터리 안에서 (플러그인 번들 파일 아님)
python iros_cart_by_corpnum.py # 또는 상호명 기반: python iros_cart.py
If you did not clone it or automation is blocked (manual procedure): In the browser, log in to IROS → registry viewing/issuance menu → search by corporate registration number (or company name) → add the issuance target to the cart. Organizing the list as CSV/JSON makes it easier to check the order.
In either path, in the browser, the user directly pays for the payment target list in units of 10 items per page → after payment is complete, proceed to the next step.
4. View and save after corporate payment
If cloned — in the clone directory, iros_download.pycan assist with viewing and saving completed payments.
# ↓ 클론한 iros-registry-automation 디렉터리 안에서
python iros_download.py
The save path is config.json의 save_dir = $workdir/downloads. Before running, companies_list가
$workdir/companies-input.jsonif you check that it points to FileNotFoundErrorprevents
Manual procedure: After payment is complete, directly view and save (PDF) each certificate of registered matters from the view/issuance history in the IROS web UI, and
$workdir/downloadscollect them in
5. Adding real estate register copies to the cart
If cloned — from the cloned directory, iros_cart_realty.pycan assist with adding real estate items to the cart.
# ↓ 클론한 iros-registry-automation 디렉터리 안에서
python iros_cart_realty.py
For payment, viewing, and downloading, the IROS web UI's batch payment, batch view/print, and batch save are usually faster and safer, so prioritize the manual UI.
In the cloned directory, iros_download_realty.pyreview only as a supplement when needed.
6. Wizard menu (if cloned, recommended for beginners)
If you cloned the upstream, the interactive menu entry point iros_wizard.pyguides you through the above steps together.
# ↓ 클론한 iros-registry-automation 디렉터리 안에서
python iros_wizard.py
Menu: corporate cart, view/save after corporate payment, real estate cart, view/save after real estate payment, business number → corporate information lookup, PDF → comprehensive report Excel generation. If you did not clone, follow the manual procedure for each step (steps 3–5 above) in order.
Response policy
- In the first response, explicitly state **"Login and payment are handled directly by the user"**.
- Explain the scope of automation for corporations and real estate separately.
- Inform about pre-installing TouchEn nxKey and the possibility of restarting the browser.
- The issuance target list, PDFs, Excel files, and reports may contain personal and sensitive information, so a private folder outside the repositoryshould be used.
- Avoid expressions that could appear to be legal advice or interpretation of rights relationships, and assist only with issuance support and file organization.
- Leave the original author link in the response:
https://github.com/challengekim/iros-registry-automation
Related skill chaining
- before:
moai-consultant:consult-brief— Organizing the list of corporations subject to due diligence - after:
moai-lawyer:legal-legal-risk— Legal risk analysis based on issued register copies - after:
moai-officer:doc-xlsx— Converting comprehensive reports to Excel - alternative: For a single case, issue directly from the IROS web
Done when
- Distinguished the target types and input formats for corporations/real estate.
- The guidance that login, authentication, and payment are handled directly by a person is clear.
- Informed about TouchEn nxKey and the 10-items-per-page payment constraint.
- Guided that output paths and personal information be kept outside the repository.
- Original author
challengekimand reference implementation links were included.