T09 · Insecure Skill Coding Practices
- Location
framework/components/agent-init.md:68- Finding
Unvalidated Workspace Identifier Enables Path Traversal Outside the Workspace Root
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is a transparent crypto research framework, but it needs Review because workspace names are used directly in file paths, which can let an agent read or write outside the intended folder if given unsafe input.
Before installing, be comfortable with the agent reading local framework/workspace documents, using web search for public crypto research, and writing reports plus workflow state locally. Use only simple workspace IDs matching lowercase letters, numbers, and hyphens; avoid untrusted workspace names or prompts that supply path-like IDs. The publisher should add strict workspace ID validation, canonical path confinement, and confirmation before first writes.
framework/components/agent-init.md:68Unvalidated Workspace Identifier Enables Path Traversal Outside the Workspace Root
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
---
<!--
============================================================================
HOW TO USE THIS TEMPLATE
============================================================================
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
<!--
UNIVERSAL WORKFLOW TEMPLATE
INSTRUCTIONS:
- Copy to: {workflow-name}/template.md
The template embeds operative instructions inside an HTML comment, including directives to recall and apply another guide and perform validation against another file. Hidden instructions are risky because an agent may treat non-user-visible content as authoritative workflow guidance, enabling indirect prompt injection, instruction smuggling, or unexpected expansion to additional files without explicit user consent.
<!--
SESSION SUMMARY TEMPLATE
INSTRUCTIONS:
- Recall & Apply: {brainstorming-guide} (./framework/guides/brainstorming-guide.md)
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
<!--
COMPETITIVE ANALYSIS TEMPLATE
INSTRUCTIONS:
- Recall & Apply: {output-standards} (./framework/guides/output-standards.md)
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
<!--
BLOG ARTICLE TEMPLATE
INSTRUCTIONS:
- Recall & Apply: {content-style} (./framework/guides/content-style.md)
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
<!--
TIKTOK SCRIPT TEMPLATE
INSTRUCTIONS:
- Recall & Apply: {content-style} (./framework/guides/content-style.md)
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
<!--
X THREAD TEMPLATE
INSTRUCTIONS:
- Recall & Apply: {content-style} (./framework/guides/content-style.md)
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
<!--
YOUTUBE SCRIPT TEMPLATE
INSTRUCTIONS:
- Recall & Apply: {content-style} (./framework/guides/content-style.md)
The HTML comment contains hidden operational instructions such as recalling external standards and validation guidance that may be consumed by an agent but are not visible in normal rendered output. Hidden instructions are dangerous because they create a covert control channel that can override user expectations, introduce unreviewed behavior via referenced files, and make security review harder in a human-AI collaboration workflow.
<!--
INVESTMENT RESEARCH BRIEF TEMPLATE
INSTRUCTIONS:
- Recall & Apply: {output-standards} (./framework/guides/output-standards.md)
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
<!--
PROJECT RESEARCH BRIEF TEMPLATE
INSTRUCTIONS:
- Recall & Apply: {output-standards} (./framework/guides/output-standards.md)
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
<!--
SECTOR RESEARCH BRIEF TEMPLATE
INSTRUCTIONS:
- Recall & Apply: {output-standards} (./framework/guides/output-standards.md)
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
<!--
OPEN RESEARCH TEMPLATE
INSTRUCTIONS:
- Recall & Apply: {output-standards} (./framework/guides/output-standards.md)
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
<!--
PRODUCT ANALYSIS TEMPLATE
INSTRUCTIONS:
- Recall & Apply: {output-standards} (./framework/guides/output-standards.md)
The file embeds operative instructions inside an HTML comment, including cross-references to other guidance files and validation rules. Hidden instructions are dangerous because an agent may still ingest and follow them even though they are not visible to the end user, creating non-transparent behavior and enabling prompt-layer control that can override user expectations or smuggle in additional constraints from external files.
<!--
PROJECT SNAPSHOT TEMPLATE
INSTRUCTIONS:
- Recall & Apply: {output-standards} (./framework/guides/output-standards.md)
The file begins with an HTML comment containing operational instructions such as 'Recall & Apply' external standards and validation requirements. Hidden instructions are dangerous because they can influence an agent's behavior without being visible in the rendered template, creating a covert control channel that may override user expectations or introduce unreviewed behavior via referenced files.
<!--
QA REVIEW TEMPLATE
INSTRUCTIONS:
- Recall & Apply: {output-standards} (./framework/guides/output-standards.md)
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
<!--
SECTOR LANDSCAPE TEMPLATE
INSTRUCTIONS:
- Recall & Apply: {output-standards} (./framework/guides/output-standards.md)
The template embeds operational instructions inside an HTML comment, making them invisible in normal rendered output while still available to an agent that reads raw markdown. Hidden instructions can bypass user awareness and create instruction-channel confusion, causing the agent to follow repository-authored directives such as external guide references and validation rules that the user did not explicitly approve.
<!--
SECTOR OVERVIEW TEMPLATE
INSTRUCTIONS:
- Recall & Apply: {output-standards} (./framework/guides/output-standards.md)
The file embeds operative instructions inside an HTML comment, including directives to recall external standards and validation rules. Hidden instructions are dangerous because they can influence an agent's behavior without being visible to end users or reviewers, creating a covert control channel that can override user expectations or introduce unreviewed dependencies from referenced files.
<!--
SOCIAL SENTIMENT TEMPLATE
INSTRUCTIONS:
- Recall & Apply: {output-standards} (./framework/guides/output-standards.md)
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
<!--
TEAM & INVESTOR ANALYSIS TEMPLATE
INSTRUCTIONS:
- Recall & Apply: {output-standards} (./framework/guides/output-standards.md)
The template embeds operational instructions inside an HTML comment, making them invisible to typical users while still available to an AI that processes raw markdown. Hidden prompt instructions can silently influence model behavior, reduce transparency, and override user expectations by pulling in external guidance such as output standards and validation objectives.
<!--
TECHNOLOGY ANALYSIS TEMPLATE
INSTRUCTIONS:
- Recall & Apply: {output-standards} (./framework/guides/output-standards.md)
The template embeds operative instructions inside an HTML comment, making them hidden from normal rendered view while still available to an LLM processing the raw file. Hidden prompt instructions can create non-transparent behavior, cause the agent to follow unreviewed external guidance files, and weaken auditability of what is influencing model output.
<!--
TOKENOMICS ANALYSIS TEMPLATE
INSTRUCTIONS:
- Recall & Apply: {output-standards} (./framework/guides/output-standards.md)
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
<!--
TRACTION METRICS TEMPLATE
INSTRUCTIONS:
- Recall & Apply: {output-standards} (./framework/guides/output-standards.md)
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
<!--
TREND ANALYSIS TEMPLATE
INSTRUCTIONS:
- Recall & Apply: {output-standards} (./framework/guides/output-standards.md)
The README presents a very broad natural-language activation path ('Simply describe what you want') that encourages implicit skill activation from ordinary user phrasing. In agent ecosystems where tools infer and load skills from conversational intent, this can cause unintended execution of the framework, including persona adoption and downstream file operations, without a clear explicit opt-in boundary.
The README normalizes automatic workspace creation and output auto-saving but does not prominently warn that using the skill may write files to the local filesystem. In AI CLI environments with file access, silent or assumed writes can surprise users, overwrite expectations about read-only analysis, and expand the blast radius of accidental activation or prompt-triggered execution.
No suspicious patterns detected.