fix: apply prose injection rules to .txt and .yaml files - #30
Merged
royalpinto007 merged 1 commit intoSep 12, 2026
Merged
Conversation
Prose rules (prompt-injection) previously ran only when isMarkdown was true, so the same malicious text in .txt or .yaml was never checked. Introduce isProseFile and use it in ruleApplies. Fixes AgentPostmortem#3 Co-authored-by: Sharad. <sharadvc@users.noreply.github.com>
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Prompt-injection rules with
appliesTo: "prose"only ran for markdown..txt/.yaml/.ymlwere already collected as text files but skipped for prose rules. They now share the same prose path; fence handling stays markdown-only.Test plan
npm test— assertsSKILL-INJ-001on.txtand.yaml, and that.jsondoes not get prose-only rulesFixes #3