toss-securities
토스증권 공식 Open API(OAuth2)로 계좌, 보유주식, 시세/종목/시장정보, 주문조회를 안전한 read-only 흐름으로 조회한다. 공식 credentials가 없거나 공식 API가 지원하지 않는 기능은 비공식 경로로 우회하지 않는다.
Savant verdict: Review advised
SkillSpector or the source hub flagged patterns to review before use.
Live evaluation
Not evaluated yet. Workspaces can request a live evaluation.
Safety (NVIDIA SkillSpector)
Scan pending.
Structure
- 1 referenced file isn't in the packagescripts/generate-skill-stubs.js. They may be binary, too large to catalog, or missing upstream.
- The source hub's security checks flagged this skillGen Agent Trust Hub: warn (This skill requires the installation of a CLI tool from a third-party GitHub repository to handle sensitive financial data. This introduces a supply chain risk from unverified external code.); Socket: warn (1 alert: gptSecurity); Snyk: warn (Risk: MEDIUM · 1 issue)
SKILL.md
--- name: toss-securities description: 토스증권 공식 Open API(OAuth2)로 계좌, 보유주식, 시세/종목/시장정보, 주문조회를 안전한 read-only 흐름으로 조회한다. 공식 credentials가 없거나 공식 API가 지원하지 않는 기능은 비공식 경로로 우회하지 않는다. license: MIT metadata: category: finance locale: ko-KR phase: v1 --- # toss-securities <!-- k-skill:cli-stub — generated by scripts/generate-skill-stubs.js; edit skill.json / instruction.md instead --> ## Get the full instructions (required first step) Run this and follow its output as the primary instructions for this skill: ```bash npx -y @nomadamas/k-skill@0 instruct toss-securities ``` The CLI detects the current runtime (Dolshoi vault/CloakBrowser vs generic) and prints only the applicable instructions, always up to date. Helper files bundled with the CLI are listed by: ```bash npx -y @nomadamas/k-skill@0 files toss-securities ``` If `npx` is unavailable, install Node.js 18+ or follow https://github.com/NomaDamas/k-skill#readme, or read the source instructions at https://github.com/NomaDamas/k-skill/blob/main/toss-securities/instruction.md. ## Hard rules even without the CLI - Never execute payment, message/email delivery, final submission, cancellation, or public posting without the user's explicit approval immediately beforehand. - Never ask for, print, or store plaintext credentials in chat, files, or shell arguments. - Never bypass legal, physical-presence, CAPTCHA, identity-proofing, or electronic-signature boundaries.