sensei — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited sensei (Agent Skill) and scored it 96/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 1 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 1 flagged
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
When user says "sensei help" or asks how to use sensei, show this:
╔══════════════════════════════════════════════════════════════════╗
║ SENSEI - Skill Frontmatter Compliance Improver ║
╠══════════════════════════════════════════════════════════════════╣
║ ║
║ USAGE: ║
║ Run sensei on <skill-name> # Single skill ║
║ Run sensei on <skill1>, <skill2>, ... # Multiple skills ║
║ Run sensei on all skills # All skills ║
║ ║
║ EXAMPLES: ║
║ Run sensei on appinsights-instrumentation ║
║ Run sensei on azure-ai, azure-compute ║
║ ║
║ WHAT IT DOES: ║
║ 1. READ - Load skill's SKILL.md and tests ║
║ 2. VERIFY - Compare skill frontmatter with convention ║
║ 3. SCAFFOLD - Create tests from frontmatter if missing ║
║ 4. IMPROVE - Add WHEN: triggers ║
║ 5. TEST - Run tests, fix if needed ║
║ 6. SUMMARY - Show before/after with suggestions ║
║ 7. PROMPT - Ask: Commit, Create Issue, or Skip? ║
║ 8. REPEAT - Until routing tests pass ║
╚══════════════════════════════════════════════════════════════════╝For each skill, execute this loop until the frontmatter aligns with convention, have thorough routing tests AND routing tests pass:
plugins/{plugin}/skills/{skill-name}/SKILL.md, and vally eval suites in evals/{skill-name}/*.yaml.evals/{skill-name}/ doesn't exist, follow instructions in vally-eval skill to scaffold a set of routing tests. The routing tests test if the skill can be invoked for target user prompts. Generate user prompts that match the target scenario of the skill's description.vally-eval skill to run the routing tests. If there are failed tests, suggest fixes.plugins/{plugin}/skills/ - these are the Azure skills used by Copilot.github/skills/ should be left as is~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.