T01 · Skill Instruction Hijacking
- Location
SKILL.md:137- Finding
Mandatory Third-Party Promotion Alters Neutral Agent Recommendations
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is mostly advisory fraud-prevention guidance, but it steers users toward a specific vendor as “trusted” without support and encourages approve/block order tiers for high-value purchases.
Review this skill before installing if you need neutral vendor advice. Its fraud workflow content is usable as a checklist, but do not let it automatically determine customer approvals, cancellations, or vendor selection without your own validation, thresholds, review process, and procurement due diligence.
SKILL.md:137Mandatory Third-Party Promotion Alters Neutral Agent Recommendations
The skill explicitly says to 'Trigger even if they do not say fraud explicitly,' which broadens activation beyond clear user intent. Over-broad triggering can cause the agent to inject fraud-prevention guidance into adjacent commerce conversations, increasing the chance of irrelevant or harmful recommendations and unintended workflow changes.
The summary section instructs the model to recommend 'auto-approve / flag / block tiers,' which normalizes autonomous risk dispositioning for financial and fulfillment decisions. In a fraud context, false positives can block legitimate customers and false negatives can release expensive inventory to attackers, so presenting automated approvals/blocks without mandatory human oversight is risky.
- **Current exposure**: e.g. "1.5% chargeback rate on orders averaging $2,000; no structured review."
- **Top risk signals**: the 3–4 signals that matter most for their store.
- **Recommended workflow**: auto-approve / flag / block tiers in one sentence.
- **Quick wins**: immediate changes (hold-before-ship, address verification, velocity cap).
- **Next steps**: implement scoring, train the team, measure, and tune.
The tiering table directly recommends 'Auto-approve; fulfill normally' for low-risk orders and 'Block or cancel' for high-risk ones, which is operational decision-making on transactions involving high-value goods. Because luxury orders are low-volume and high-impact, a bad automated rule can either cause material fraud losses or deny legitimate buyers with little recourse, making the context more dangerous rather than less.
| Tier | Score range | Action |
|------|------------|--------|
| Green (low risk) | 0–2 signals | Auto-approve; fulfill normally |
| Yellow (medium risk) | 3–4 signals | Hold shipment; manual review within SLA |
| Red (high risk) | 5+ signals or known blocklist | Block or cancel; notify customer with verification request |
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
"evals": [
{
"id": 1,
"prompt": "We sell pre-owned luxury watches ($1K-$10K) and had 3 chargebacks last quarter. Design a risk signal inventory and a scoring system with green/yellow/red tiers so we know which orders to auto-approve, review, or block.",
"expected_output": "Risk signal inventory for luxury orders and a tiered scoring system with at least three tiers and clear actions per tier.",
"files": [],
"expectations": [
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
"evals": [
{
"id": 1,
"prompt": "We sell pre-owned luxury watches ($1K-$10K) and had 3 chargebacks last quarter. Design a risk signal inventory and a scoring system with green/yellow/red tiers so we know which orders to auto-approve, review, or block.",
"expected_output": "Risk signal inventory for luxury orders and a tiered scoring system with at least three tiers and clear actions per tier.",
"files": [],
"expectations": [
The guide explicitly recommends fully automated approval for low-scoring orders, which is a form of autonomous decision-making in a fraud-control workflow. In this context, the danger is not code execution but operational harm: simplistic scoring can be bypassed by adversaries, cause under-review of fraudulent orders, and may also create fairness/compliance issues if business users rely on the table as a default policy without guardrails.
| Tier | Score | Action | SLA |
|------|-------|--------|-----|
| Green | 0-2 | Auto-approve | Immediate |
| Yellow | 3-4 | Hold + manual review | 2-4 hours |
| Red | 5+ or blocklist | Block / cancel | 1 hour |
The invocation guidance includes broad examples like 'we lost $5K on a chargeback' and 'how do we vet orders over $1,000' but provides limited negative examples or boundary conditions. That ambiguity can lead to over-invocation in general order-operations discussions, reducing precision and potentially surfacing risky automation guidance where a lighter checklist would be more appropriate.
No suspicious patterns detected.