المهارات 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 كافٍ

التثبيت باستخدام Agent لدي

انسخ هذا الطلب إلى Agent لديك. يتضمن صفحة Skill المعتمدة وملف manifest.

طلب الوكيل

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 عرض خطته وطلب أي تأكيد تفرضه سياسة الأمان.

موارد مهيّأة لـ Agents

استخدم هذه الروابط عندما يحتاج AI Agent أو 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 • ٥‏/١٠‏/٢٠٢٦ فتح التقرير المرتبط بالإصدار

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 الأدلة من دون أن تقرر ما إذا كانت هذه المهارة آمنة.

فتح التقرير المرتبط بالإصدار

نسخ رابط التقرير

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

حداثة الصيانة

٥‏/١٠‏/٢٠٢٦

الاستخدام

0 تنزيلات · 0 مشاهدات

بنية الملفات

📁 references/

📄 examples.md

📄 SKILL.md