Back to skill

Security audit

Microsoft To Do

Security checks across malware telemetry and agentic risk

Overview

The skill does what it says, but it needs review because it tells agents to bypass delete confirmations for Microsoft To Do data and gives weak guidance for stored OAuth secrets.

Install only if you trust the upstream `microsoft-todo-cli` package and are comfortable granting it Microsoft To Do access. Require explicit confirmation before any task, step, note, or list deletion, preferably after the agent shows the exact target and uses a stable ID. Treat `keys.yml` and OAuth token files as secrets: restrict local file permissions, do not paste or log their contents, and rotate the Azure client secret if it is exposed.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (5)

Missing User Warnings

Medium
Confidence
93% confidence
Finding
The skill documents destructive deletion of tasks using `todo rm "Task" -y --json`, which explicitly suppresses confirmation and provides no safety guidance. In an agentic context, this increases the chance of irreversible task deletion from ambiguous task names, stale context, or mis-targeted automation.

Missing User Warnings

Medium
Confidence
92% confidence
Finding
The documented `todo rm-list "Project X" -y --json` command deletes an entire list and suppresses confirmation without warning. Because lists may contain many tasks, accidental or automated misuse can cause broader data loss than single-task deletion.

Missing User Warnings

Medium
Confidence
96% confidence
Finding
The note explicitly says to 'Always use `-y` with `rm` commands to skip confirmation,' which operationalizes unsafe behavior for all removals. In a skill meant for automation, this reduces human oversight and makes accidental destructive actions significantly more likely.

Missing User Warnings

Medium
Confidence
95% confidence
Finding
The setup instructions direct users to store a Microsoft OAuth client secret in a plaintext YAML file under their home directory without any warning about file permissions, secret storage risks, or safer alternatives. If the host is shared, backed up insecurely, checked into source control, or compromised by local malware, the secret could be exposed and abused to impersonate the registered application.

Autonomous Decision Making

Medium
Category
Excessive Agency
Content
## Notes

- **Always use `--json`** for all commands to get structured output
- **Always use `-y`** with `rm` commands to skip confirmation
- Use `--id` with `-l ListName` for list context
- First run opens browser for OAuth authentication
Confidence
84% confidence
Finding
skip confirmation

VirusTotal

66/66 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.