Back to skill

Security audit

Kansodata Jira Ops

Security checks for vulnerabilities and agentic risk

Overview

This skill is a read-only Jira analysis helper with clear limits against changing Jira data.

Install this only if you are comfortable letting the agent read Jira issues, comments, worklogs, projects, statuses, and transitions available through your Jira plugin. It should not create, edit, comment on, assign, or transition Jira items, and users who do not work in Spanish may want translated instructions or examples.

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

Ae1

High
Category
analysis-evasion
Content
Ver `examples.md` en esta misma carpeta.
Confidence
100% confidence
Finding
Referenced artifact was not completely inspected

Natural-Language Policy Violations

Medium
Confidence
96% confidence
Finding
This markdown file contains user-facing instructions and descriptions exclusively in Spanish, including the skill description, purpose, operational modes, and safety rules. Under the language/locale policy, forcing a specific language without user opt-in is a natural-language policy concern unless the locale restriction is explicitly justified.

Natural-Language Policy Violations

Medium
Confidence
95% confidence
Finding
The file’s natural-language content, including headings, prompts, and expected outputs, is entirely in Spanish. Under the policy, forcing a specific language without user opt-in or a documented justification is a natural-language policy violation.

Natural-Language Policy Violations

Medium
Confidence
93% confidence
Finding
The file presents all user-facing natural-language instructions in Spanish, which can force a specific language on users without opt-in. Under the policy, this is a language/locale constraint unless the skill offers a choice or clearly documents a justified region-specific limitation, which this file does not do.

Natural-Language Policy Violations

Medium
Confidence
92% confidence
Finding
This markdown file contains user-facing operational rules exclusively in Spanish, and there is no indication that users may choose another language or that the locale restriction is justified. Under the policy, forcing a specific language without user opt-in is a natural-language policy violation.

Static analysis

No suspicious patterns detected.