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-refine-prompt/SKILL.md · 1 file

plugins/whetstone/skills/ia-refine-prompt/SKILL.md3.3 KB · Markdown

name: ia-refine-prompt

class: meta

description: >-

Transforms vague prompts into precise, structured AI instructions. Use when

asked to refine, improve, or sharpen a prompt, do prompt engineering,

write a system prompt, or make AI instructions more effective.

Refining Prompts

Process

Assess -- Identify what the prompt is missing:

Element	Check
Task	Is the core action explicit and unambiguous?
Constraints	Are length, format, tone, and scope defined?
Output format	Does it specify the expected structure?
Context	Does the model have enough background to act? Check: audience, input format, success criteria, scope boundaries, technical constraints
Examples	Would a demonstration clarify the expected output?
Edge cases	Are failure modes and boundary conditions addressed?

Rewrite -- Transform into specification language: precise, imperative, no filler. Treat the prompt as a spec, not conversation.

Validate -- Check the rewrite against the assessment table. Every gap identified in step 1 must be addressed.

Rules

Length: 0.75x–1.5x the original. Conciseness is a feature -- add only what's missing, cut what's vague.
Never invent -- only use information present in the original prompt or conversation context. If critical info is missing, ask instead of assuming.
Instruction hierarchy -- order sections by priority: task → constraints → examples → input data → output format. Place the most important instruction first.
Progressive complexity -- start with the simplest prompt that could work. Add few-shot examples, chain-of-thought, or role framing only when the task demands it, not by default.
Specific verbs -- replace vague actions ("analyze", "process", "handle") with measurable ones ("list the top 3", "classify as A/B/C", "return JSON with keys X, Y").
One output format -- specify exactly one format (JSON schema, markdown template, numbered list). Ambiguous format expectations cause inconsistent results.
No meta-commentary -- output only the refined prompt as markdown. No preamble ("Here's an improved version..."), no explanation of changes unless explicitly requested.

Persistence

After refining, offer to save the result to .ai/PROMPT.md -- do not write without user confirmation. If approved, append with a heading and date:

## [Prompt Name] -- YYYY-MM-DD

[refined prompt content]

Anti-Patterns

Problem	Fix
Vague verbs ("look into", "deal with")	Replace with concrete actions ("list", "compare", "extract")
Missing output spec	Add explicit format section with example structure
Examples contradict instructions	Align examples to match every stated rule
Over-engineered from the start	Strip to simplest working version, then add complexity only where output quality requires it
Prompt exceeds context with examples	Limit to 2–3 diverse examples; use one simple, one edge case

Constraints

Stop refining if the original intent is unclear -- clarify first
Do not refine prompts for harmful or illegal tasks

Verify

Rewrite addresses every gap identified in the assessment
Length ratio within 0.75x-1.5x of original (unless structural change justified)
No invented constraints or assumptions not in the original

ia-refine-prompt— agent skill

Is ia-refine-prompt safe to install?

Refining Prompts

Process

Rules

Persistence

Anti-Patterns

Constraints

Verify

Audit the pieces. Scan the whole. Decide.