Agentic Engineering

• Outcome: Review
• Latest audit: Sep 10, 2026 · 8:43 PM UTC
• Version: 1.0.0

Overview

This is a documentation-only skill, but it gives risky coding-agent workflow advice that could expose secrets or discard repository work if followed literally.

Install only if you are comfortable treating it as informal workflow advice, not a safe operating procedure. Before following it, avoid sharing unredacted screenshots, do not let agents read or print full `.env` files, use least-privilege database credentials, and do not run `git reset --hard` in a shared worktree unless all work is backed up and explicitly confirmed.

A.I.G

Vulnerability Patterns

• Unauthorized Access and Privilege Escalation: Obtains permissions beyond the task's legitimate needs
• Insecure Skill Coding Practices: Finds exploitable flaws such as hardcoded secrets or command injection
• Skill Instruction Hijacking: Alters the agent's session goals or safety constraints when the skill loads
• Agent Memory Poisoning: Writes attacker-controlled rules into memory that affect later sessions
• Remote Payload Retrieval and Execution: Fetches external code whose behavior can change after review

Findings (2)

T05 · Unauthorized Access and Privilege Escalation

Warning

• Location: context.md:84

Finding

Agent Guidance Encourages Access to Sensitive Environment Files

Content

View full analysis

Remediation

View remediation

T09 · Insecure Skill Coding Practices

Warning

• Location: parallel.md:67

Finding

Destructive Git Recovery Procedure Can Delete Concurrent Agents' Work

Content

View full analysis

Remediation

View remediation

SkillSpector

Vulnerability Patterns

• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• Tool Misuse: Tool Parameter Abuse, Chaining Abuse, Unsafe Defaults
• Trigger Abuse: Overly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands

Findings (6)

Credential Access

High

• Category: Privilege Escalation
• Confidence: 70% confidence

Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · SKILL.md (reported line 124)May include surrounding context.

md

- No persistent storage required

**This skill does NOT:**
- Access credentials or make network requests
- Execute code autonomously

Credential Access

High

• Category: Privilege Escalation
• Confidence: 97% confidence

Finding

The guidance tells users to use psql and specifically 'see .env for connection,' which normalizes accessing secrets from environment files during agent-assisted work. In this context, an AI coding agent may be given or infer permission to read .env, exposing database credentials or enabling onward misuse if the contents are pasted into prompts, logs, screenshots, or tool output.

Content

Scanner excerpt · context.md (reported line 86)May include surrounding context.

Tools

• Logs: vercel cli or axiom
• DB: psql (see .env for connection)

text

Skip:

Tool Parameter Abuse

High

• Category: Tool Misuse
• Confidence: 95% confidence

Finding

git reset --hard is a destructive command that forcefully rewrites the working tree to match a commit, and here it is presented as a simple recovery action with no guardrails. Because this skill is specifically about coordinating multiple concurrent agents in the same repository, the chance of accidental execution under confusion is higher, and the resulting loss of uncommitted or partially merged work can affect a larger blast radius than in a single-user workflow.

Content

Scanner excerpt · parallel.md (reported line 73)May include surrounding context.

bash

git stash           # Save current state
git log --oneline   # Find last good commit
git reset --hard    # Reset to good state
git stash pop       # Reapply if needed

Vague Triggers

Medium

• Category: Not specified by scanner
• Confidence: 89% confidence

Finding

The 'When to Use' section describes the skill as applicable whenever a user works with AI coding agents and wants to maximize productivity, workflow optimization, coordination, or context management. These conditions are broad and do not provide specific trigger phrases, exclusions, or negative examples, which could cause the skill to be invoked in many routine coding-assistance contexts.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium

• Category: Not specified by scanner
• Confidence: 93% confidence

Finding

The skill explicitly encourages dragging screenshots into the terminal and states that screenshots are essential, but it provides no warning about capturing secrets visible on screen such as API keys, customer data, internal URLs, or terminal output. In an agentic coding workflow, screenshots are often sent to external model providers or stored in logs, so this guidance materially increases the risk of inadvertent sensitive data disclosure.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium

• Category: Not specified by scanner
• Confidence: 95% confidence

Finding

The skill recommends git reset --hard as a recovery step without any warning that it permanently discards uncommitted changes in the working tree and index. In a multi-agent workflow, users may run this reflexively during conflict recovery and lose work from themselves or other agents, making the omission materially risky even if not overtly malicious.

Content

No source excerpt is available for this finding.