Навыки 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-агентов

Используйте эти ссылки, когда AI-агенту, crawler или script нужен чистый контекст вместо полной страницы.

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 • 05.10.2026 Открыть версионный отчет

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

Актуальность поддержки

05.10.2026

Использование

0 загрузок · 0 просмотров

Структура файлов

📁 references/

📄 examples.md

📄 SKILL.md