T09 · Insecure Skill Coding Practices
- Location
SKILL.md:365- Finding
Agent Identity Verification Can Be Bypassed When the Agent ID Header Is Omitted
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is a non-executable guide, but some production migration examples could expose credentials or sensitive API data if copied as written.
Treat this as a Review item before installing or following it. It does not auto-run code, but do not copy the shadow traffic or baseline recorder examples into production without strict header allowlists, body redaction, approved destination hosts, dry-run controls for non-idempotent requests, and a policy that raw production captures are not committed to version control. Also fix the identity-verification fail-closed behavior before relying on the adapter for authenticated agent access.
SKILL.md:365Agent Identity Verification Can Be Bypassed When the Agent ID Header Is Omitted
SKILL.md:1969Shadow Traffic Replay Forwards Sensitive Credentials and Production Request Data
SKILL.md:1847Baseline Recorder Persists Unredacted API Data and Recommends Committing It to Version Control
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# Response headers on 402:
X-Price: 0.05
X-Currency: USD
X-Payment-URL: https://api.greenhelix.net/v1/payments/create
X-Payment-Methods: greenhelix-escrow, x402-direct
X-Price-Window: 300 # price valid for 300 seconds
The surrounding documentation says agent sessions are 'stateless by design' and frames continuity through idempotency keys and request correlation, but the provided example implements AgentSessionStore, an in-memory server-side session registry keyed by generated session IDs. That directly contradicts the stated stateless model and could mislead readers about the migration approach being recommended.
The line states discovery mode 'does not actually process payments,' but the guide's surrounding migration examples prominently implement live escrow verification and payment-enforcing middleware. While the guide is educational, this sentence can be read as describing the shown implementation path even though no discovery-mode-specific code is provided here.