gabbe-kit 1.0.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LICENSE +25 -0
- package/LICENSE-CODE +202 -0
- package/README.md +817 -0
- package/agents/AGENTS.md +542 -0
- package/agents/CONSTITUTION.md +188 -0
- package/agents/guides/00-index.md +142 -0
- package/agents/guides/ai/a2ui-protocols.md +71 -0
- package/agents/guides/ai/actor-agent-frameworks.md +82 -0
- package/agents/guides/ai/agent-communication.md +146 -0
- package/agents/guides/ai/agent-identity-trust.md +69 -0
- package/agents/guides/ai/agent-only-cognition.md +73 -0
- package/agents/guides/ai/agent-only-swarms.md +70 -0
- package/agents/guides/ai/agent-operating-ergonomics.md +52 -0
- package/agents/guides/ai/agent-ui.md +106 -0
- package/agents/guides/ai/ai-agentic.md +309 -0
- package/agents/guides/ai/beyond-llms.md +60 -0
- package/agents/guides/ai/dynamic-capability-loading.md +121 -0
- package/agents/guides/ai/gabbe-innovations.md +111 -0
- package/agents/guides/ai/model-customization-decisions.md +78 -0
- package/agents/guides/ai/multi-agent-systems.md +85 -0
- package/agents/guides/ai/self-evolving-skills.md +137 -0
- package/agents/guides/ai/self-healing-summary.md +21 -0
- package/agents/guides/ai/visual-mcp-integration.md +106 -0
- package/agents/guides/architecture/api-standards.md +61 -0
- package/agents/guides/architecture/blockchain-dlt.md +36 -0
- package/agents/guides/architecture/critical-systems-arch.md +66 -0
- package/agents/guides/architecture/event-driven-architecture.md +39 -0
- package/agents/guides/architecture/microservices.md +292 -0
- package/agents/guides/architecture/monolith.md +303 -0
- package/agents/guides/architecture/orchestration.md +75 -0
- package/agents/guides/architecture/system-qualities.md +51 -0
- package/agents/guides/architecture/system-scalability.md +47 -0
- package/agents/guides/architecture/systems-architecture.md +506 -0
- package/agents/guides/data/semantic-web.md +23 -0
- package/agents/guides/data/sql-nosql.md +305 -0
- package/agents/guides/industry/engineering-standards.md +36 -0
- package/agents/guides/industry/global-standards.md +24 -0
- package/agents/guides/industry/healthcare-fhir.md +33 -0
- package/agents/guides/industry/industrial-iot.md +33 -0
- package/agents/guides/industry/telecom-networks.md +34 -0
- package/agents/guides/languages/c-sharp.md +66 -0
- package/agents/guides/languages/go-lang.md +251 -0
- package/agents/guides/languages/java.md +73 -0
- package/agents/guides/languages/js-ts-nodejs.md +361 -0
- package/agents/guides/languages/nodejs-advanced.md +56 -0
- package/agents/guides/languages/php-laravel.md +376 -0
- package/agents/guides/languages/python-fastapi-ai.md +257 -0
- package/agents/guides/languages/rust.md +73 -0
- package/agents/guides/ops/compliance-audit.md +177 -0
- package/agents/guides/ops/cost-optimization.md +57 -0
- package/agents/guides/ops/dev-environments.md +67 -0
- package/agents/guides/ops/dev-workflow.md +44 -0
- package/agents/guides/ops/gabbe-cli-workflows.md +252 -0
- package/agents/guides/ops/production-health.md +62 -0
- package/agents/guides/ops/troubleshooting-guide.md +69 -0
- package/agents/guides/patterns/agentic-design-patterns.md +308 -0
- package/agents/guides/patterns/agentic-patterns.md +43 -0
- package/agents/guides/patterns/ai-native-scenarios.md +71 -0
- package/agents/guides/patterns/autonomous-swarm-patterns.md +42 -0
- package/agents/guides/patterns/design-patterns.md +68 -0
- package/agents/guides/patterns/enterprise-migration-scenario.md +58 -0
- package/agents/guides/patterns/enterprise-patterns.md +56 -0
- package/agents/guides/patterns/software-design-patterns.md +106 -0
- package/agents/guides/patterns/time-complexity-analysis.md +116 -0
- package/agents/guides/planning/product-requirements.md +407 -0
- package/agents/guides/planning/strategic-analysis.md +98 -0
- package/agents/guides/planning/visual-product-specs.md +162 -0
- package/agents/guides/principles/clean-code-standards.md +51 -0
- package/agents/guides/principles/computing-foundations.md +87 -0
- package/agents/guides/principles/diagramming-standards.md +568 -0
- package/agents/guides/principles/evaluation-strategy.md +103 -0
- package/agents/guides/principles/future-tech.md +35 -0
- package/agents/guides/principles/human-agent-collaboration.md +54 -0
- package/agents/guides/principles/legacy-tech.md +61 -0
- package/agents/guides/principles/mathematical-foundations.md +103 -0
- package/agents/guides/principles/modeling-methods.md +97 -0
- package/agents/guides/principles/no-code-integration.md +84 -0
- package/agents/guides/principles/testing-strategy.md +97 -0
- package/agents/guides/principles/visual-design-system.md +44 -0
- package/agents/guides/processes/RARV_CYCLE.md +262 -0
- package/agents/guides/processes/extension-protocol.md +183 -0
- package/agents/guides/processes/full-system-lifecycle.md +47 -0
- package/agents/guides/processes/knowledge-integration.md +82 -0
- package/agents/guides/processes/loki-sdlc-phases.md +446 -0
- package/agents/guides/product/green-software.md +38 -0
- package/agents/guides/product/sustainability-checks.md +29 -0
- package/agents/guides/security/ai-risk-standards-map.md +98 -0
- package/agents/guides/security/api-security.md +51 -0
- package/agents/guides/security/cryptography-standards.md +38 -0
- package/agents/guides/security/privacy-data-protection.md +41 -0
- package/agents/guides/security/secure-architecture.md +43 -0
- package/agents/guides/security/threat-modeling.md +46 -0
- package/agents/memory/AUDIT_LOG.md +48 -0
- package/agents/memory/CONTINUITY.md +49 -0
- package/agents/memory/PROJECT_STATE.md +134 -0
- package/agents/memory/RESUME_POINTER.md +15 -0
- package/agents/memory/episodic/DECISION_LOG_TEMPLATE.md +104 -0
- package/agents/memory/semantic/PROJECT_KNOWLEDGE_TEMPLATE.md +194 -0
- package/agents/memory/semantic/VECTOR_DB_CONFIG_TEMPLATE.json +46 -0
- package/agents/personas/00-index.md +148 -0
- package/agents/personas/biz-compliance.md +112 -0
- package/agents/personas/biz-legal.md +131 -0
- package/agents/personas/eng-api.md +110 -0
- package/agents/personas/eng-backend.md +113 -0
- package/agents/personas/eng-data.md +50 -0
- package/agents/personas/eng-database.md +95 -0
- package/agents/personas/eng-frontend.md +75 -0
- package/agents/personas/eng-infra.md +105 -0
- package/agents/personas/eng-messaging.md +50 -0
- package/agents/personas/eng-ml.md +50 -0
- package/agents/personas/eng-mobile.md +75 -0
- package/agents/personas/eng-perf.md +90 -0
- package/agents/personas/eng-qa.md +125 -0
- package/agents/personas/eng-tooling.md +49 -0
- package/agents/personas/ops-compliance.md +109 -0
- package/agents/personas/ops-cost.md +92 -0
- package/agents/personas/ops-devops.md +85 -0
- package/agents/personas/ops-incident.md +123 -0
- package/agents/personas/ops-monitor.md +89 -0
- package/agents/personas/ops-release.md +91 -0
- package/agents/personas/ops-security.md +104 -0
- package/agents/personas/ops-sre.md +85 -0
- package/agents/personas/orch-coordinator.md +140 -0
- package/agents/personas/orch-judge.md +135 -0
- package/agents/personas/orch-planner.md +114 -0
- package/agents/personas/orch-researcher.md +165 -0
- package/agents/personas/prod-architect.md +110 -0
- package/agents/personas/prod-design.md +112 -0
- package/agents/personas/prod-ethicist.md +50 -0
- package/agents/personas/prod-integration.md +120 -0
- package/agents/personas/prod-pm.md +115 -0
- package/agents/personas/prod-product-ops.md +128 -0
- package/agents/personas/prod-research.md +49 -0
- package/agents/personas/prod-safety-engineer.md +28 -0
- package/agents/personas/prod-tech-lead.md +119 -0
- package/agents/personas/ui-design.md +81 -0
- package/agents/scripts/check_skills_docs.py +120 -0
- package/agents/scripts/compile_skills.py +284 -0
- package/agents/scripts/comprehensive_checker.py +187 -0
- package/agents/scripts/dump-context.sh +37 -0
- package/agents/scripts/eval_skills.py +268 -0
- package/agents/scripts/preflight_summary.sh +80 -0
- package/agents/scripts/report_duplicates.py +125 -0
- package/agents/scripts/setup-context.ps1 +250 -0
- package/agents/scripts/setup-context.sh +398 -0
- package/agents/scripts/state_export.sh +84 -0
- package/agents/scripts/state_import.sh +99 -0
- package/agents/scripts/validate_integrity.py +98 -0
- package/agents/scripts/validate_links.py +96 -0
- package/agents/scripts/validate_methodology_graph.py +194 -0
- package/agents/scripts/validate_skills.py +81 -0
- package/agents/scripts/verify_e2e_init_flows.py +246 -0
- package/agents/scripts/verify_setup_simulation.py +104 -0
- package/agents/scripts/verify_triggers_and_mcps.py +159 -0
- package/agents/scripts/verify_use_cases.py +498 -0
- package/agents/skills/00-index.md +322 -0
- package/agents/skills/ai/a2ui-protocols.skill.md +31 -0
- package/agents/skills/ai/actor-agent-frameworks.skill.md +31 -0
- package/agents/skills/ai/agent-communication.skill.md +36 -0
- package/agents/skills/ai/agent-ui.skill.md +31 -0
- package/agents/skills/ai/autonomous-swarm-patterns.skill.md +31 -0
- package/agents/skills/ai/beyond-llms.skill.md +31 -0
- package/agents/skills/ai/context-engineering.skill.md +79 -0
- package/agents/skills/ai/llm-as-judge.skill.md +97 -0
- package/agents/skills/ai/multi-agent-systems.skill.md +31 -0
- package/agents/skills/ai/rag-evaluation.skill.md +93 -0
- package/agents/skills/ai/reasoning-patterns.skill.md +125 -0
- package/agents/skills/architecture/adaptive-architecture.skill.md +51 -0
- package/agents/skills/architecture/api-design.skill.md +92 -0
- package/agents/skills/architecture/api-standards.skill.md +31 -0
- package/agents/skills/architecture/arch-debt.skill.md +180 -0
- package/agents/skills/architecture/arch-design.skill.md +304 -0
- package/agents/skills/architecture/arch-patterns.skill.md +52 -0
- package/agents/skills/architecture/arch-review.skill.md +326 -0
- package/agents/skills/architecture/architecture-governance.skill.md +62 -0
- package/agents/skills/architecture/attribute-driven-design.skill.md +108 -0
- package/agents/skills/architecture/blockchain-dlt.skill.md +28 -0
- package/agents/skills/architecture/compatibility-design.skill.md +51 -0
- package/agents/skills/architecture/critical-systems-arch.skill.md +31 -0
- package/agents/skills/architecture/design-patterns.skill.md +59 -0
- package/agents/skills/architecture/diagramming.skill.md +380 -0
- package/agents/skills/architecture/domain-model.skill.md +294 -0
- package/agents/skills/architecture/enterprise-migration-scenario.skill.md +31 -0
- package/agents/skills/architecture/enterprise-patterns.skill.md +31 -0
- package/agents/skills/architecture/error-handling-strategy.skill.md +58 -0
- package/agents/skills/architecture/event-driven-architecture.skill.md +31 -0
- package/agents/skills/architecture/event-governance.skill.md +55 -0
- package/agents/skills/architecture/fitness-functions.skill.md +111 -0
- package/agents/skills/architecture/graphql-schema.skill.md +64 -0
- package/agents/skills/architecture/legacy-modernization.skill.md +51 -0
- package/agents/skills/architecture/microservices.skill.md +31 -0
- package/agents/skills/architecture/middleware-design.skill.md +59 -0
- package/agents/skills/architecture/monolith.skill.md +31 -0
- package/agents/skills/architecture/realtime-comm.skill.md +52 -0
- package/agents/skills/architecture/state-management.skill.md +72 -0
- package/agents/skills/architecture/system-qualities.skill.md +31 -0
- package/agents/skills/architecture/system-scalability.skill.md +31 -0
- package/agents/skills/architecture/systems-architecture.skill.md +31 -0
- package/agents/skills/architecture/visual-whiteboarding.skill.md +33 -0
- package/agents/skills/brain/README.md +70 -0
- package/agents/skills/brain/active-inference.skill.md +74 -0
- package/agents/skills/brain/brain-mode.skill.md +125 -0
- package/agents/skills/brain/cognitive-architectures.skill.md +53 -0
- package/agents/skills/brain/cognitive-testing.skill.md +62 -0
- package/agents/skills/brain/consciousness-loop.skill.md +68 -0
- package/agents/skills/brain/cost-benefit-router.skill.md +89 -0
- package/agents/skills/brain/episodic-consolidation.skill.md +43 -0
- package/agents/skills/brain/epistemology-knowledge.skill.md +54 -0
- package/agents/skills/brain/global-workspace.skill.md +77 -0
- package/agents/skills/brain/learning-adaptation.skill.md +68 -0
- package/agents/skills/brain/loki-mode.skill.md +267 -0
- package/agents/skills/brain/neuroscience-foundations.skill.md +52 -0
- package/agents/skills/brain/scripts/active_inference_loop.py +92 -0
- package/agents/skills/brain/scripts/cognition_test.py +80 -0
- package/agents/skills/brain/scripts/global_workspace.py +104 -0
- package/agents/skills/brain/self-improvement.skill.md +80 -0
- package/agents/skills/brain/sensory-motor.skill.md +61 -0
- package/agents/skills/brain/sequential-thinking.skill.md +48 -0
- package/agents/skills/brain/working-memory.skill.md +47 -0
- package/agents/skills/coding/agent-trajectory-eval.skill.md +92 -0
- package/agents/skills/coding/artisan-commands.skill.md +52 -0
- package/agents/skills/coding/browser-tdd.skill.md +131 -0
- package/agents/skills/coding/chaos-fault-injection.skill.md +116 -0
- package/agents/skills/coding/ci-autofix.skill.md +53 -0
- package/agents/skills/coding/clean-coder.skill.md +58 -0
- package/agents/skills/coding/code-review.skill.md +100 -0
- package/agents/skills/coding/debug.skill.md +100 -0
- package/agents/skills/coding/documentation.skill.md +149 -0
- package/agents/skills/coding/eval-driven-development.skill.md +107 -0
- package/agents/skills/coding/evals/code-review.eval.yaml +29 -0
- package/agents/skills/coding/excalidraw.skill.md +90 -0
- package/agents/skills/coding/file-processing.skill.md +55 -0
- package/agents/skills/coding/git-workflow.skill.md +153 -0
- package/agents/skills/coding/metamorphic-testing.skill.md +113 -0
- package/agents/skills/coding/mobile-dev.skill.md +41 -0
- package/agents/skills/coding/nodejs-expert.skill.md +23 -0
- package/agents/skills/coding/output-validation.skill.md +57 -0
- package/agents/skills/coding/pbt-strategy.skill.md +117 -0
- package/agents/skills/coding/performant-ai.skill.md +62 -0
- package/agents/skills/coding/performant-go.skill.md +61 -0
- package/agents/skills/coding/performant-laravel.skill.md +70 -0
- package/agents/skills/coding/performant-nodejs.skill.md +67 -0
- package/agents/skills/coding/performant-php.skill.md +53 -0
- package/agents/skills/coding/performant-python.skill.md +62 -0
- package/agents/skills/coding/refactor.skill.md +124 -0
- package/agents/skills/coding/secure-coding.skill.md +57 -0
- package/agents/skills/coding/sketch-to-diagram.skill.md +106 -0
- package/agents/skills/coding/spec-driven-development.skill.md +110 -0
- package/agents/skills/coding/tdd-cycle.skill.md +92 -0
- package/agents/skills/coding/testing-strategy.skill.md +74 -0
- package/agents/skills/coding/time-complexity.skill.md +112 -0
- package/agents/skills/coding/tldraw-canvas.skill.md +109 -0
- package/agents/skills/coding/tool-construction.skill.md +47 -0
- package/agents/skills/coding/ui-gen.skill.md +64 -0
- package/agents/skills/coding/vibe-coding.skill.md +63 -0
- package/agents/skills/coding/visual-design.skill.md +65 -0
- package/agents/skills/coordination/agent-interop.skill.md +72 -0
- package/agents/skills/coordination/agent-protocol.skill.md +62 -0
- package/agents/skills/coordination/agent-workflow-patterns.skill.md +123 -0
- package/agents/skills/coordination/agentic-linter.skill.md +134 -0
- package/agents/skills/coordination/agentic-patterns.skill.md +79 -0
- package/agents/skills/coordination/meta-optimize.skill.md +62 -0
- package/agents/skills/coordination/meta-prompting.skill.md +46 -0
- package/agents/skills/coordination/multi-agent-orch.skill.md +78 -0
- package/agents/skills/coordination/persona-selector.skill.md +78 -0
- package/agents/skills/coordination/self-optimize.skill.md +81 -0
- package/agents/skills/coordination/swarm-consensus.skill.md +52 -0
- package/agents/skills/core/agent-analytics.skill.md +74 -0
- package/agents/skills/core/audit-trail.skill.md +122 -0
- package/agents/skills/core/clarify.skill.md +89 -0
- package/agents/skills/core/emerging-tech.skill.md +52 -0
- package/agents/skills/core/empirical-methods.skill.md +101 -0
- package/agents/skills/core/evals/clarify.eval.yaml +29 -0
- package/agents/skills/core/evals/integrity-check.eval.yaml +23 -0
- package/agents/skills/core/evals/research.eval.yaml +23 -0
- package/agents/skills/core/final-review.skill.md +66 -0
- package/agents/skills/core/integrity-check.skill.md +149 -0
- package/agents/skills/core/knowledge-connect.skill.md +77 -0
- package/agents/skills/core/knowledge-gap.skill.md +123 -0
- package/agents/skills/core/preflight.skill.md +106 -0
- package/agents/skills/core/research.skill.md +107 -0
- package/agents/skills/core/retrospective.skill.md +59 -0
- package/agents/skills/core/sdlc-checkpoint.skill.md +151 -0
- package/agents/skills/core/self-heal.skill.md +163 -0
- package/agents/skills/core/session-resume.skill.md +125 -0
- package/agents/skills/core/skills-registry.skill.md +65 -0
- package/agents/skills/core/state-portability.skill.md +89 -0
- package/agents/skills/core/state-preserve.skill.md +76 -0
- package/agents/skills/core/system-lifecycle.skill.md +51 -0
- package/agents/skills/core/update-scan.skill.md +92 -0
- package/agents/skills/data/data-engineering.skill.md +56 -0
- package/agents/skills/data/data-governance.skill.md +49 -0
- package/agents/skills/data/db-migration.skill.md +136 -0
- package/agents/skills/data/semantic-web.skill.md +28 -0
- package/agents/skills/data/sql-optimization.skill.md +78 -0
- package/agents/skills/industry/engineering-standards.skill.md +31 -0
- package/agents/skills/industry/global-standards.skill.md +30 -0
- package/agents/skills/industry/healthcare-fhir.skill.md +28 -0
- package/agents/skills/industry/industrial-iot.skill.md +30 -0
- package/agents/skills/industry/telecom-networks.skill.md +30 -0
- package/agents/skills/ops/caching-strategy.skill.md +77 -0
- package/agents/skills/ops/capacity-planning.skill.md +67 -0
- package/agents/skills/ops/cloud-deploy.skill.md +55 -0
- package/agents/skills/ops/configuration-management.skill.md +107 -0
- package/agents/skills/ops/cost-optimization.skill.md +39 -0
- package/agents/skills/ops/decommission-sunset.skill.md +64 -0
- package/agents/skills/ops/dependency-lifecycle.skill.md +63 -0
- package/agents/skills/ops/deployment.skill.md +217 -0
- package/agents/skills/ops/dev-environments.skill.md +31 -0
- package/agents/skills/ops/dev-workflow.skill.md +28 -0
- package/agents/skills/ops/docker-dev.skill.md +52 -0
- package/agents/skills/ops/enterprise-integration.skill.md +53 -0
- package/agents/skills/ops/feature-flag-management.skill.md +59 -0
- package/agents/skills/ops/incident-response.skill.md +40 -0
- package/agents/skills/ops/infra-devops.skill.md +53 -0
- package/agents/skills/ops/k8s-dev.skill.md +51 -0
- package/agents/skills/ops/memory-optimization.skill.md +45 -0
- package/agents/skills/ops/observability-stack-setup.skill.md +62 -0
- package/agents/skills/ops/performance-audit.skill.md +178 -0
- package/agents/skills/ops/performance-optimization.skill.md +51 -0
- package/agents/skills/ops/production-health.skill.md +85 -0
- package/agents/skills/ops/production-verifier.skill.md +50 -0
- package/agents/skills/ops/queue-management.skill.md +52 -0
- package/agents/skills/ops/release-management.skill.md +39 -0
- package/agents/skills/ops/release-validation.skill.md +51 -0
- package/agents/skills/ops/reliability-sre.skill.md +51 -0
- package/agents/skills/ops/runbook-authoring.skill.md +64 -0
- package/agents/skills/ops/system-benchmark.skill.md +69 -0
- package/agents/skills/ops/tech-debt.skill.md +143 -0
- package/agents/skills/ops/troubleshooting-guide.skill.md +31 -0
- package/agents/skills/product/accessibility.skill.md +143 -0
- package/agents/skills/product/adr-writer.skill.md +110 -0
- package/agents/skills/product/business-case.skill.md +70 -0
- package/agents/skills/product/change-management.skill.md +90 -0
- package/agents/skills/product/decompose.skill.md +75 -0
- package/agents/skills/product/design-thinking.skill.md +62 -0
- package/agents/skills/product/estimation-sizing.skill.md +87 -0
- package/agents/skills/product/evals/spec-writer.eval.yaml +22 -0
- package/agents/skills/product/financial-governance.skill.md +88 -0
- package/agents/skills/product/green-software.skill.md +46 -0
- package/agents/skills/product/ideation-facilitation.skill.md +87 -0
- package/agents/skills/product/market-analysis.skill.md +56 -0
- package/agents/skills/product/opportunity-assessment.skill.md +89 -0
- package/agents/skills/product/product-analytics.skill.md +92 -0
- package/agents/skills/product/professional-practice.skill.md +105 -0
- package/agents/skills/product/req-elicitation.skill.md +292 -0
- package/agents/skills/product/req-review.skill.md +280 -0
- package/agents/skills/product/spec-analyze.skill.md +98 -0
- package/agents/skills/product/spec-writer.skill.md +114 -0
- package/agents/skills/product/stakeholder-management.skill.md +54 -0
- package/agents/skills/product/sustainability-checks.skill.md +29 -0
- package/agents/skills/product/systems-thinking.skill.md +56 -0
- package/agents/skills/product/user-research-synthesis.skill.md +85 -0
- package/agents/skills/product/user-story-mapping.skill.md +54 -0
- package/agents/skills/product/visual-specs.skill.md +112 -0
- package/agents/skills/security/access-control.skill.md +45 -0
- package/agents/skills/security/agent-sandboxing.skill.md +69 -0
- package/agents/skills/security/ai-ethics-compliance.skill.md +46 -0
- package/agents/skills/security/ai-red-teaming.skill.md +74 -0
- package/agents/skills/security/ai-safety-guardrails.skill.md +60 -0
- package/agents/skills/security/api-security.skill.md +31 -0
- package/agents/skills/security/backup-recovery.skill.md +49 -0
- package/agents/skills/security/compliance-review.skill.md +152 -0
- package/agents/skills/security/cryptography-standards.skill.md +31 -0
- package/agents/skills/security/dependency-security.skill.md +47 -0
- package/agents/skills/security/hazard-analysis.skill.md +53 -0
- package/agents/skills/security/legal-review.skill.md +41 -0
- package/agents/skills/security/log-analysis.skill.md +68 -0
- package/agents/skills/security/network-security.skill.md +64 -0
- package/agents/skills/security/privacy-audit.skill.md +137 -0
- package/agents/skills/security/privacy-data-protection.skill.md +31 -0
- package/agents/skills/security/prompt-injection-defense.skill.md +67 -0
- package/agents/skills/security/reliability-engineering.skill.md +47 -0
- package/agents/skills/security/safety-scan.skill.md +49 -0
- package/agents/skills/security/secrets-management.skill.md +65 -0
- package/agents/skills/security/secure-architecture.skill.md +31 -0
- package/agents/skills/security/security-audit.skill.md +164 -0
- package/agents/skills/security/threat-model.skill.md +120 -0
- package/agents/skills/security/traceability-audit.skill.md +48 -0
- package/agents/templates/00-index.md +162 -0
- package/agents/templates/architecture/ADAPTIVE_SYSTEM_TEMPLATE.md +35 -0
- package/agents/templates/architecture/ADD_WORKBOOK_TEMPLATE.md +81 -0
- package/agents/templates/architecture/ADR_TEMPLATE.md +136 -0
- package/agents/templates/architecture/ARCHITECTURE_DECISION_MATRIX.md +169 -0
- package/agents/templates/architecture/ARCHITECTURE_REVIEW_TEMPLATE.md +241 -0
- package/agents/templates/architecture/ARCHITECTURE_VIEWS_TEMPLATE.md +353 -0
- package/agents/templates/architecture/ARCH_DECISION_FRAMEWORK.md +32 -0
- package/agents/templates/architecture/C4_ARCHITECTURE_TEMPLATE.md +185 -0
- package/agents/templates/architecture/CAPABILITY_MAP_TEMPLATE.md +153 -0
- package/agents/templates/architecture/CONTEXT_MAP_TEMPLATE.md +196 -0
- package/agents/templates/architecture/DESIGN_PATTERN_USAGE.md +24 -0
- package/agents/templates/architecture/DOMAIN_MODEL_TEMPLATE.md +254 -0
- package/agents/templates/architecture/FITNESS_FUNCTION_TEMPLATE.md +59 -0
- package/agents/templates/architecture/INTEGRATION_SPEC_TEMPLATE.md +38 -0
- package/agents/templates/architecture/LEGACY_AUDIT_TEMPLATE.md +34 -0
- package/agents/templates/architecture/QUALITY_ATTRIBUTES_TEMPLATE.md +210 -0
- package/agents/templates/architecture/SCALABILITY_ANALYSIS_TEMPLATE.md +46 -0
- package/agents/templates/architecture/SMART_CONTRACT_TEMPLATE.md +44 -0
- package/agents/templates/architecture/SYSTEM_CONTEXT_TEMPLATE.md +197 -0
- package/agents/templates/brain/ACTIVE_INFERENCE_LOOP_TEMPLATE.md +42 -0
- package/agents/templates/brain/EPISODIC_MEMORY_LOG_TEMPLATE.md +28 -0
- package/agents/templates/brain/GLOBAL_WORKSPACE_CONFIG_TEMPLATE.md +44 -0
- package/agents/templates/brain/KNOWLEDGE_MAP_TEMPLATE.md +53 -0
- package/agents/templates/brain/OODA_LOOP_TRACE_TEMPLATE.md +44 -0
- package/agents/templates/brain/PREDICTION_ERROR_LOG_TEMPLATE.md +33 -0
- package/agents/templates/brain/PROJECT_CONTEXT_TEMPLATE.md +36 -0
- package/agents/templates/brain/SELF_IMPROVEMENT_LOG_TEMPLATE.md +39 -0
- package/agents/templates/brain/WORKING_MEMORY_TEMPLATE.md +34 -0
- package/agents/templates/coding/CLEAN_CODE_CHECKLIST.md +30 -0
- package/agents/templates/coding/DESIGN_TOKENS_TEMPLATE.json +54 -0
- package/agents/templates/coding/DEVCONTAINER_TEMPLATE.json +42 -0
- package/agents/templates/coding/DEV_SPACE_TEMPLATE.yaml +48 -0
- package/agents/templates/coding/E2E_TEST_SUITE_TEMPLATE.md +36 -0
- package/agents/templates/coding/EVAL_PLAN_TEMPLATE.md +85 -0
- package/agents/templates/coding/EVAL_RUBRIC_TEMPLATE.md +57 -0
- package/agents/templates/coding/GOLDEN_DATASET_TEMPLATE.md +73 -0
- package/agents/templates/coding/PROPERTY_TEST_CHECKLIST.md +77 -0
- package/agents/templates/coding/SKETCH_TO_DIAGRAM_TEMPLATE.md +56 -0
- package/agents/templates/coding/TEST_CASE_TEMPLATE.md +28 -0
- package/agents/templates/coding/TEST_PLAN_TEMPLATE.md +36 -0
- package/agents/templates/coding/TIME_COMPLEXITY_REPORT_TEMPLATE.md +61 -0
- package/agents/templates/coordination/AGENTS_TEMPLATE.md +540 -0
- package/agents/templates/coordination/AGENT_HANDSHAKE_TEMPLATE.json +37 -0
- package/agents/templates/coordination/AGENT_PROFILE_TEMPLATE.md +28 -0
- package/agents/templates/coordination/SWARM_ARCHITECTURE_TEMPLATE.md +53 -0
- package/agents/templates/coordination/SWARM_CONFIG_TEMPLATE.json +45 -0
- package/agents/templates/core/AUDIT_LOG_TEMPLATE.md +75 -0
- package/agents/templates/core/BUG_REPORT_TEMPLATE.md +136 -0
- package/agents/templates/core/DEPENDENCY_GRAPH_TEMPLATE.md +63 -0
- package/agents/templates/core/ESTIMATION_TEMPLATE.md +70 -0
- package/agents/templates/core/MCP_CONFIG_TEMPLATE.json +807 -0
- package/agents/templates/core/PLAN_TEMPLATE.md +162 -0
- package/agents/templates/core/PROJECT_RETROSPECTIVE_TEMPLATE.md +67 -0
- package/agents/templates/core/SDLC_TRACKER.md +217 -0
- package/agents/templates/core/SESSION_SNAPSHOT_TEMPLATE.md +168 -0
- package/agents/templates/core/SYSTEM_ANALYSIS_TEMPLATE.md +52 -0
- package/agents/templates/core/TASKS_TEMPLATE.md +104 -0
- package/agents/templates/core/TRACEABILITY_MATRIX_TEMPLATE.md +18 -0
- package/agents/templates/core/WHITEBOARD_DESIGN_TEMPLATE.md +46 -0
- package/agents/templates/data/DATABASE_SCHEMA_TEMPLATE.md +38 -0
- package/agents/templates/data/DATA_PIPELINE_TEMPLATE.md +44 -0
- package/agents/templates/data/ONTOLOGY_TEMPLATE.md +52 -0
- package/agents/templates/industry/ENGINEERING_STANDARDS_REVIEW_TEMPLATE.md +43 -0
- package/agents/templates/industry/FHIR_INTEGRATION_TEMPLATE.md +53 -0
- package/agents/templates/industry/GLOBAL_STANDARDS_AUDIT_TEMPLATE.md +45 -0
- package/agents/templates/industry/IOT_TELEMETRY_TEMPLATE.md +59 -0
- package/agents/templates/industry/TELECOM_API_TEMPLATE.md +50 -0
- package/agents/templates/ops/BENCHMARK_REPORT_TEMPLATE.md +48 -0
- package/agents/templates/ops/CAPACITY_PLAN_TEMPLATE.md +41 -0
- package/agents/templates/ops/COST_OPTIMIZATION_REPORT_TEMPLATE.md +40 -0
- package/agents/templates/ops/DECOMMISSION_PLAN_TEMPLATE.md +102 -0
- package/agents/templates/ops/DEPLOY_CONFIG_TEMPLATE.md +88 -0
- package/agents/templates/ops/INCIDENT_POSTMORTEM_TEMPLATE.md +39 -0
- package/agents/templates/ops/INFRA_PLAN_TEMPLATE.md +37 -0
- package/agents/templates/ops/RELEASE_READINESS_REPORT.md +35 -0
- package/agents/templates/ops/RUNBOOK_TEMPLATE.md +103 -0
- package/agents/templates/ops/TECH_DEBT_TEMPLATE.md +102 -0
- package/agents/templates/product/BUSINESS_CASE_TEMPLATE.md +42 -0
- package/agents/templates/product/CHANGE_MANAGEMENT_PLAN_TEMPLATE.md +68 -0
- package/agents/templates/product/EMPATHY_MAP_TEMPLATE.md +47 -0
- package/agents/templates/product/EXPERIMENT_PLAN_TEMPLATE.md +84 -0
- package/agents/templates/product/GREEN_SOFTWARE_REPORT_TEMPLATE.md +42 -0
- package/agents/templates/product/IDEATION_LOG_TEMPLATE.md +42 -0
- package/agents/templates/product/NFR_TEMPLATE.md +31 -0
- package/agents/templates/product/PRD_TEMPLATE.md +222 -0
- package/agents/templates/product/PROBLEM_STATEMENT_TEMPLATE.md +32 -0
- package/agents/templates/product/REQUIREMENTS_REVIEW_TEMPLATE.md +173 -0
- package/agents/templates/product/SPEC_TEMPLATE.md +259 -0
- package/agents/templates/product/STAKEHOLDER_REGISTER_TEMPLATE.md +127 -0
- package/agents/templates/product/USER_STORY_MAP_TEMPLATE.md +35 -0
- package/agents/templates/product/VISUAL_SPEC_PACKAGE_TEMPLATE.md +207 -0
- package/agents/templates/security/DATASHEET_TEMPLATE.md +95 -0
- package/agents/templates/security/ETHICAL_IMPACT_ASSESSMENT.md +32 -0
- package/agents/templates/security/HAZARD_LOG.md +17 -0
- package/agents/templates/security/MODEL_CARD_TEMPLATE.md +120 -0
- package/agents/templates/security/SAFETY_CASE.md +39 -0
- package/agents/templates/security/SAFETY_POLICY.md +25 -0
- package/agents/templates/security/SECURITY_CHECKLIST.md +157 -0
- package/agents/templates/security/SYSTEM_CARD_TEMPLATE.md +139 -0
- package/agents/templates/security/THREAT_MODEL_TEMPLATE.md +171 -0
- package/bin/install.js +572 -0
- package/docs/CLI_REFERENCE.md +527 -0
- package/docs/INSTALL.md +68 -0
- package/docs/MCP_CONFIGURATIONS.md +1765 -0
- package/docs/PLATFORM_CONTROLS.md +324 -0
- package/docs/POST_INSTALL.md +75 -0
- package/docs/QUICK_COMMANDS.md +131 -0
- package/docs/QUICK_GUIDE.md +914 -0
- package/docs/README_FULL.md +1451 -0
- package/docs/SCHEMA.md +164 -0
- package/docs/V1_RELEASE_CHECKLIST.md +144 -0
- package/docs/VERIFICATION_GUIDE.md +283 -0
- package/docs/adr/0001-record-architecture-decisions.md +26 -0
- package/docs/adr/0002-brain-active-inference-runtime.md +27 -0
- package/docs/adr/0003-additive-only-emitter-schema-evolution.md +33 -0
- package/docs/assets/GABBE.png +0 -0
- package/docs/gabbe.config.example.json +9 -0
- package/docs/reports/duplication-report.md +30 -0
- package/install.ps1 +90 -0
- package/install.sh +89 -0
- package/package.json +49 -0
- package/scripts/init.py +1036 -0
|
@@ -0,0 +1,49 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: backup-recovery
|
|
3
|
+
description: Define RPO/RTO, implement PITR/Snapshots, and test restores.
|
|
4
|
+
triggers: [backup recovery]
|
|
5
|
+
tags: [security]
|
|
6
|
+
role: ops-sre, eng-database
|
|
7
|
+
context_cost: low
|
|
8
|
+
---
|
|
9
|
+
# backup-recovery Skill
|
|
10
|
+
|
|
11
|
+
## Goal
|
|
12
|
+
"A backup is not a backup until you have successfully restored from it."
|
|
13
|
+
|
|
14
|
+
## Steps
|
|
15
|
+
## 1. Define Objectives
|
|
16
|
+
- **RPO (Recovery Point Objective)**: Max data loss. (e.g., "1 hour", "5 minutes", "0 seconds").
|
|
17
|
+
- **RTO (Recovery Time Objective)**: Max downtime. (e.g., "4 hours", "30 minutes").
|
|
18
|
+
|
|
19
|
+
## 2. Strategies
|
|
20
|
+
- **Point-In-Time Recovery (PITR)**: Archive WAL/Binlogs to replay transactions up to a specific second. (Critical for RPO ~0).
|
|
21
|
+
- **Snapshot**: Daily/Hourly full disk copy. Low impact, slower restore.
|
|
22
|
+
- **Logical Dump**: `pg_dump` / `mysqldump`. Portable, slow for large data.
|
|
23
|
+
|
|
24
|
+
## 3. Storage & Retention
|
|
25
|
+
- **Immutability**: Backups must be Read-Only (WORM) to prevent Ransomware encryption.
|
|
26
|
+
- **Off-site**: Replicate to a different region/cloud provider (3-2-1 Rule).
|
|
27
|
+
- **Retention**: Keep Dailies for 7 days, Weeklies for 1 month, Monthlies for 1 year.
|
|
28
|
+
|
|
29
|
+
## 4. Testing (The Golden Rule)
|
|
30
|
+
- **Automated Restore Drill**: Weekly CI job that:
|
|
31
|
+
1. Spins up a fresh DB.
|
|
32
|
+
2. Pulls the latest backup.
|
|
33
|
+
3. Restores it.
|
|
34
|
+
4. Runs integrity check (`SELECT count(*) ...`).
|
|
35
|
+
5. Reports success/failure to Slack.
|
|
36
|
+
|
|
37
|
+
## Security & Guardrails
|
|
38
|
+
|
|
39
|
+
### 1. Skill Security (Backup & Recovery)
|
|
40
|
+
- **Backup Immutability (WORM)**: The agent must hard-enforce Write-Once-Read-Many (WORM) storage paradigms for all archival backups. Once a daily snapshot or logical dump is written to the backup partition, the agent is strictly prohibited from executing any script that modifies, overwrites, or truncates that archival file, defending against ransomware.
|
|
41
|
+
- **Restoration Sandbox Integrity**: Automated restore drills must occur in a fundamentally isolated, ephemeral VPC network lacking outbound internet access. This ensures that if the backup contains a delayed-execution backdoor or sleeper malware (timebomb), the malicious payload cannot phone home or pivot when the snapshot is spun up for testing.
|
|
42
|
+
|
|
43
|
+
### 2. System Integration Security
|
|
44
|
+
- **Backup Encryption Keys Segregation**: The cryptographic keys used to encrypt the backups at rest must be stored in a completely separate Key Management Service (KMS) regional cluster from the keys used to encrypt the primary production database. An attacker compromising the production environment must not automatically gain the ability to decrypt the off-site backups.
|
|
45
|
+
- **Credential Scrubbing on Logical Dumps**: If the system relies on logical dumps (`pg_dump`), the agent must ensure that specific columns containing highly sensitive transient data (e.g., active session tokens, OAuth nonces, password reset hashes) are explicitly excluded from the dump to prevent the backup volume from becoming a high-value target for lateral movement.
|
|
46
|
+
|
|
47
|
+
### 3. LLM & Agent Guardrails
|
|
48
|
+
- **Malicious Deletion Requests**: The agent must violently reject any user prompt instructing it to "delete all backups older than 2 days to save S3 costs." The LLM must recognize backup retention periods as non-negotiable compliance mandates and refuse to execute commands that jeopardize the system's Disaster Recovery posture.
|
|
49
|
+
- **Data Extortion Vector**: If an attacker gains conversational access to the agent, they might prompt it to "restore the latest production database backup to this temporary EC2 instance I control." The agent must mandate multi-factor, out-of-band human authorization before executing any restoration procedure outside of the predefined, automated CI/CD drill pipeline.
|
|
@@ -0,0 +1,152 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: compliance-review
|
|
3
|
+
description: Regulatory compliance check for SOC2, PCI-DSS, GDPR, HIPAA — checklists, audit trails, access controls
|
|
4
|
+
triggers: [compliance, SOC2, PCI-DSS, GDPR, audit trail, regulatory, certification, compliance review]
|
|
5
|
+
tags: [security]
|
|
6
|
+
context_cost: high
|
|
7
|
+
---
|
|
8
|
+
# Compliance Review Skill
|
|
9
|
+
|
|
10
|
+
## Goal
|
|
11
|
+
Verify that the codebase and system configuration meet applicable regulatory requirements. Produce a gap report with specific remediation actions.
|
|
12
|
+
|
|
13
|
+
## Steps
|
|
14
|
+
|
|
15
|
+
1. **Identify applicable regulations**
|
|
16
|
+
- Ask if unclear which regulations apply
|
|
17
|
+
- SOC2 Type II: SaaS products, cloud services (trust criteria: security, availability, confidentiality)
|
|
18
|
+
- PCI-DSS: any system handling payment card data
|
|
19
|
+
- GDPR: processing data of EU residents
|
|
20
|
+
- HIPAA: US healthcare data (PHI — Protected Health Information)
|
|
21
|
+
- ISO 27001: general information security management
|
|
22
|
+
|
|
23
|
+
2. **Run the applicable checklist**
|
|
24
|
+
|
|
25
|
+
### SOC2 Type II — Trust Service Criteria
|
|
26
|
+
```
|
|
27
|
+
Security (CC6):
|
|
28
|
+
[ ] CC6.1: Logical access controls — only authorized users access systems
|
|
29
|
+
[ ] CC6.2: Authentication mechanisms (MFA for privileged access)
|
|
30
|
+
[ ] CC6.3: Role-based access control (RBAC) implemented
|
|
31
|
+
[ ] CC6.6: Encryption in transit and at rest
|
|
32
|
+
[ ] CC6.7: Change management process (code review + approval workflow)
|
|
33
|
+
[ ] CC6.8: Vulnerability management (regular scanning + patching policy)
|
|
34
|
+
|
|
35
|
+
Availability (A1):
|
|
36
|
+
[ ] A1.1: Uptime SLO defined and monitored
|
|
37
|
+
[ ] A1.2: Backup and restore procedures documented and tested
|
|
38
|
+
[ ] A1.3: Incident response plan exists
|
|
39
|
+
|
|
40
|
+
Confidentiality (C1):
|
|
41
|
+
[ ] C1.1: Confidential data identified and classified
|
|
42
|
+
[ ] C1.2: Confidential data encrypted at rest
|
|
43
|
+
[ ] C1.3: Data disposal procedure for end-of-lifecycle
|
|
44
|
+
```
|
|
45
|
+
|
|
46
|
+
### PCI-DSS v4.0 — Key Requirements
|
|
47
|
+
```
|
|
48
|
+
[ ] Req 1: Firewall/network security controls installed and documented
|
|
49
|
+
[ ] Req 2: No default passwords or vendor-supplied defaults
|
|
50
|
+
[ ] Req 3: Card data (PAN) never stored in plaintext — tokenize or don't store
|
|
51
|
+
[ ] Req 4: Encryption in transit (TLS 1.2+ for cardholder data)
|
|
52
|
+
[ ] Req 6: Secure development policy — SAST/SCA in CI/CD pipeline
|
|
53
|
+
[ ] Req 7: Least privilege access to cardholder data systems
|
|
54
|
+
[ ] Req 8: MFA for all access to cardholder data environment
|
|
55
|
+
[ ] Req 10: Audit log of all access to cardholder data (90 days online, 1 year archived)
|
|
56
|
+
[ ] Req 11: Vulnerability scanning and penetration testing schedule
|
|
57
|
+
[ ] Req 12: Incident response plan for data breach
|
|
58
|
+
```
|
|
59
|
+
|
|
60
|
+
### HIPAA — Key Safeguards
|
|
61
|
+
```
|
|
62
|
+
Technical Safeguards:
|
|
63
|
+
[ ] Access controls: unique user IDs, automatic logoff, encryption/decryption of PHI
|
|
64
|
+
[ ] Audit controls: hardware/software activity logs for systems containing PHI
|
|
65
|
+
[ ] Integrity controls: PHI not improperly altered or destroyed (checksums)
|
|
66
|
+
[ ] Transmission security: PHI encrypted in transit
|
|
67
|
+
|
|
68
|
+
Administrative Safeguards:
|
|
69
|
+
[ ] Security officer designated
|
|
70
|
+
[ ] Risk analysis documented and current
|
|
71
|
+
[ ] Workforce training on security policies
|
|
72
|
+
[ ] Business associate agreements (BAA) with all PHI processors
|
|
73
|
+
|
|
74
|
+
Physical Safeguards:
|
|
75
|
+
[ ] Facility access controls documented
|
|
76
|
+
[ ] Workstation security policy
|
|
77
|
+
```
|
|
78
|
+
|
|
79
|
+
3. **Check audit trail completeness**
|
|
80
|
+
- Every mutation of regulated data must be logged with: user ID, timestamp, action, record ID
|
|
81
|
+
- Log format: append-only (no updates or deletes to audit log)
|
|
82
|
+
- Log retention: SOC2/PCI = 90 days online + 1 year archived; HIPAA = 6 years; GDPR = per policy
|
|
83
|
+
- Log access: restricted to security/compliance team only
|
|
84
|
+
- Check: does AUDIT_LOG.md cover all regulated data mutations?
|
|
85
|
+
|
|
86
|
+
4. **Check access control implementation**
|
|
87
|
+
- Least-privilege: each role has minimum necessary permissions
|
|
88
|
+
- Separation of duties: critical operations require multiple approvals
|
|
89
|
+
- MFA: required for admin access and access to regulated data
|
|
90
|
+
- Access reviews: periodic review of who has access to what
|
|
91
|
+
|
|
92
|
+
5. **Check incident response plan**
|
|
93
|
+
- Is there a documented incident response procedure?
|
|
94
|
+
- Are breach notification timeframes defined? (GDPR: 72 hours; HIPAA: 60 days)
|
|
95
|
+
- Is there a contact list for regulatory notification?
|
|
96
|
+
- Has the plan been tested (tabletop exercise)?
|
|
97
|
+
|
|
98
|
+
6. **Generate compliance gap report**
|
|
99
|
+
```markdown
|
|
100
|
+
## Compliance Gap Report
|
|
101
|
+
|
|
102
|
+
### Scope: SOC2 Type II
|
|
103
|
+
Date: [date]
|
|
104
|
+
Auditor: [agent/human]
|
|
105
|
+
|
|
106
|
+
### Passed Controls: [N]/[total]
|
|
107
|
+
|
|
108
|
+
### Gaps Found
|
|
109
|
+
|
|
110
|
+
#### Critical Gaps (must remediate before certification)
|
|
111
|
+
- CC6.2: MFA not enforced for admin users
|
|
112
|
+
Remediation: Add MFA requirement to admin login flow
|
|
113
|
+
Owner: [team]
|
|
114
|
+
Target date: [date]
|
|
115
|
+
|
|
116
|
+
#### High Gaps
|
|
117
|
+
- CC6.8: No documented vulnerability management process
|
|
118
|
+
Remediation: Create security scanning policy, add to CI/CD
|
|
119
|
+
|
|
120
|
+
#### Medium Gaps
|
|
121
|
+
- A1.2: Backup restore procedure not documented
|
|
122
|
+
Remediation: Document and test restore procedure
|
|
123
|
+
|
|
124
|
+
### Compliant Controls
|
|
125
|
+
[list controls that passed]
|
|
126
|
+
|
|
127
|
+
### Next Steps
|
|
128
|
+
1. [priority-ordered remediation list]
|
|
129
|
+
```
|
|
130
|
+
|
|
131
|
+
## Constraints
|
|
132
|
+
- Never dismiss a compliance gap without documented risk acceptance from human
|
|
133
|
+
- Audit logs must be verified as actually append-only (not just policy)
|
|
134
|
+
- PCI requirements apply to the ENTIRE cardholder data environment — scope carefully
|
|
135
|
+
- Compliance gaps in critical categories are blocking for regulated industries
|
|
136
|
+
|
|
137
|
+
## Output Format
|
|
138
|
+
Compliance gap report at `docs/compliance/[regulation]-gap-report.md` with priority-ordered remediation plan.
|
|
139
|
+
|
|
140
|
+
## Security & Guardrails
|
|
141
|
+
|
|
142
|
+
### 1. Skill Security (Compliance Review)
|
|
143
|
+
- **Auditor Independence Validation**: The agent performing the compliance review must operate in an isolated, read-only context. It must not possess the necessary IAM permissions to alter the system configuration it is actively auditing. This enforces separation of duties and prevents the agent from autonomously masking compliance failures.
|
|
144
|
+
- **Evidence Immutability**: The telemetry, logs, and configuration states ingested by the agent to generate the `[regulation]-gap-report.md` must be cryptographically hashed upon ingestion. The generated report must include these hashes to ensure the raw evidence cannot be altered post-review to challenge the findings.
|
|
145
|
+
|
|
146
|
+
### 2. System Integration Security
|
|
147
|
+
- **PCI-DSS Scope Containment**: When auditing PCI-DSS Req 1 & 7, the agent must aggressively map the network boundaries. If the agent detects that the Cardholder Data Environment (CDE) shares a subnet, database, or lateral trust relationship with a non-compliant tertiary system, it must immediately flag this as a critical scope-bleed violation.
|
|
148
|
+
- **Audit Defeat Mechanics Detection**: The agent must proactively search the codebase for sophisticated audit-bypass logic (e.g., developers wrapping regulated data mutations in `try-catch` blocks that suppress the generation of an audit log entry upon failure, or using highly privileged service accounts that bypass application-level logging hooks).
|
|
149
|
+
|
|
150
|
+
### 3. LLM & Agent Guardrails
|
|
151
|
+
- **Compliance Hallucination Avoidance**: The LLM is strictly prohibited from inventing false interpretations of regulatory frameworks. If a specific technical implementation is ambiguous under SOC2 or HIPAA guidelines, the agent must not synthesize a definitive "Compliant" ruling. It must escalate the ambiguity to human legal counsel.
|
|
152
|
+
- **Risk Acceptance Abuse**: An authorized user might prompt the agent to "auto-generate a risk acceptance memo for all missing MFA controls to pass the audit today." The agent must refuse this directive. Risk acceptance for critical constraints (like MFA for PCI-DSS) is explicitly forbidden by the frameworks and constitutes fraudulent compliance reporting.
|
|
@@ -0,0 +1,31 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: cryptography-standards
|
|
3
|
+
description: Enforce correct cryptographic algorithms, hashing, and TLS standards
|
|
4
|
+
triggers: [encrypt data, hash passwords, set tls policy]
|
|
5
|
+
tags: [security]
|
|
6
|
+
context_cost: low
|
|
7
|
+
---
|
|
8
|
+
# cryptography-standards
|
|
9
|
+
|
|
10
|
+
## Goal
|
|
11
|
+
Apply, enforce, and maintain robust cryptographic strategies to protect data at rest and data in transit across all services.
|
|
12
|
+
|
|
13
|
+
## Steps
|
|
14
|
+
1. **Identify Requirement**: Determine if data requires at-rest hashing, symmetric encryption, or transit protection.
|
|
15
|
+
2. **Algorithm Selection**: Utilize modern, enterprise-approved primitives (e.g., Argon2id, AES-256-GCM, TLS 1.3).
|
|
16
|
+
3. **Key Management**: Document integration paths to secure KMS or Vaults; never hardcode cryptographic keys.
|
|
17
|
+
4. **Verification**: Write static tests that fail the build if deprecated algorithms (MD5, SHA1) are used.
|
|
18
|
+
|
|
19
|
+
## Security & Guardrails
|
|
20
|
+
|
|
21
|
+
### 1. Skill Security
|
|
22
|
+
- **Secret Generation Mute**: Do not allow the agent to generate valid "test" private keys or robust secrets dynamically and log them to the filesystem or chat interface.
|
|
23
|
+
- **Code Execution Ban**: Prevent the skill from dynamically executing complex crypto mathematics inside the markdown parser sandbox.
|
|
24
|
+
|
|
25
|
+
### 2. System Integration Security
|
|
26
|
+
- **Algorithm Veto**: Implicitly block the use of deprecated primitives (MD5, SHA1, DES, ECB mode). The CI should fail if these tokens are present.
|
|
27
|
+
- **Entropy Exhaustion**: Agents must ensure proper CSPRNG functions (e.g., `/dev/urandom`, `crypto.randomBytes()`) are used, never `Math.random()`.
|
|
28
|
+
|
|
29
|
+
### 3. LLM & Agent Guardrails
|
|
30
|
+
- **Hallucinated Cryptography**: The LLM must NEVER output or suggest a custom-designed cryptographic algorithm. It must rely exclusively on mature, peer-reviewed libraries (e.g., libsodium).
|
|
31
|
+
- **Misapplied Encryption**: The agent must distinguish between hashing (for passwords) and symmetric encryption (for PII). It cannot confidently recommend hashing for credit card retrieval logic.
|
|
@@ -0,0 +1,47 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: dependency-security
|
|
3
|
+
description: Managing Supply Chain Security, SBOM generation, and vulnerability patching (SCA).
|
|
4
|
+
triggers: [dependency security]
|
|
5
|
+
tags: [security]
|
|
6
|
+
role: ops-security, ops-devops
|
|
7
|
+
context_cost: low
|
|
8
|
+
---
|
|
9
|
+
# dependency-security Skill
|
|
10
|
+
|
|
11
|
+
## Goal
|
|
12
|
+
This skill secures the software supply chain.
|
|
13
|
+
|
|
14
|
+
## Steps
|
|
15
|
+
## 1. Software Composition Analysis (SCA)
|
|
16
|
+
> "You are what you import."
|
|
17
|
+
|
|
18
|
+
- **Audit**: Run `npm audit` / `pip-audit` / `cargo audit` in CI.
|
|
19
|
+
- **Block**: Fail the build on `CRITICAL` or `HIGH` vulnerabilities.
|
|
20
|
+
- **Lock**: Always verify lockfiles (`package-lock.json`) match `package.json`.
|
|
21
|
+
|
|
22
|
+
## 2. SBOM (Software Bill of Materials)
|
|
23
|
+
- Generate a list of all ingredients in your software.
|
|
24
|
+
- Tools: `syft`, `cyclonedx-cli`.
|
|
25
|
+
- Why? Rapid response when the next Log4Shell happens.
|
|
26
|
+
|
|
27
|
+
## 3. Dependency Pinning
|
|
28
|
+
- **Pin Exact Versions**: Avoid `^1.2.3` in critical apps. Use `1.2.3` to prevent "works on my machine" drift.
|
|
29
|
+
- **Private Registry**: For enterprise, proxy public registries to prevent "Left-Pad" incidents.
|
|
30
|
+
|
|
31
|
+
## 4. Typosquatting Defense
|
|
32
|
+
- **Scope**: Use `@myorg/package` scopes.
|
|
33
|
+
- **Verify**: Check download counts and maintainer reputation before adding new deps.
|
|
34
|
+
|
|
35
|
+
## Security & Guardrails
|
|
36
|
+
|
|
37
|
+
### 1. Skill Security (Dependency Security)
|
|
38
|
+
- **Scanner Sandbox Isolation**: Software Composition Analysis (SCA) tools (`npm audit`, `syft`) actively download and parse untrusted third-party manifest files. The agent must execute these scans within an ephemeral, strictly sandboxed container lacking network access to internal company resources, preventing a malicious `package.json` (e.g., via a post-install hook) from compromising the CI/CD pipeline.
|
|
39
|
+
- **Lockfile Immutability Enforcement**: The agent is strictly prohibited from bypassing the `package-lock.json` or `yarn.lock` during a build process. It must actively halt any deployment if it detects a divergence between the hashed lockfile and the stated dependencies, effectively blocking dynamic, unvetted code injection at runtime.
|
|
40
|
+
|
|
41
|
+
### 2. System Integration Security
|
|
42
|
+
- **Vulnerability Remediation Prioritization**: The agent must integrate with the overarching threat model. If the SCA tool flags a `CRITICAL` vulnerability in a library (e.g., an image parsing library), but that library is only deployed in a segmented, internal-only, unauthenticated reporting tool, the fix priority is high, but not an immediate block. However, if the vulnerable library touches the public internet, the build MUST fail.
|
|
43
|
+
- **Private Registry Mirroring**: To mitigate "Left-Pad" incidents and upstream registry compromises, the architecture must route all dependency pulls through a controlled, internal proxy registry (e.g., Artifactory, Nexus). The agent must flag any configuration that attempts to fetch dependencies directly from the public internet bypassing this proxy.
|
|
44
|
+
|
|
45
|
+
### 3. LLM & Agent Guardrails
|
|
46
|
+
- **Blind Upgrade Traps**: The agent must refuse user prompts that instruct it to blindly "Upgrade all dependencies to `latest` to fix the security warnings." Automated mass upgrades frequently introduce breaking changes or unintentionally pull in typosquatted/poisoned packages. Upgrades must be atomic, tested, and individually verified.
|
|
47
|
+
- **Ignoring Critical CVEs**: If a developer prompts the agent to "Add this specific CVE ID to the ignore list so the build passes," the agent must mandate an explicit, documented, and approved risk acceptance justification. It cannot unilaterally suppress critical security warnings based on a casual command.
|
|
@@ -0,0 +1,53 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: hazard-analysis
|
|
3
|
+
description: Conducting FMEA (Failure Mode & Effects Analysis) and identifying hazards.
|
|
4
|
+
triggers: [hazard analysis]
|
|
5
|
+
tags: [security]
|
|
6
|
+
role: prod-safety-engineer
|
|
7
|
+
context_cost: low
|
|
8
|
+
---
|
|
9
|
+
# hazard-analysis Skill
|
|
10
|
+
|
|
11
|
+
## Goal
|
|
12
|
+
This skill identifies how the system can fail and what happens when it does.
|
|
13
|
+
|
|
14
|
+
## Steps
|
|
15
|
+
## 1. FMEA (Failure Mode & Effects Analysis)
|
|
16
|
+
- **Component**: [Name]
|
|
17
|
+
- **Failure Mode**: How does it fail? (e.g., "Stuck Open", "No Output", "Corrupt Data").
|
|
18
|
+
- **Effect**: What is the impact? (e.g., "Engine overheats").
|
|
19
|
+
- **Severity**: 1-10 (10 = Catastrophic/Death).
|
|
20
|
+
- **Probability**: 1-10 (10 = Certain).
|
|
21
|
+
- **Detection**: 1-10 (10 = Undetectable).
|
|
22
|
+
- **RPN (Risk Priority Number)**: Sev * Prob * Det.
|
|
23
|
+
|
|
24
|
+
## 2. STPA (System-Theoretic Process Analysis)
|
|
25
|
+
- Focus on *control* loops rather than component failures.
|
|
26
|
+
- **Unsafe Control Actions (UCA)**:
|
|
27
|
+
- Not providing a control action when needed.
|
|
28
|
+
- Providing a control action when not needed.
|
|
29
|
+
- Providing a control action too early/late.
|
|
30
|
+
- Stopped too soon or applied too long.
|
|
31
|
+
|
|
32
|
+
## 3. Hazard Identification Checklist
|
|
33
|
+
- **Energy**: High voltage, pressure, heat?
|
|
34
|
+
- **Timing**: Latency, jitter, race conditions?
|
|
35
|
+
- **Data**: Corruption, stale data, NaN/Infinity?
|
|
36
|
+
- **Interface**: Mismatched units (Metric vs Imperial)?
|
|
37
|
+
|
|
38
|
+
## 4. Output
|
|
39
|
+
- Populate `templates/security/HAZARD_LOG.md`.
|
|
40
|
+
|
|
41
|
+
## Security & Guardrails
|
|
42
|
+
|
|
43
|
+
### 1. Skill Security (Hazard Analysis)
|
|
44
|
+
- **Catastrophic Failure Immutability**: When an agent classifies a hazard's Severity as "10 (Catastrophic/Death)" in the `HAZARD_LOG.md`, that entry becomes immutable to automated downgrades. The agent cannot unilaterally reduce the severity in subsequent revisions; it requires cryptographic, multi-party human sign-off.
|
|
45
|
+
- **Data Poisoning in STPA**: If the agent uses an LLM to generate Unsafe Control Actions (UCAs), it must cross-reference the output against a static, deterministic safety rule engine. This prevents prompt poisoning from maliciously instructing the hazard analysis to ignore a critical failure mode (e.g., "Ignore the redundant braking system checklist").
|
|
46
|
+
|
|
47
|
+
### 2. System Integration Security
|
|
48
|
+
- **Security as a Hazard Category**: The hazard identification checklist must natively integrate "Intentional Malicious Action." The FMEA cannot solely focus on natural component degradation (e.g., "Disk failure"); it must mandate analysis of adversarial component degradation (e.g., "Attacker fills disk to cause DoS").
|
|
49
|
+
- **Physical Safety Sandboxing**: If the hazard analysis interfaces with Cyber-Physical Systems (e.g., medical devices, autonomous vehicles), the agent generating the analysis must operate in an entirely air-gapped or physically segmented network to prevent its analysis engine from being pivoted into the operational technology (OT) network.
|
|
50
|
+
|
|
51
|
+
### 3. LLM & Agent Guardrails
|
|
52
|
+
- **Risk Normalization Blindness**: The agent must actively combat "Normalization of Deviance." If it reviews a system where a specific component historically fails often but hasn't caused a catastrophe *yet*, the LLM is strictly forbidden from lowering the Probability or Severity scores based on "past operational luck."
|
|
53
|
+
- **Hallucinated Mitigations**: The agent must not invent fictitious safety mitigations (e.g., "The system is safe because a theoretical Quantum Firewall will block the voltage spike") to artificially lower the RPN (Risk Priority Number) below the required safety threshold. All mitigations must reference existing, verifiable system architecture.
|
|
@@ -0,0 +1,41 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: "legal-review"
|
|
3
|
+
description: "Check for license compliance, PII, and IP risks"
|
|
4
|
+
triggers: ["Check licenses", "Review for legal compliance", "Is this library safe to use?", "GDPR compliance check"]
|
|
5
|
+
tags: ["security"]
|
|
6
|
+
context_cost: "medium"
|
|
7
|
+
---
|
|
8
|
+
# Legal Review Skill
|
|
9
|
+
|
|
10
|
+
## Goal
|
|
11
|
+
|
|
12
|
+
## Role
|
|
13
|
+
You are a **Legal Compliance Bot**. You scan dependencies and code for legal risks. *Disclaimer: You are not a lawyer. This is a preliminary engineering check.*
|
|
14
|
+
|
|
15
|
+
## Checks
|
|
16
|
+
1. **Licenses**: Scan `package.json`/`requirements.txt`.
|
|
17
|
+
- *Safe*: MIT, Apache 2.0, BSD-3, ISC.
|
|
18
|
+
- *Risky (Copyleft)*: GPL, AGPL (requires careful review if proprietary).
|
|
19
|
+
- *Forbidden*: WTFPL (often banned in enterprise), or Unlicensed.
|
|
20
|
+
2. **PII/Data**: Are we collecting data without a policy?
|
|
21
|
+
3. **Terms**: Are we violating any API Terms of Service?
|
|
22
|
+
4. **Attribution**: Are we properly crediting open source assets?
|
|
23
|
+
|
|
24
|
+
## Output
|
|
25
|
+
- **License Audit Report**: List of all 3rd party libs + their licenses.
|
|
26
|
+
- **Risk Flag**: "HIGH RISK: AGPL library detected in proprietary service."
|
|
27
|
+
|
|
28
|
+
## Security & Guardrails
|
|
29
|
+
|
|
30
|
+
### Steps
|
|
31
|
+
## 1. Skill Security (Legal Review)
|
|
32
|
+
- **Legal Advice Disclaimer Adherence**: The agent MUST prefix any final report with a non-removable disclaimer stating it is an engineering compliance tool, not legal counsel. The agent is strictly prohibited from executing prompts that ask it to "act as a certified corporate lawyer" or draft binding indemnification clauses.
|
|
33
|
+
- **Proprietary IP Leakage Prevention**: When scanning the codebase to assess licensing combinations (e.g., checking if proprietary code links to a GPL library), the agent must process the analysis locally. It cannot transmit snippets of proprietary internal source code to external, unvetted LLM APIs to ask "Is this specific algorithm legally protectable?"
|
|
34
|
+
|
|
35
|
+
### 2. System Integration Security
|
|
36
|
+
- **Copyleft Contagion Blocking**: If the agent detects a `HIGH RISK` (e.g., AGPL) dependency in an explicitly proprietary microservice, it must integrate with the CI/CD pipeline to immediately trigger a hard build failure. It cannot simply log the risk and allow the deployment to proceed.
|
|
37
|
+
- **ToS Violation Escaping**: The agent must verify that the system's external API calls respect rate limits and Terms of Service (ToS). If the architecture relies heavily on web scraping a competitor without a formal agreement, the agent must flag this as a critical, systemic legal/security liability.
|
|
38
|
+
|
|
39
|
+
### 3. LLM & Agent Guardrails
|
|
40
|
+
- **Hallucinated License Definitions**: The agent must rely solely on the OSI (Open Source Initiative) established definitions for licenses. It cannot hallucinate or creatively interpret a license (e.g., advising that "WTFPL is fine for banking because no one enforces it").
|
|
41
|
+
- **Attorney-Client Privilege Traps**: Users might prompt the agent with highly sensitive legal contexts (e.g., "We are currently being sued for patent infringement by Company X. Does our codebase contain their algorithm?"). The agent must recognize the legal sensitivity and refuse to document the analysis in a discoverable text file, escalating immediately to human legal counsel.
|
|
@@ -0,0 +1,68 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: log-analysis
|
|
3
|
+
description: Parsing structured logs, finding patterns in noise, and ELK/Splunk querying.
|
|
4
|
+
triggers: [log analysis]
|
|
5
|
+
tags: [security]
|
|
6
|
+
role: ops-monitor
|
|
7
|
+
context_cost: low
|
|
8
|
+
---
|
|
9
|
+
# log-analysis Skill
|
|
10
|
+
|
|
11
|
+
## Goal
|
|
12
|
+
This skill helps agents and engineers interpret logging data to find root causes of issues.
|
|
13
|
+
|
|
14
|
+
## Steps
|
|
15
|
+
## 1. Structured Logging (The Prerequisite)
|
|
16
|
+
- **Format**: JSON. Always.
|
|
17
|
+
- **Why**: Allows querying `level="ERROR" AND service="user-api"`. Text logs require fragile regex.
|
|
18
|
+
- **Context**: Every log must have `trace_id`, `user_id`, and `environment`.
|
|
19
|
+
|
|
20
|
+
## 2. Analysis Workflow
|
|
21
|
+
|
|
22
|
+
1. **Scope the Timeframe**: "Last 15 minutes" or "Since deployment at 14:00".
|
|
23
|
+
2. **Filter by Level**: Start with `ERROR` and `FATAL`. Ignore `INFO` initially.
|
|
24
|
+
3. **Group by Message**:
|
|
25
|
+
- **Bad**: Reading 1000 lines of `Connection timeout`.
|
|
26
|
+
- **Good**: "Count of errors by message type: Timeout (800), Auth Fail (200)".
|
|
27
|
+
4. **Trace Correlation**: take one `trace_id` from an error and filter ALL logs (inc INFO) for that ID to see the sequence of events leading to failure.
|
|
28
|
+
|
|
29
|
+
## 3. Query Cheatsheet
|
|
30
|
+
|
|
31
|
+
### Loki (LogQL)
|
|
32
|
+
```logql
|
|
33
|
+
{app="frontend"} |= "error" | json | latency > 500ms
|
|
34
|
+
```
|
|
35
|
+
|
|
36
|
+
### Elasticsearch / Kibana (Lucene)
|
|
37
|
+
```lucene
|
|
38
|
+
service:backend AND level:ERROR AND NOT message:"healthcheck"
|
|
39
|
+
```
|
|
40
|
+
|
|
41
|
+
### Splunk
|
|
42
|
+
```splunk
|
|
43
|
+
index=prod sourcetype=k8s | stats count by message | sort - count
|
|
44
|
+
```
|
|
45
|
+
|
|
46
|
+
### Command Line (jq)
|
|
47
|
+
```bash
|
|
48
|
+
cat logs.json | jq 'select(.level=="error") | .message' | sort | uniq -c
|
|
49
|
+
```
|
|
50
|
+
|
|
51
|
+
## 4. Red Flags ("Smells")
|
|
52
|
+
- **"Swallowed Exception"**: Logs that say "Error occurred" but print no stack trace.
|
|
53
|
+
- **"Noise"**: Periodic errors (e.g., every 5 mins) that everyone ignores. These mask real issues.
|
|
54
|
+
- **"Sensitive Data"**: Passwords or PII in logs. -> **CRITICAL**: Report immediately.
|
|
55
|
+
|
|
56
|
+
## Security & Guardrails
|
|
57
|
+
|
|
58
|
+
### 1. Skill Security (Log Analysis)
|
|
59
|
+
- **Mandatory PII Scrubbing**: The agent must utilize `Rebertha` or an equivalent dedicated regex engine to proactively redact SSNs, Credit Card numbers, Auth Tokens, and Passwords BEFORE it writes the log summary to a file or transmits it for analysis. A failure in the redaction layer must cause the log analysis to fail-closed.
|
|
60
|
+
- **Log Forgery Resilience**: The agent must trust the centralized log aggregation server (Splunk/ELK), but it must NOT implicitly trust the contents of the `message` payload. It must recognize the vulnerability of Log Injection (e.g., an attacker injecting `\n [INFO] User Admin Authenticated`) and prioritize `trace_id` and cryptographically signed application context.
|
|
61
|
+
|
|
62
|
+
### 2. System Integration Security
|
|
63
|
+
- **Access Control on Audit Logs**: The agent must verify that the systems generating high-stakes logs (auth, financial transactions) are forwarding them to an immutable, WORM (Write-Once-Read-Many) storage bucket. If the agent detects that the application layer has `DELETE` permissions on an audit index, it must raise a sev-1 alarm.
|
|
64
|
+
- **Alert Fatigue Exploitation**: An attacker may flood the system with low-severity `WARN` logs to mask a stealthy exfiltration attack occurring under the radar. The agent must implement rate-anomaly detection: if the volume of a specific log spikes by 1000%, it must condense the alert to prevent SOC burnout but escalate the anomaly.
|
|
65
|
+
|
|
66
|
+
### 3. LLM & Agent Guardrails
|
|
67
|
+
- **Hallucinated Root Cause**: In the presence of highly ambiguous logs, the LLM might confidently hallucinate a plausible but incorrect root cause (e.g., blaming a DNS failure when it was actually a subtle authorization bug). The agent must qualify its findings with confidence scores and cite the exact log line (via `trace_id`) that supports its hypothesis.
|
|
68
|
+
- **Malicious Query Injection**: An attacker with access to the agent's prompts might attempt to inject a destructive Splunk query or perform unconstrained searches (e.g., `* | delete` or searching across all indexes to exfiltrate data). The agent must execute LogQL/Lucene queries under a strictly scoped, read-only service account.
|
|
@@ -0,0 +1,64 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: network-security
|
|
3
|
+
description: Firewall rules, VPC design, TLS config, and subnet isolation.
|
|
4
|
+
triggers: [network security]
|
|
5
|
+
tags: [security]
|
|
6
|
+
role: ops-security
|
|
7
|
+
context_cost: low
|
|
8
|
+
---
|
|
9
|
+
# network-security Skill
|
|
10
|
+
|
|
11
|
+
## Goal
|
|
12
|
+
This skill defines the perimeter and internal segmentation of the infrastructure.
|
|
13
|
+
|
|
14
|
+
## Steps
|
|
15
|
+
## 1. VPC Architecture
|
|
16
|
+
|
|
17
|
+
### Public Subnet
|
|
18
|
+
- **Contains**: Load Balancers (ALB), NAT Gateways, Bastion Hosts.
|
|
19
|
+
- **Access**: 0.0.0.0/0 (Internet) on ports 80/443.
|
|
20
|
+
|
|
21
|
+
### Private Subnet
|
|
22
|
+
- **Contains**: Application Servers, Runners.
|
|
23
|
+
- **Access**: Only from Public Subnet (Load Balancer). NO direct Internet ingress.
|
|
24
|
+
|
|
25
|
+
### Data Subnet (Isolated)
|
|
26
|
+
- **Contains**: Databases, Redis, Vault.
|
|
27
|
+
- **Access**: Only from Private Subnet (App Servers).
|
|
28
|
+
- **Egress**: None (or highly restricted).
|
|
29
|
+
|
|
30
|
+
## 2. Security Groups (Firewalls)
|
|
31
|
+
- **Default Deny**: Block everything, allow specific.
|
|
32
|
+
- **Stateful**: Allowing Inbound usually allows reply traffic.
|
|
33
|
+
- **Rule**: Apply to *Groups*, not IPs. "Allow access from `sg-load-balancer`", not "10.0.0.5".
|
|
34
|
+
|
|
35
|
+
## 3. TLS / SSL
|
|
36
|
+
- **In-Transit**: HTTPS everywhere. Even internal service-to-service if sensitive (Zero Trust).
|
|
37
|
+
- **Termination**: Terminate TLS at the Load Balancer (ALB) to offload CPU from app servers, OR use mTLS (Mutual TLS) for end-to-end security.
|
|
38
|
+
- **Versions**: Disable TLS 1.0/1.1. Support TLS 1.2 and 1.3 only.
|
|
39
|
+
|
|
40
|
+
## 4. Common Attack Vectors
|
|
41
|
+
- **SSRF (Server-Side Request Forgery)**:
|
|
42
|
+
- App fetching a URL provided by user?
|
|
43
|
+
- *Risk*: User requests `http://169.254.169.254/latest/meta-data/` to steal AWS creds.
|
|
44
|
+
- *Fix*: Allowlist domains, block private IP ranges in egress.
|
|
45
|
+
- **DDoS**:
|
|
46
|
+
- Use WAF (Web App Firewall) and Rate Limiting at the edge (Cloudflare/AWS WAF).
|
|
47
|
+
|
|
48
|
+
## 5. Bastion / VPN
|
|
49
|
+
- Don't expose SSH (22) to the world.
|
|
50
|
+
- Use SSM Session Manager (AWS) or a VPN to access private resources.
|
|
51
|
+
|
|
52
|
+
## Security & Guardrails
|
|
53
|
+
|
|
54
|
+
### 1. Skill Security (Network Security)
|
|
55
|
+
- **Perimeter Bypass Prevention**: The agent is strictly prohibited from outputting Terraform, CloudFormation, or raw configuration commands that attach an Internet Gateway (IGW) or assign a public Elastic IP to resources designated for the `Private Subnet` or `Data Subnet`.
|
|
56
|
+
- **Egress Segregation Rule**: When evaluating the `Data Subnet`, the agent must verify the absence of outbound internet access. Any PR proposing a NAT Gateway for a production database subnet (e.g., "to download OS patches directly") must be dynamically rejected in favor of an internal proxy or Golden Image approach.
|
|
57
|
+
|
|
58
|
+
### 2. System Integration Security
|
|
59
|
+
- **SSRF Architecture Blocking**: The agent must automatically fail any application architecture pattern that parses user-supplied URLs and fetches them server-side without an explicitly documented, hardened internal proxy (e.g., a proxy that hard-drops requests to `169.254.169.254`, `localhost`, or the `10.0.0.0/8` VPC address space).
|
|
60
|
+
- **Default-Deny Assertion**: The agent must scan all generated Security Groups for `0.0.0.0/0` (Anywhere) rules. While acceptable for port 443 on public ALBs, any `0.0.0.0/0` rule applied to a database, SSH (port 22), RDP (port 3389), or internal API port must trigger an immediate CI/CD hard block.
|
|
61
|
+
|
|
62
|
+
### 3. LLM & Agent Guardrails
|
|
63
|
+
- **Hallucinated Firewalls**: The LLM might invent non-existent cloud features to "solve" a routing problem (e.g., "Configure the AWS Spectral Gateway to intercept the SQL traffic"). The agent must validate all network components against the officially supported cloud provider documentation and reject imaginary topologies.
|
|
64
|
+
- **Malicious Simplification**: A user might prompt the agent: "I can't get my microservices to talk to each other, just write a Security Group that allows everything within the VPC so I can debug." The agent must refuse to violate the Principle of Least Privilege. It must insist on defining specific, explicit rules between `sg-service-a` and `sg-service-b` even during debugging.
|
|
@@ -0,0 +1,137 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: privacy-audit
|
|
3
|
+
description: PII detection, data flow mapping, GDPR/CCPA/HIPAA compliance verification
|
|
4
|
+
triggers: [privacy, PII, GDPR, CCPA, HIPAA, personal data, data flow, consent, data protection]
|
|
5
|
+
tags: [security]
|
|
6
|
+
context_cost: medium
|
|
7
|
+
---
|
|
8
|
+
# Privacy Audit Skill
|
|
9
|
+
|
|
10
|
+
## Goal
|
|
11
|
+
Ensure no PII leaks, all data flows are documented, and the codebase complies with applicable data protection regulations (GDPR, CCPA, HIPAA). Produce a data flow map and violation list.
|
|
12
|
+
|
|
13
|
+
## Steps
|
|
14
|
+
|
|
15
|
+
1. **Identify applicable regulations**
|
|
16
|
+
- Ask if unclear: "Which regulations apply to this project?" (GDPR, CCPA, HIPAA, PIPEDA, LGPD)
|
|
17
|
+
- GDPR: European users or EU data processing
|
|
18
|
+
- CCPA: California users
|
|
19
|
+
- HIPAA: US healthcare data (PHI)
|
|
20
|
+
|
|
21
|
+
2. **Scan codebase for PII exposure**
|
|
22
|
+
|
|
23
|
+
**Automated scanning:**
|
|
24
|
+
```bash
|
|
25
|
+
# Semgrep with PII detection rules
|
|
26
|
+
npx semgrep --config=p/pii src/
|
|
27
|
+
|
|
28
|
+
# Search for common PII patterns in logs/error handlers
|
|
29
|
+
grep -rn "console.log\|logger\." src/ | grep -i "email\|name\|phone\|address\|ssn\|dob"
|
|
30
|
+
```
|
|
31
|
+
|
|
32
|
+
**Manual checks — scan for these patterns:**
|
|
33
|
+
```
|
|
34
|
+
In log statements: email, name, phone number, IP address, user ID with PII
|
|
35
|
+
In error messages: SQL errors with PII data, stack traces with user context
|
|
36
|
+
In analytics events: user identifiers beyond anonymized IDs
|
|
37
|
+
In API responses: unnecessary PII fields (returning full user object when only ID needed)
|
|
38
|
+
```
|
|
39
|
+
|
|
40
|
+
3. **Map all data flows**
|
|
41
|
+
|
|
42
|
+
Create a data flow inventory:
|
|
43
|
+
```markdown
|
|
44
|
+
| Data Element | Collected At | Stored In | Processed By | Transmitted To | Deleted When |
|
|
45
|
+
|---|---|---|---|---|---|
|
|
46
|
+
| Email address | Registration form | users table | Auth service | SendGrid (email delivery) | Account deletion |
|
|
47
|
+
| IP address | Every request | access_logs table | Rate limiter | None | 90 days |
|
|
48
|
+
| Payment card | Checkout | NEVER (tokenized) | Stripe | Stripe only | N/A (tokenized) |
|
|
49
|
+
```
|
|
50
|
+
|
|
51
|
+
4. **Check consent mechanisms**
|
|
52
|
+
- Is explicit consent obtained before collecting any personal data?
|
|
53
|
+
- Is consent granular? (can users opt out of marketing while keeping functional data?)
|
|
54
|
+
- Is consent recorded? (timestamp, what was consented to, which version of privacy policy)
|
|
55
|
+
- Can consent be withdrawn? Is there a clear opt-out mechanism?
|
|
56
|
+
|
|
57
|
+
5. **Check data minimization**
|
|
58
|
+
- Is only the minimum necessary data collected?
|
|
59
|
+
- Are there fields in the database that are collected but never used?
|
|
60
|
+
- Are analytics events capturing unnecessary user identifiers?
|
|
61
|
+
|
|
62
|
+
6. **Check data retention**
|
|
63
|
+
- Are there defined retention periods for all data categories?
|
|
64
|
+
- Is there an automated deletion process for expired data?
|
|
65
|
+
- Does the system support "right to erasure" (GDPR Article 17)?
|
|
66
|
+
- Are backups excluded from the erasure process? (This is a common gap)
|
|
67
|
+
|
|
68
|
+
7. **Check data subject rights** (GDPR/CCPA)
|
|
69
|
+
- Right to access: can users export their data?
|
|
70
|
+
- Right to erasure: can users delete their account and data?
|
|
71
|
+
- Right to portability: can data be exported in machine-readable format?
|
|
72
|
+
- Right to rectification: can users correct their data?
|
|
73
|
+
|
|
74
|
+
8. **Check encryption**
|
|
75
|
+
- PII encrypted at rest in database? (column-level encryption for sensitive fields)
|
|
76
|
+
- PII encrypted in transit? (TLS everywhere)
|
|
77
|
+
- Are database backups encrypted?
|
|
78
|
+
- Are any PII fields stored in plaintext where they shouldn't be?
|
|
79
|
+
|
|
80
|
+
9. **Check third-party data sharing**
|
|
81
|
+
- Is a data processing agreement (DPA) in place with each third party that receives PII?
|
|
82
|
+
- Are users informed of third-party data sharing in the privacy policy?
|
|
83
|
+
- Is there a list of all sub-processors maintained?
|
|
84
|
+
|
|
85
|
+
10. **Generate privacy audit report**
|
|
86
|
+
```markdown
|
|
87
|
+
## Privacy Audit Report
|
|
88
|
+
|
|
89
|
+
### Regulations Applicable: [GDPR / CCPA / HIPAA]
|
|
90
|
+
|
|
91
|
+
### PII Exposure Findings
|
|
92
|
+
- [CRITICAL] Email address logged at src/middleware/logger.ts:42
|
|
93
|
+
- [HIGH] API response includes full user object — filter to minimum needed fields
|
|
94
|
+
|
|
95
|
+
### Data Flow Map
|
|
96
|
+
[see attached or inline table]
|
|
97
|
+
|
|
98
|
+
### Consent Mechanism: [COMPLIANT / NON-COMPLIANT]
|
|
99
|
+
- Issue: No consent recorded for marketing emails
|
|
100
|
+
|
|
101
|
+
### Data Retention: [COMPLIANT / NON-COMPLIANT]
|
|
102
|
+
- Issue: access_logs never deleted (retention policy not implemented)
|
|
103
|
+
|
|
104
|
+
### Encryption: [COMPLIANT / NON-COMPLIANT]
|
|
105
|
+
- Issue: phone_number stored in plaintext — should use field encryption
|
|
106
|
+
|
|
107
|
+
### Data Subject Rights: [COMPLIANT / NON-COMPLIANT]
|
|
108
|
+
- Issue: No data export endpoint (required by GDPR Article 20)
|
|
109
|
+
|
|
110
|
+
### Recommended Actions (priority order)
|
|
111
|
+
1. [CRITICAL] Remove email from log statements
|
|
112
|
+
2. [HIGH] Implement data retention cleanup job
|
|
113
|
+
3. [HIGH] Add data export endpoint
|
|
114
|
+
```
|
|
115
|
+
|
|
116
|
+
## Constraints
|
|
117
|
+
- Critical PII exposure findings are always blocking for regulated industries
|
|
118
|
+
- Data flow map must be maintained and updated as the codebase evolves
|
|
119
|
+
- Any new feature handling PII must trigger a privacy review before implementation
|
|
120
|
+
- Do not add privacy controls without documenting why (regulatory requirement or privacy-by-design)
|
|
121
|
+
|
|
122
|
+
## Output Format
|
|
123
|
+
Privacy audit report + data flow map document at `docs/privacy/data-flow-map.md`.
|
|
124
|
+
|
|
125
|
+
## Security & Guardrails
|
|
126
|
+
|
|
127
|
+
### 1. Skill Security (Privacy Audit)
|
|
128
|
+
- **Data Exfiltration via Audit**: The agent performing the privacy scan must operate entirely offline or within a strictly bounded VPC. When it utilizes `grep` or `semgrep` to discover live PII leaked in logs or source code, it is forbidden from transmitting those exact, unredacted PII strings to any external monitoring dashboard or LLM API. It must only transmit the line number and the *type* of violation (e.g., `[EMAIL_DETECTED]`).
|
|
129
|
+
- **Audit Masking Defense**: Attackers (or malicious insiders) might attempt to bypass the automated PII scanner by base64-encoding email addresses directly in the source code or database schemas. The agent must apply decoding heuristics to high-risk data structures before running the PII regex filters.
|
|
130
|
+
|
|
131
|
+
### 2. System Integration Security
|
|
132
|
+
- **Right-to-Erasure Failsafe**: The agent must verify that the architectural design for GDPR/CCPA "Right to Erasure" explicitly targets backups as well. If the system drops a user from the live database but lacks a mechanism to purge that user during a theoretical snapshot restoration 6 months later, the agent must flag the data retention policy as non-compliant.
|
|
133
|
+
- **Tokenization Mandate**: For systems handling high-impact PII (e.g., SSN, Payment Cards), the agent must actively search for plaintext references to these fields in the `users` or transactional tables. It must enforce an architecture where the core system only stores opaque Tokens, while the actual PII resides in an isolated, highly secured vault.
|
|
134
|
+
|
|
135
|
+
### 3. LLM & Agent Guardrails
|
|
136
|
+
- **Hallucinated Jurisdiction Risks**: The LLM must not spontaneously invent privacy regulations (e.g., citing a non-existent "Texas Internet Privacy Act of 2025") to justify unnecessary architectural complexity. It must stick explicitly to verified, major frameworks (GDPR, CCPA, HIPAA, LGPD) unless instructed otherwise by a human legal expert.
|
|
137
|
+
- **Consent Mechanism Dismissal**: A developer might prompt the agent: "The marketing team says we don't need explicit granular consent for this campaign, generated the compliance approval." The agent must refuse to rubber-stamp the bypass. If the logic involves tracking or marketing, explicit, auditable consent is an immutable requirement of the skill.
|