KIS Trading (한국투자증권)

SuspiciousAudited by ClawScan on May 10, 2026.

Overview

This appears to be a legitimate KIS trading skill, but it can place real stock orders without an enforced in-script confirmation step.

Install only if you are comfortable giving the agent access to your KIS brokerage API credentials. Start with the mock/demo endpoint, keep the config and token files private, and do not allow live orders unless you have explicitly reviewed the stock, side, quantity, and price.

Findings (3)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

If the agent invokes this command prematurely or with misunderstood parameters, it could place real stock trades and cause financial loss.

Why it was flagged

After printing an order warning, the script immediately calls the order API; there is no required --confirm flag or interactive prompt before a live buy/sell order is submitted.

Skill content
print(f"\n⚠️  위 내용으로 {side_str} 주문을 실행합니다.")

    result = place_order(cfg, token, args.side, args.code, args.qty, args.price, args.market)
Recommendation

Use the demo KIS endpoint first, require explicit user approval before every order, and consider modifying the script so --dry-run is the default and live orders require a separate --confirm flag or interactive confirmation.

What this means

Anyone with access to the config or cached token may be able to query account information or place trades through the broker API.

Why it was flagged

The skill requires broker API credentials and an account number, then caches an access token locally. This is expected for KIS trading, but it grants sensitive account access.

Skill content
required = ['APP_KEY', 'APP_SECRET', 'ACCOUNT_NO'] ... _TOKEN_FILE = os.path.expanduser('~/.kis-trading/token.json') ... json.dump({'token': token, 'expired': expired}, f)
Recommendation

Store the config and token files securely, avoid sharing command output or config files, and use the least-privileged/demo credentials where possible.

What this means

Users have less external context for verifying the publisher, maintenance history, or authenticity of a financial-trading skill.

Why it was flagged

The package does not provide an upstream source or homepage. For a skill that handles broker credentials and orders, provenance is important even though the included code is reviewable.

Skill content
Source: unknown
Homepage: none
Recommendation

Verify the publisher and code before use, and prefer a trusted or auditable source for tools that can access brokerage accounts.