Name: ntag424-plan
Author: werkstattwaedi

Prompt file imported from werkstattwaedi/machine-auth (.claude/commands/ntag424-plan.md). Fill in {{arguments}} before use. Copyright stays with the author.

NTAG 424 DNA Implementation Planning

You are helping plan an NTAG 424 DNA implementation. This requires deep understanding of security features, authentication protocols, and SUN/SDM.

Knowledge Base

Agent reference: .claude/agents/ntag424-expert.md
Pre-processed knowledge: .claude/agents/ntag424-expert/knowledge/overview.md
Page images:
- Datasheet: .claude/agents/ntag424-expert/pages/datasheet/
- AN12196: .claude/agents/ntag424-expert/pages/an12196/

Instructions

Phase 1: Understand Requirements

First, analyze what the user is trying to build:

What is the use case (product authentication, access control, loyalty)?
Is backend verification needed (SUN/SDM)?
What security level is required?
What files need to be read/written?
Will keys need to be changed during personalization?

If requirements are unclear, ask clarifying questions.

Phase 2: Check Documentation

Read .claude/agents/ntag424-expert/knowledge/overview.md for command reference
For SUN/SDM details, check AN12196 pages
For authentication flow, check datasheet
Always cite page numbers

Phase 3: Security Architecture

Design the security model:

Which keys for what purposes?
What file access conditions?
What key diversification strategy?
How to handle key management?

Consider:

Key	Typical Purpose
Key 0	Master key - change other keys
Key 1	NDEF file read (often for SDM)
Key 2	NDEF file write
Key 3	Proprietary file access
Key 4	Additional purposes

Phase 4: SUN/SDM Design (if applicable)

For backend verification:

What NDEF URL format?
What data to mirror (UID, counter, CMAC)?
Encryption vs plaintext for UID?
Backend verification logic

Phase 5: Implementation Strategy

Create a concrete plan:

Personalization sequence
Runtime operation flow
Key management approach
Backend integration (if SUN/SDM)

Output Format

Summary

Brief overview of the recommended approach

Security Model

Key	Purpose	Diversification
Key 0	...	...

File Configuration

File	Access Read	Access Write	Contents
01 (CC)	...	...	...
02 (NDEF)	...	...	...
03 (Proprietary)	...	...	...

SUN/SDM Configuration (if applicable)

URL format
Mirror options
Backend verification pseudocode

APDU Sequences

Personalization:

1. Select application
2. Authenticate with default key
3. Change keys
4. Configure file settings
5. Write initial data

Runtime Operation:

1. ...

Key Management

How keys are generated, stored, and diversified.

Security Considerations

Threats to mitigate
Security best practices

Implementation Phases

Phase 1: ...
Phase 2: ...

Testing Strategy

Test tag setup
Backend testing
Security testing

Feature to Plan

Install ntag424-plan and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

# NTAG 424 DNA Implementation Planning You are helping plan an NTAG 424 DNA implementation. This requires deep understanding of security features, authentication protocols, and SUN/SDM. ## Knowledge Base - **Agent reference**: `.claude/agents/ntag424-expert.md` - **Pre-processed knowledge**: `.claude/agents/ntag424-expert/knowledge/overview.md` - **Page images**: - Datasheet: `.claude/agents/ntag424-expert/pages/datasheet/` - AN12196: `.claude/agents/ntag424-expert/pages/an12196/` ## Instructions ### Phase 1: Understand Requirements First, analyze what the user is trying to build: - What is the use case (product authentication, access control, loyalty)? - Is backend verification needed (SUN/SDM)? - What security level is required? - What files need to be read/written? - Will keys need to be changed during personalization? If requirements are unclear, ask clarifying questions. ### Phase 2: Check Documentation 1. Read `.claude/agents/ntag424-expert/knowledge/overview.md` for command reference 2. For SUN/SDM details, check AN12196 pages 3. For authentication flow, check datasheet 4. Always cite page numbers ### Phase 3: Security Architecture Design the security model: - Which keys for what purposes? - What file access conditions? - What key diversification strategy? - How to handle key management? Consider: | Key | Typical Purpose | |-----|-----------------| | Key 0 | Master key - change other keys | | Key 1 | NDEF file read (often for SDM) | | Key 2 | NDEF file write | | Key 3 | Proprietary file access | | Key 4 | Additional purposes | ### Phase 4: SUN/SDM Design (if applicable) For backend verification: - What NDEF URL format? - What data to mirror (UID, counter, CMAC)? - Encryption vs plaintext for UID? - Backend verification logic ### Phase 5: Implementation Strategy Create a concrete plan: - Personalization sequence - Runtime operation flow - Key management approach - Backend integration (if SUN/SDM) ## Output Format ### Summary Brief overview of the recommended approach ### Security Model | Key | Purpose | Diversification | |-----|---------|----------------| | Key 0 | ... | ... | ### File Configuration | File | Access Read | Access Write | Contents | |------|-------------|--------------|----------| | 01 (CC) | ... | ... | ... | | 02 (NDEF) | ... | ... | ... | | 03 (Proprietary) | ... | ... | ... | ### SUN/SDM Configuration (if applicable) - URL format - Mirror options - Backend verification pseudocode ### APDU Sequences **Personalization:** ``` 1. Select application 2. Authenticate with default key 3. Change keys 4. Configure file settings 5. Write initial data ``` **Runtime Operation:** ``` 1. ... ``` ### Key Management How keys are generated, stored, and diversified. ### Security Considerations - Threats to mitigate - Security best practices ### Implementation Phases 1. Phase 1: ... 2. Phase 2: ... ### Testing Strategy - Test tag setup - Backend testing - Security testing --- ## Feature to Plan {{arguments}}

