N

nha-in/abdm-integrators-assistant

Copy page

Run /abdm-start after installing: it says what this plugin does, offers prompts to start from, and asks what you are building. Agent skills for ABDM integration from the ABDM Developer Portal, compiled from the Catalogue. One skill per module: abdm-gateway, abdm-m1 to abdm-m4 on the provider side, abdm-p1 (P1 Registration and login), abdm-p2 (P2 Consents Management), abdm-p3 (P3 Subscription) and abdm-p4 (P4 Locker) inside a PHR application, abdm-scan-and-register, abdm-scan-and-pay, abdm-record-share, and abdm-fhir for NRCES compliant bundles. Each carries its work as sections that load on demand: scaffold builds the module flow by flow against the sandbox, integrate holds the calls and headers, debug lists every code the specification's examples return and walks a failed call to a fix proved by the original call succeeding. Every step names the operation it came from. Commands open the work from the terminal: /abdm-preflight checks what must be true before any call, /abdm-prove-encryption settles the RSA padding before a flow is built on it, and /abdm-decode-error turns a response into its code and the most likely fix. /abdm-build resumes a module one functionality at a time from the tracker in INTEGRATION-PLAN.md, and /abdm-test runs every mandatory NHA test case on one final build; both start with a survey of the machine. M1 is built per functionality; other modules follow. Three agents plan above the skills: abdm-integration-agent takes a goal such as becoming an HIU and sequences the module skills by what each requires and produces, abdm-call-debugger takes one failing call to a fix and verifies it by the original call succeeding, and fhir-compliance-agent validates and repairs the bundles a codebase emits until the validator passes. Every skill declares its domain, what it requires and produces, and that it never orchestrates.