技能 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 合格

使用我的智能体安装

将此请求复制给你的智能体，其中包含权威 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.

你的智能体仍应展示其计划，并按安全策略请求必要确认。

Agent 可读资源

当 AI Agent、爬虫或脚本需要干净上下文，而不是读取完整页面时，请使用这些链接。

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