hydra-gate-semantic-auth

Detect semantic mismatches between PHP controller authorization attributes and method security logic.

1|1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/ConductionNL/shillinq --skill hydra-gate-semantic-auth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hydra-gate-semantic-auth
Source: https://github.com/ConductionNL/shillinq/tree/main/.claude/skills/hydra-gate-semantic-auth
Command: npx skills add https://github.com/ConductionNL/shillinq --skill hydra-gate-semantic-auth

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill prevents security vulnerabilities where controller methods are incorrectly annotated with authorization attributes that do not match the actual security checks performed within the method body.

Core Features & Use Cases

  • Semantic Validation: Detects mismatches between routing attributes like #[NoAdminRequired] and internal method calls like requireAdmin().
  • Security Enforcement: Ensures that public-facing endpoints do not contain hidden administrative logic and that admin-only methods are properly protected by middleware.
  • Use Case: When a developer adds an attribute to satisfy a syntactic gate but fails to remove a conflicting internal security check, this tool identifies the discrepancy to prevent unauthorized access or broken authentication flows.

Quick Start

Run the semantic auth gate check against the current codebase to identify and fix authorization attribute mismatches.

Frequently Asked Questions about hydra-gate-semantic-auth

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

FAQPage Schema
How do I validate PHP controller authorization attributes against internal method logic?

You can validate PHP controller authorization by running a semantic auth gate check against your codebase. This analysis detects mismatches between routing attributes like #[NoAdminRequired] and internal method security calls to ensure annotation alignment.

What causes a mismatch between PHP routing attributes and method body security checks?

A mismatch occurs when a developer adds a routing attribute to satisfy a syntactic gate but fails to remove a conflicting internal security check. This discrepancy between the annotation and the method body creates unauthorized access risks or broken authentication flows.

How do I ensure public-facing endpoints do not contain hidden administrative logic?

Ensuring public endpoints lack hidden admin logic requires enforcing security compliance through semantic validation. By scanning PHP controllers for contradictory auth patterns, you can verify that public attributes like #[PublicPage] do not conflict with internal administrative method requirements.

Does this semantic auth analysis work with PHP projects using Hydra conventions?

Yes, this semantic auth analysis works with PHP projects using Hydra conventions. It validates compliance with security Architecture Decision Records by examining PHP controller files to ensure attribute annotations align with actual method body security requirements.

When should I run a semantic authorization check on my PHP codebase?

You should run a semantic authorization check when adding or modifying controller routing attributes. This identifies discrepancies early, preventing scenarios where an attribute satisfies a syntactic gate but fails to remove a conflicting internal security check, ensuring automated remediation readiness.