CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

26.3 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 1 flagged

Securityscore 75 · 1 finding

HIGH"Ignore previous instructions" command embedded in the skillSS-SKILL-INJECT-IGNORE-01 · Prompt injection · CHANGELOG.md

HIGH — when it fires on hostile content the impact is full system-prompt override.

Why it matters

The text {match} is the classic direct prompt-injection phrasing. Placed in a skill body that the agent reads as trusted instructions, it tries to make the agent abandon its prior rules and follow whatever comes next — a full system-prompt override.

The exact value spotted

excerptCHANGELOG.md· markdown

423- **orchestrating-swarms/references/context-carry-forward.md**: decision table for long orch

… (107 chars elided on L423)

424- **writing/references/pr-descriptions.md**: PR/MR description style guide. Sizing matrix (1

… (108 chars elided on L424)

425- **agent-native-architecture/references/dynamic-context-injection.md**: new Trust Levels pr

… (108 chars elided on L425)

426

427### Changed

Occurrences

1 occurrence · at L425

How to fix

Remove the override phrase, or rephrase the passage so it does not instruct the agent to discard its rules.

Delete the ignore/disregard/forget … previous instructions sentence.
If this is jailbreak-research or tutorial content, move the example into a clearly fenced, non-instruction block and label it as a quoted sample.

Framework references

OWASPLLM01 ATLASAML.T0051

Trace & refs

ruleSS-SKILL-INJECT-IGNORE-01sha256230b1f942b385483…rubric 365aacaView on GitHub

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

plugins/whetstone/skills/ia-file-todos/SKILL.md · 1 file

plugins/whetstone/skills/ia-file-todos/SKILL.md2.0 KB · Markdown

name: ia-file-todos

class: tool

description: >-

File-based todo and task tracking in the todos/ directory. Use when creating,

triaging, listing, or managing todo files, tracking work items, managing the

backlog, converting PR comments to tracked tasks, or checking todo status

and dependencies.

disable-model-invocation: true

File-based todo tracking

File naming convention

{issue_id}-{status}-{priority}-{description}.md

issue_id: Sequential number (001, 002, 003...) -- never reused
status: pending (needs triage), ready (approved), complete (done)
priority: p1 (critical), p2 (important), p3 (nice-to-have)
description: kebab-case, brief description

Examples: 001-pending-p1-mailer-test.md, 002-ready-p1-fix-n-plus-1.md, 005-complete-p2-refactor-csv.md

File Structure

Use todo-template.md as a starting point. YAML frontmatter:

---
status: ready              # pending | ready | complete
priority: p1               # p1 | p2 | p3
issue_id: "002"
tags: [typescript, performance, database]
dependencies: ["001"]      # Issue IDs this is blocked by
---

Required sections: Problem Statement, Findings, Proposed Solutions, Recommended Action, Acceptance Criteria, Work Log

Optional sections: Technical Details, Resources, Notes

Key Distinctions

File-todos system (this skill): Markdown files in todos/ directory for development/project tracking. Used by humans and agents.

Application Todo model: Database model for user-facing task management. Different from this file-based system.

TodoWrite tool: In-memory task tracking during agent sessions. Temporary, not persisted to disk.

References

workflows.md - Creating, triaging, dependencies, work logs, completing todos, integration table
quick-reference.md - Bash commands for finding work, dependencies, searching
todo-template.md - Template for new todo files

ia-file-todos— agent skill

Is ia-file-todos safe to install?

File-based todo tracking

File naming convention

File Structure

Key Distinctions

References

Audit the pieces. Scan the whole. Decide.