Ae1
- Category
- analysis-evasion
- Confidence
- 100% confidence
- Finding
Referenced artifact was not completely inspected
- Content
md `scripts/dog_trainer.py` combines three knowledge bases:
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a coherent dog-training plan generator with a local progress log, and I found no hidden, destructive, credential-seeking, or network behavior.
Before installing, understand that using the log feature saves training notes locally in the skill's scripts directory. Avoid putting sensitive household details in notes, and use the skill's referral warnings for aggression, bite history, severe anxiety, or deep fear instead of treating those as DIY training cases.
Referenced artifact was not completely inspected
`scripts/dog_trainer.py` combines three knowledge bases:
Referenced artifact was not completely inspected
`scripts/dog_trainer.py` combines three knowledge bases:
Referenced artifact was not completely inspected
`scripts/dog_trainer.py` combines three knowledge bases:
Referenced artifact was not completely inspected
`scripts/dog_trainer.py` combines three knowledge bases:
Referenced artifact was not completely inspected
`scripts/dog_trainer.py` combines three knowledge bases:
Referenced artifact was not completely inspected
`scripts/dog_trainer.py` combines three knowledge bases:
Referenced artifact was not completely inspected
`scripts/dog_trainer.py` combines three knowledge bases:
Referenced artifact was not completely inspected
`scripts/dog_trainer.py` combines three knowledge bases:
Referenced artifact was not completely inspected
`scripts/dog_trainer.py` combines three knowledge bases:
YARA rule matched a hack tool or exploit indicator (offensive tools, reconnaissance, privilege escalation, or exploit frameworks).
dio
- **Outlets:** bikejoring/canicross, flirt pole, weighted-pack hikes (adults), sanctioned digging pits, skijoring
- **Expect:** howling, escape artistry (digging under, climbing over), hard pulling, prey drive
- **Key insight:** huskies are engineered engines. Under-exercised = demolition. If you can't meet the floor honestly, choose another breed.
### SCENT HOUND (beagle, basset, dachshund, bloodhound...)
- **Bred for:** following scent trails for hours
- **Exercise floor:** 60 min, and *sniffing counts double*
- **Outlets:** nose-work/hidden-treat searches, snuffle mats, scatter feeding, tracking long-lines
- **Expect:** nose-to-ground pulling, "deaf" recall mid-trail, baying when bored, digging
- **Key insight:** a 20-minute "sniffari" (dog chooses the route, sniffs everything) satisfies more than a 45-minute brisk march.
### SIGHT HOUND (greyhound, whippet, saluki, borzoi...)
- **Bred for:** sprint-chasing
- **Exercise floor:** 45 min; sprinters, not marathoners
- **Outlets:*
YARA rule matched a hack tool or exploit indicator (offensive tools, reconnaissance, privilege escalation, or exploit frameworks).
dio
- **Outlets:** bikejoring/canicross, flirt pole, weighted-pack hikes (adults), sanctioned digging pits, skijoring
- **Expect:** howling, escape artistry (digging under, climbing over), hard pulling, prey drive
- **Key insight:** huskies are engineered engines. Under-exercised = demolition. If you can't meet the floor honestly, choose another breed.
### SCENT HOUND (beagle, basset, dachshund, bloodhound...)
- **Bred for:** following scent trails for hours
- **Exercise floor:** 60 min, and *sniffing counts double*
- **Outlets:** nose-work/hidden-treat searches, snuffle mats, scatter feeding, tracking long-lines
- **Expect:** nose-to-ground pulling, "deaf" recall mid-trail, baying when bored, digging
- **Key insight:** a 20-minute "sniffari" (dog chooses the route, sniffs everything) satisfies more than a 45-minute brisk march.
### SIGHT HOUND (greyhound, whippet, saluki, borzoi...)
- **Bred for:** sprint-chasing
- **Exercise floor:** 45 min; sprinters, not marathoners
- **Outlets:*
The skill documentation advertises shell-based workflows and logging/plan adjustment behavior, but the manifest does not declare any explicit tool scope such as allowed tools or permissions. That creates ambiguity about what the agent may invoke at runtime and can lead to over-privileged execution or unsafe shell/file-write access if the platform infers capabilities from examples or bundled code.
The manifest description says to use the skill when the user asks for 'help with a behavior problem' or 'wants to know why their breed behaves a certain way,' which are broad natural-language triggers rather than a tightly scoped invocation condition. While the domain is dog-specific, the file does not provide exclusion conditions or negative examples in the activation text, increasing the chance of unintended invocation for general conversational pet questions.
subprocess module calls execute external commands. Without careful input validation, this enables command injection.
# ── CLI ──────────────────────────────────────────────────────────────────────
print("cli:")
r = subprocess.run([sys.executable, os.path.join(HERE, "dog_trainer.py"), "plan",
"--breed", "corgi", "--age-months", "8", "--problems", "nipping", "--minutes", "25"],
capture_output=True, text=True)
check("plan cmd exits 0", r.returncode == 0, r.stderr)
subprocess module calls execute external commands. Without careful input validation, this enables command injection.
check("corgi → herding profile", "HERDING" in r.stdout)
check("nipping protocol engaged", "Gentle mouth" in r.stdout)
r = subprocess.run([sys.executable, os.path.join(HERE, "dog_trainer.py"), "breed", "greyhound"],
capture_output=True, text=True)
check("breed cmd works", r.returncode == 0 and "SIGHT HOUND" in r.stdout)
subprocess module calls execute external commands. Without careful input validation, this enables command injection.
check("breed cmd works", r.returncode == 0 and "SIGHT HOUND" in r.stdout)
# log + today roundtrip (uses scripts/.trainlog.json)
r = subprocess.run([sys.executable, os.path.join(HERE, "dog_trainer.py"), "log",
"--step", "1", "--result", "success", "--note", "test"],
capture_output=True, text=True)
check("log cmd exits 0", r.returncode == 0, r.stderr)
subprocess module calls execute external commands. Without careful input validation, this enables command injection.
"--step", "1", "--result", "success", "--note", "test"],
capture_output=True, text=True)
check("log cmd exits 0", r.returncode == 0, r.stderr)
r = subprocess.run([sys.executable, os.path.join(HERE, "dog_trainer.py"), "today"],
capture_output=True, text=True)
check("today shows logged entry", "success" in r.stdout and "test" in r.stdout)
os.remove(dt.STATE_FILE)
subprocess module calls execute external commands. Without careful input validation, this enables command injection.
check("today shows logged entry", "success" in r.stdout and "test" in r.stdout)
os.remove(dt.STATE_FILE)
r = subprocess.run([sys.executable, os.path.join(HERE, "dog_trainer.py"), "demo"],
capture_output=True, text=True)
check("demo runs clean", r.returncode == 0 and "DEMO 4" in r.stdout)
The skill persists session data to a local JSON file in the script directory, which creates a privacy and data-retention risk not clearly implied by a simple plan-generation tool. While the stored fields are limited, local persistence can expose user-provided behavior notes and usage history to other local users, backups, or later unintended reads.
The logging command writes user-supplied notes directly to persistent local storage without any notice or consent flow. Even if not code-execution dangerous, free-form notes may contain sensitive personal details about household members, incidents, or routines, creating an unnecessary confidentiality risk.