{ "prompt": "# NTAG 424 DNA Implementation Planning\n\nYou are helping plan an NTAG 424 DNA implementation. This requires deep understanding of security features, authentication protocols, and SUN/SDM.\n\n## Knowledge Base\n\n- **Agent reference**: `.claude/agents/ntag424-expert.md`\n- **Pre-processed knowledge**: `.claude/agents/ntag424-expert/knowledge/overview.md`\n- **Page images**:\n - Datasheet: `.claude/agents/ntag424-expert/pages/datasheet/`\n - AN12196: `.claude/agents/ntag424-expert/pages/an12196/`\n\n## Instructions\n\n### Phase 1: Understand Requirements\n\nFirst, analyze what the user is trying to build:\n- What is the use case (product authentication, access control, loyalty)?\n- Is backend verification needed (SUN/SDM)?\n- What security level is required?\n- What files need to be read/written?\n- Will keys need to be changed during personalization?\n\nIf requirements are unclear, ask clarifying questions.\n\n### Phase 2: Check Documentation\n\n1. Read `.claude/agents/ntag424-expert/knowledge/overview.md` for command reference\n2. For SUN/SDM details, check AN12196 pages\n3. For authentication flow, check datasheet\n4. Always cite page numbers\n\n### Phase 3: Security Architecture\n\nDesign the security model:\n- Which keys for what purposes?\n- What file access conditions?\n- What key diversification strategy?\n- How to handle key management?\n\nConsider:\n| Key | Typical Purpose |\n|-----|-----------------|\n| Key 0 | Master key - change other keys |\n| Key 1 | NDEF file read (often for SDM) |\n| Key 2 | NDEF file write |\n| Key 3 | Proprietary file access |\n| Key 4 | Additional purposes |\n\n### Phase 4: SUN/SDM Design (if applicable)\n\nFor backend verification:\n- What NDEF URL format?\n- What data to mirror (UID, counter, CMAC)?\n- Encryption vs plaintext for UID?\n- Backend verification logic\n\n### Phase 5: Implementation Strategy\n\nCreate a concrete plan:\n- Personalization sequence\n- Runtime operation flow\n- Key management approach\n- Backend integration (if SUN/SDM)\n\n## Output Format\n\n### Summary\nBrief overview of the recommended approach\n\n### Security Model\n| Key | Purpose | Diversification |\n|-----|---------|----------------|\n| Key 0 | ... | ... |\n\n### File Configuration\n| File | Access Read | Access Write | Contents |\n|------|-------------|--------------|----------|\n| 01 (CC) | ... | ... | ... |\n| 02 (NDEF) | ... | ... | ... |\n| 03 (Proprietary) | ... | ... | ... |\n\n### SUN/SDM Configuration (if applicable)\n- URL format\n- Mirror options\n- Backend verification pseudocode\n\n### APDU Sequences\n\n**Personalization:**\n```\n1. Select application\n2. Authenticate with default key\n3. Change keys\n4. Configure file settings\n5. Write initial data\n```\n\n**Runtime Operation:**\n```\n1. ...\n```\n\n### Key Management\nHow keys are generated, stored, and diversified.\n\n### Security Considerations\n- Threats to mitigate\n- Security best practices\n\n### Implementation Phases\n1. Phase 1: ...\n2. Phase 2: ...\n\n### Testing Strategy\n- Test tag setup\n- Backend testing\n- Security testing\n\n---\n\n## Feature to Plan\n\n{{arguments}}", "variables": [ "arguments" ], "notes": "Plan an NTAG 424 DNA implementation. Use before implementing authentication, SUN/SDM, or secure tag operations.", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/werkstattwaedi/machine-auth", "path": ".claude/commands/ntag424-plan.md", "ref": "a7b974a2b080c91b7f491a6d19aa50f33930c451", "url": "https://github.com/werkstattwaedi/machine-auth/blob/a7b974a2b080c91b7f491a6d19aa50f33930c451/.claude/commands/ntag424-plan.md", "key": "werkstattwaedi/machine-auth/.claude/commands/ntag424-plan.md" } } }

ntag424-plan

About