ClawHub
Back to skill

Security audit

Hindi

Security checks for vulnerabilities and agentic risk

Overview

This skill only gives style guidance for more natural Hindi/Hinglish writing and does not request tools, persistence, credentials, or system access.

Install only if you want a Hindi style assistant that leans casual and may mix English into Hindi. For formal writing, respectful address, pure Hindi, or a specific regional/script preference, tell the agent explicitly.

A.I.G

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

SkillSpector

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 (3)

Natural-Language Policy Violations

Medium
Confidence
97% confidence
Finding
The description instructs the skill to "Write Hindi that sounds human," which imposes a specific language behavior by default. This is a natural-language policy concern because the file does not offer the user a language/locale choice or state that Hindi is only used when explicitly requested.

Natural-Language Policy Violations

Medium
Confidence
93% confidence
Finding
The line says to "lean casual" unless explicitly formal, making a specific Hindi register the default regardless of user preference. Because the skill does not present this as an opt-in or user-selected style, it constitutes a language/locale policy issue.

Natural-Language Policy Violations

Medium
Confidence
96% confidence
Finding
This instruction tells the model to add English mixing whenever the output appears too formal, effectively forcing a specific bilingual style. That is a policy concern because no user opt-in or language preference check is required before changing the language/register.

Static analysis

No suspicious patterns detected.