스킬 verify-bank-detail-change

📦

verify-bank-detail-change

Name: verify-bank-detail-change
Author: victor-emmanuel-c

v1.0 콘텐츠 리비전 r1 안전 🌐 네트워크 접근

Verify Supplier Bank Detail Changes

Supplier bank change requests can redirect payments to an unverified account. This skill uses Jithox MCP checks to compare IBANs and identify cases requiring independent confirmation.

지원: Claude Codex Code(CC)

📊 74 적절함

Maintain this Skill? Claim it 📊 74 적절함

내 에이전트로 설치

이 요청을 에이전트에 복사하세요. 공식 Skill 페이지와 매니페스트가 포함되어 있습니다.

에이전트 요청

Review the Skillstore skill "verify-bank-detail-change" from https://skillstore.io/skills/victor-emmanuel-c-verify-bank-detail-change.md and its manifest at https://skillstore.io/api/skills/victor-emmanuel-c-verify-bank-detail-change/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

에이전트는 계속해서 계획을 표시하고 보안 정책에서 요구하는 확인을 요청해야 합니다.

에이전트가 읽기 쉬운 리소스

AI 에이전트, 크롤러, 스크립트가 전체 페이지 대신 정리된 컨텍스트만 필요할 때 이 링크를 사용하세요.

Markdown 상세 GET /skills/victor-emmanuel-c-verify-bank-detail-change.md 서명된 manifest GET /api/skills/victor-emmanuel-c-verify-bank-detail-change/manifest 서명된 lockfile GET /api/skills/victor-emmanuel-c-verify-bank-detail-change/lockfile

테스트해 보기

"verify-bank-detail-change" 사용 중입니다. A proposed supplier account matches the trusted stored account, and completed tool checks report a match and valid structure.

예상 결과:

Illustrative summary, not a live tool result.
Workflow outcome: no_change, based on the completed account comparison.
IBAN structure: valid; account ownership remains unproven.
Next step: investigate any email that still insists the account changed.
Nothing was paid or changed.

"verify-bank-detail-change" 사용 중입니다. The proposed supplier account differs from the stored account, and completed checks report a change with valid IBAN structure.

예상 결과:

Illustrative summary, not a live tool result.
Workflow outcome: verify_first.
Hold payment and record updates pending independent confirmation.
Call a number from existing records and have the supplier read back the full account number.
Valid structure does not prove ownership. No callback is claimed, and nothing was paid or changed.

"verify-bank-detail-change" 사용 중입니다. The native verification tools are unavailable, so no live checks complete.

예상 결과:

Illustrative summary, not a live tool result.
Tool-called status: not_run. Raw results: unavailable.
Workflow outcome: verify_first. Account comparison and IBAN validation remain unresolved.
Hold payment and record updates; complete the checks and independent confirmation.
Nothing was paid or changed.

보안 감사

안전

v1 • 2026. 10. 5. 버전별 보고서 열기

Six example URLs use public test accounts, and both reconnaissance matches describe safety boundaries rather than system inspection. The live MCP workflow sends supplier IBANs to Jithox, creating an external financial-data disclosure risk without an explicit approval requirement. No evidence found of malicious exfiltration intent, prompt injection, or instructions to execute the example shell commands.

스캔된 파일

130

분석된 줄 수

검토 항목

오탐 무시됨

기능 검토 항목 (1)

이 스킬에 대해 예상될 수 있는 실제 로컬 기능이므로 검토가 필요하지만, 확인된 악의적 동작으로는 집계되지 않습니다.

낮음

SKILL.md:15

Hardcoded URL

Use only check_payment_change and verify_iban at https://jithox.com/api/mcp.

Lines 22-28 require sending proposed and stored supplier IBANs to the external Jithox MCP service. This exposes financial identifiers without explicit disclosure approval; no malicious intent is established.

위험 요인

🌐 네트워크 접근 (7)

references/examples.md:16 references/examples.md:24 references/examples.md:32 references/examples.md:52 references/examples.md:60 references/examples.md:68 SKILL.md:15

감사자: codex

이 보고서 공유 및 인용

버전이 지정된 평가 보고서, 중립 배지, 임베드 카드 및 인용을 공유하세요. Skillstore는 근거를 보고하지만 이 Skill의 안전 여부를 판단하지 않습니다.

버전별 보고서 열기

보고서 링크 복사

https://skillstore.io/skills/victor-emmanuel-c-verify-bank-detail-change/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown 배지

