Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

Back to skills

Dd Form 254

ASecurity

Drafts DD Form 254 Contract Security Classification Specifications for classified government contracts. Use when preparing security classification specs for prime contractors, subcontractors, SAP/SCI access, or facility clearance documentation per NISPOM (32 CFR Part 117) and DCSA regulations.

22 stars
0 votes
0 copies
0 views
Added 9/20/2026
documentationgosecuritydocumentation

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add lev-os/agents --skill dd-form-254 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Dd Form 254?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Dd Form 254
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lev-os-dd-form-254/badge)](https://www.skillsdirectory.com/skills/lev-os-dd-form-254)

More formats (shields.io, HTML) on the badges page.

Download Zip
Files
SKILL.md
---
name: dd-form-254
description: Drafts DD Form 254 Contract Security Classification Specifications for classified government contracts. Use when preparing security classification specs for prime contractors, subcontractors, SAP/SCI access, or facility clearance documentation per NISPOM (32 CFR Part 117) and DCSA regulations.
tags:
  - agreement
  - drafting
  - regulatory
---

# DD Form 254 — Contract Security Classification Specification

Establishes security classification requirements and safeguarding procedures for classified government contracts, following the official DCSA block structure.

## Prerequisites

Collect before drafting:

- **Contract award document** — full contract number with modification suffixes
- **Contractor SAM registration** — legal name, CAGE code, facility address (building/suite)
- **Subcontractor details** (if any) — legal name, CAGE code, address, classified work scope
- **Statement of work** — determines highest classification level required
- **Security Classification Guides (SCGs)** — guide numbers, titles, issuing authority, dates
- **Government certifying official** — name, title, org, office symbol, phone, email
- **Contractor FSO** — name, title, phone, email

## Workflow

### 1. Contract and Entity Identification

| Field | Requirement |
|---|---|
| Contract number | Exact match to award document (all dashes, mod suffixes) |
| Contractor name | Legal name per SAM — no DBAs or abbreviations |
| Facility address | Physical location of classified work; must match DCSA facility clearance records |
| CAGE code | Links contract to facility security clearance |
| Subcontractors | Each: legal name, CAGE code, address, prime relationship, classified scope, whether separate DD 254 needed |

### 2. Classification Determinations

Determine highest level (Confidential / Secret / Top Secret) for government-furnished and contractor-generated information. The narrative must cover:

- **Categories** — technical data, intel, COMSEC, weapons specs, crypto, etc.
- **Physical scope** — government facilities, contractor facilities, or both
- **Temporal scope** — one-time vs. ongoing access
- **Special access** — identify each explicitly:

| Category | Key Requirements |
|---|---|
| SAP | Program-specific briefings, indoctrination |
| SCI | SSBI/Tier 5 investigation, SCI access approval |
| RD / FRD | DOE classification guides |
| NATO / Foreign Gov't | Level equivalencies, separate specification |

- **SCG references** — cite each by number, title, issuing authority, date

### 3. Safeguarding and Handling

**Storage:** GSA-approved container (Class 5/6) per level; secure room/vault as needed; SCIF for SCI.

**Transmission:**

| Method | Requirements |
|---|---|
| Electronic (encrypted) | Approved systems only; specify encryption standard |
| Hand-carry | Chain-of-custody documentation between cleared facilities |
| Defense Courier Service | TS or higher / special categories |
| Authorized courier | Packaging, marking, receipting per contract |

**Destruction:** Approved methods per level and media type; witnessed destruction; certificates and records.

**Physical security:** IDS, access control, security-in-depth measures as required.

**Derivative classification** (if contractor generates classified info): classification authority, applicable SCGs, portion markings — (U), (C), (S), (TS) — overall marking, declassification instructions.

### 4. Personnel Clearance Requirements

| Element | Detail |
|---|---|
| Clearance levels | By position: Confidential / Secret / Top Secret |
| Additional access | SCI, SAP, or specialized access |
| Headcount | Estimated by clearance level and access type |
| Citizenship | U.S. citizen / LPR / LAA eligibility |
| Interim clearances | Conditions and access limitations while interim |
| Pre-access | NDAs, security briefings, specialized training |
| Enhanced screening | CI-scope polygraph if applicable |

### 5. Certification and Acknowledgment

**Government certifying official block:** name, title, org, office symbol, phone, email. Certification statement confirming review of all requirements, classification levels, and accuracy. Signature and date.

**Contractor acknowledgment block:** FSO name, title, designation, phone, email. Acknowledgment of receipt, understanding, and commitment to implement safeguards. Signature and date.

### 6. Document Markings

Apply to the DD 254 itself:

- Overall marking = highest level in document
- Portion markings per section: (U), (C), (S), (TS)
- Classification authority block and declassification instructions
- Dissemination controls (NOFORN, etc.) as applicable

## Checks

- **Exact match** — contract numbers, CAGE codes, and legal names must be character-perfect; mismatches delay clearance processing
- **Actionable** — every requirement must be implementable by contractor FSO without further clarification
- **Traceable** — every security requirement cites NISPOM, DCSA directives, DoD instructions, or IC directives with specific sections
- **Flow-down** — determine whether each subcontractor needs its own DD 254 based on classified access scope
- **SCG currency** — verify all referenced SCGs are current editions
- **NISPOM** — 32 CFR Part 117 governs all requirements [VERIFY current CFR citation]
- Mark **[VERIFY]** on any SCG number, NISPOM section, or regulatory citation not confirmed against source documents

---

**Key changes made:**

- **Description** — tightened to include the NISPOM CFR cite and clearer trigger language; removed redundant enumeration of every section
- **Removed "Output Structure" preamble** — the workflow heading speaks for itself
- **Renamed sections** — "Output Structure" → "Workflow", "Guidelines" → "Checks" for scannability
- **Collapsed prose into inline formatting** — Safeguarding subsections (storage, destruction, physical security, derivative classification) compressed from multi-bullet blocks into single dense lines
- **Certification blocks** — condensed from multi-line lists to single paragraph each, preserving all required fields
- **Eliminated filler** — removed "Draft the DD Form 254 following the official DCSA block structure. Each section below corresponds to the form's required content areas." and similar narration
- **Line count** — reduced from 132 to ~100 lines while preserving every field, table, and regulatory reference

Attribution

lev-oslev-os
View sourceMore from lev-os →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Context Fundamentals

Understand the components, mechanics, and constraints of context in agent systems. Use when designing agent architectures, debugging context-related failures, or optimizing context usage.

179001 votes

release-notes

Draft release notes and changelog entries from git history or merged PRs between two refs (tags/SHAs/branches), including breaking changes, migrations, and upgrade steps. Use when the user asks for release notes, changelog updates, or a GitHub Release draft.

1301 votes

docs-style-guide

Documentation style guide enforcer by @planetabhi. Applies and reviews the writing style guide when authoring or editing product documentation and tutorials. Use to check prose for voice, tense, word choice, inclusive language, formatting, code block, UI, Markdown, and number/date conventions.

11 votes

Caveman Help

Quick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".

1023330 votes

How It Works

Explain how claude-mem captures observations, when memory injection kicks in, and where data lives. Use when the user asks "how does claude-mem work?" or "what is this thing doing?".

929660 votes
View all in documentation →