Results for “warden-protocol”

Guardian of V.A.I.R.E. quality standards (Value/Agency/Identity/Resilience/Echo). Handles pre-release evaluation, scorecard assessment, and pass/fail determination. Use when UX quality gates are needed. Does not write code.

Guides implementing authentication, authorization, input validation, and OWASP Top 10 prevention with secure code patterns and validation checkpoints.

Centralized JSON validation for AGENT_SUCCESS_CRITERIA with defensive parsing and injection attack prevention (CVSS 8.2)

Consolidates 89 high-integrity SOPs for the Full department of the Galyarder Framework, covering adapter creation, execution protocols, and multi-agent hygiene.

Decomposes an approved specification into dependency-aware waves and atomic executable tasks with exact file scope, test-first actions, verification commands, and an execution gate.

AI safety and responsible AI practices

Apply Optionals, Protocols, Extensions, and Type Safety patterns in Swift. Use when working with Swift Optionals, Protocols, Extensions, or type-safe APIs.

Guides the creation, editing, and verification of agent skills using a test-driven development approach, with structured documentation and quality gates.

Prevents destructive operations on production systems and restricts file edits to a specific directory when running agents autonomously.

Utilize Shodan, the search engine for Internet-connected devices, to discover exposed assets, vulnerable ports, default credentials, and specific infrastructure configurations using advanced search queries (dorks).

Strict test-first gate only when explicitly requested or required by repository policy. Do not use for ordinary practical testing.

Drafts GDPR Article 28-compliant Data Processing Addenda with schedules ready for execution. Use when drafting or updating a DPA, vendor GDPR addendum, controller-processor agreement, or data protection addendum involving sub-processors, breach notification, audits, international transfers, or SCCs.

Provides 89 standard operating procedures for the Galyarder department, covering agent adapters, execution protocols, and multi-agent hygiene.

Use to define handoff standards for support transfers and to measure whether context survives the handoff — cold vs warm, required fields, and re-ask rate after transfer. Trigger for "transfer protocol", "warm handoff", "customers repeat themselves after transfer", "ping-pong between teams", "what should agents include when transferring", handoff quality, or re-ask rate after escalation.