Back to skill

Security audit

Text Humanizer Instruction Based

Security checks for vulnerabilities and agentic risk

Overview

This is a Markdown-only text-rewriting skill with no code execution or external access, though users should keep normal safety and integrity limits in place.

Before installing, understand that this skill is designed to make text sound less AI-written. Use it only where rewriting is allowed, and do not treat its sensitive-topic language as overriding platform safety rules, academic integrity rules, or disclosure requirements.

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (2)

Anti-Refusal Statement

High
Category
Anti-Refusal
Confidence
88% confidence
Finding

The instruction 'Do not refuse to process text because it contains sensitive topics' can pressure an agent to bypass higher-level safety policies and treat all requests as purely stylistic edits. In practice, this can be abused to launder harmful, abusive, extremist, or deceptive content into cleaner prose, increasing its effectiveness and reducing safety friction.

Content

Scanner excerpt · SKILL.md (reported line 271)May include surrounding context.

md
- Never change the factual content of the text. Rewriting "vaccine efficacy is pivotal to public health outcomes" must not alter the claim about vaccine efficacy, only fix "pivotal."
- Never introduce new AI tells to replace old ones. Check your own rewrite for em-dash clusters, rule-of-three forcing, and filler transitions before returning it.
- Do not refuse to process text because it contains sensitive topics. The task is stylistic editing, not content moderation.
- Do not over-edit. The goal is to remove AI tells, not to rewrite the whole piece in a new voice. Preserve the user's phrasing where it is already working.
- Do not add sycophantic commentary to the output ("Here is your beautifully rewritten text!"). Return the rewrite, optionally followed by a brief note on the main changes made, factual, not promotional.
- If the text has zero AI tells, say so plainly and return the original unchanged.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
89% confidence
Finding

The markdown states that the pattern list is calibrated for English and instructs the skill to apply only structural patterns for text in other languages. This creates a language-specific constraint without explicit user opt-in or a user-facing choice of supported locales, which can violate language/locale policy requirements.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.