openspec-verify-change
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
92%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
The canonical home for this skill is openspec-verify-change in PBH-BTN/PeerBanHelper
W011: Third-party content exposure detected (indirect prompt injection risk).
What this means
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Why it was flagged
The workflow fetches and reads change “contextFiles” via `openspec instructions apply --json`, then extracts free-form text from artifacts like `tasks.md` and `specs/` (outsider-authored by upstream change authors in the change directory), which the agent will ingest into LLM context for parsing and verification.
- Repository
PBH-BTN/PeerBanHelper
- Revision
a1b1216
- Audited
- Security analysis
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.