[![Skillstore security assessment](https://skillstore.io/badges/skills/victor-emmanuel-c-verify-bank-detail-change/security.svg)](https://skillstore.io/skills/victor-emmanuel-c-verify-bank-detail-change?utm_source=security_passport_badge)

HTML 배지

<a href="https://skillstore.io/skills/victor-emmanuel-c-verify-bank-detail-change?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/victor-emmanuel-c-verify-bank-detail-change/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

임베드 카드

<iframe src="https://skillstore.io/embed/skills/victor-emmanuel-c-verify-bank-detail-change.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

학술 인용 (APA · BibTeX · CFF)

APA 인용

victor-emmanuel-c. (2026). verify-bank-detail-change security audit report (audit version 1) [Author version 1.0]. Skillstore. https://skillstore.io/skills/victor-emmanuel-c-verify-bank-detail-change/audits/1

BibTeX 인용

@techreport{victor-emmanuel-c-victor-emmanuel-c-verify-bank-detail-change-2026,
  author = {victor-emmanuel-c},
  title = {verify-bank-detail-change security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/victor-emmanuel-c-verify-bank-detail-change/audits/1},
  note = {Author version 1.0}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "verify-bank-detail-change security audit report (audit version 1)"
version: "1.0"
type: report
authors:
  - name: "victor-emmanuel-c"
date-released: "2026-10-05"
url: "https://skillstore.io/skills/victor-emmanuel-c-verify-bank-detail-change/audits/1"
identifiers:
  - type: other
    value: "skillstore:victor-emmanuel-c-verify-bank-detail-change:audit:1"
    description: "Skillstore immutable audit report identifier"

Skillstore 점수

이 점수의 이유 증거 신뢰도: 중간

아키텍처

유지보수성

콘텐츠

커뮤니티

사양 준수

만들 수 있는 것

Review a Supplier Change Request

Compare a proposed IBAN against accounting records and hold changed or unresolved accounts for an independent callback.

Check a New Supplier Account

Validate a proposed IBAN, disclose the missing historical comparison, and identify independent confirmation steps before any payment.

Review Conflicting Account Drafts

Check each proposed account separately, retain raw tool results, and distinguish invalid accounts from unresolved changes.

이 프롬프트를 사용해 보세요

Check One Proposed IBAN

Check proposed supplier IBAN [new IBAN] using Jithox MCP. I approve sharing it for this check. Report limitations and next steps; change nothing.

Compare With Trusted Records

Compare [new IBAN] with [stored IBAN] from our accounting records. Supplier country is [country]. I approve sharing these details with Jithox. Report both checks.

Review Several Account Drafts

Check proposed accounts [IBAN A] and [IBAN B] separately against trusted [stored IBAN]. I approve Jithox processing. Preserve raw verdicts and flags. Change nothing.

Prepare a Controlled Review

Review [proposed IBAN] against trusted [stored IBAN] using Jithox; sharing is approved. Preserve raw results, unresolved checks, and callback requirements. Never infer completed checks.

모범 사례

Approve external processing of supplier IBANs before using Jithox, and provide only information required by the live tool schemas.
Obtain the stored account and callback number from existing trusted records, never from the change request.
Preserve actual tool results and unresolved checks; maintain the payment hold until independent confirmation is completed.

피하기

Treating a valid checksum or no_change result as payment approval or proof of account ownership.
Using the change email as the trusted source for the old account or callback number.
Running the example curl commands or presenting conditional examples as completed live checks.

자주 묻는 질문

Does this skill pay invoices or update supplier records?

No. It reports checks and next steps without making payments or changing vendor records.

Does a valid IBAN prove that the supplier owns the account?

No. IBAN validation establishes structure and checksum only, not account existence or ownership.

Which external service receives the account details?

The native checks use the Jithox MCP service at jithox.com. Confirm permission to share supplier IBANs before using it.

What happens when no existing account is available?

The skill omits the old account, discloses the missing comparison, and requires independent confirmation before proceeding.

What happens when a tool call fails?

The result remains unknown, not passed or invalid. The workflow stays verify_first, and the affected check is marked not_run.

Can I run the shell commands in the examples?

Agents must use native MCP tools. The example shell commands are maintainer build checks with public test accounts, not live verification results.

개발자 세부 정보

작성자

victor-emmanuel-c

라이선스

MIT

작성자 버전

v1.0

Skillstore 리비전

버전 안내

작성자가 선언한 버전은 유효한 SemVer가 아닙니다.

리포지토리

https://github.com/victor-emmanuel-c/jithox-mcp/tree/4a878019dc0b25613bd88699fcb707d52726ecd1/skills/verify-bank-detail-change

참조

0be6750e006665680212ad9cbfba1b18e115834a

유지보수 최신성

2026. 10. 5.

사용량

0 다운로드 · 0 조회

파일 구조

📁 references/

📄 examples.md

📄 SKILL.md