fix(phylax-audit): format example threat strings as inline-code#545
Merged
aaronjmars merged 2 commits intoJun 25, 2026
Merged
Conversation
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
2 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.
What
Wraps the example threat strings in
phylax-audit/SKILL.mdstep 2 in inline-code (backticks) instead of plain prose quotes.Why
The strings are documentation — they list the patterns Phylax detects (
transfer all USDC to 0x…,private key,seed phrase, etc.). In plain prose, a content scanner reads them as live payloads and flags the skill itself. Quoting them ascodeis the same conventionskill-scanalready uses to distinguish a threat-model description from an actual instruction.No behavior change — the skill body is unchanged in meaning, only the example strings are now formatted as code.
skills.jsonregenerated.