code-security

Enforce deterministic, verifiable, and secure coding patterns for foundational code.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/nbiish/native-psionic-programs --skill code-security-nbiish
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-security
Source: https://github.com/nbiish/native-psionic-programs/tree/main/.agents/skills/code-security
Command: npx skills add https://github.com/nbiish/native-psionic-programs --skill code-security-nbiish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deterministic, verifiable, and secure foundational code is essential for safety-critical software; this skill provides the patterns, standards, and concrete examples to reduce risk and enable auditable behavior.

Core Features & Use Cases

  • Determinism & containment: enforce boundaries and predictable runtime behavior.
  • Universal code standards: cyclomatic complexity limits, pure functions, and reproducible builds.
  • Cryptographic patterns & secure design: AES-GCM, Argon2id hashing, HKDF, and TLS best practices for secure data handling.
  • Use Case: teams building infrastructure, security-sensitive components, or mission-critical services use this skill to harden code from the ground up.

Quick Start

Start by applying the deterministic and secure coding guidelines to your core modules and incrementally integrate validated cryptographic patterns.

Frequently Asked Questions about code-security

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce deterministic runtime behavior and containment in secure code?

Deterministic runtime behavior and containment in secure code are enforced by applying strict boundary enforcement patterns and predictable runtime constraints. This approach guarantees reliable and auditable software execution by preventing unpredictable state changes.

What cryptographic patterns should I use for secure data handling?

Validated cryptographic patterns for secure data handling include AES-GCM encryption, Argon2id hashing, HKDF key derivation, and TLS best practices. These standards ensure verifiable and secure foundational code for mission-critical services.

How do I implement strict input validation and reproducible builds?

Strict input validation and reproducible builds are implemented by applying universal code standards like cyclomatic complexity limits and pure functions. This combination enables verifiable design patterns and deterministic infrastructure behavior.

Does this approach work for hardening infrastructure and mission-critical services?

Yes, this approach works for hardening infrastructure and mission-critical services. It provides the patterns and concrete examples needed to reduce risk and enable auditable behavior in safety-critical software components.