Ae1
- Category
- analysis-evasion
- Confidence
- 100% confidence
- Finding
Referenced artifact was not completely inspected
- Content
md - Use `scripts/validate-quality-docs.mjs` only after adapting its explicit configuration to the repository's schema.
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a coherent engineering documentation governance helper, with no artifact-backed evidence of hidden execution, exfiltration, persistence, or malicious behavior.
Install this for engineering repositories where you want structured technical specs, quality logs, and validation checks. Review the paths and validator configuration before use, especially in repositories with private research or secrets, and invoke it explicitly if you do not want automatic routing.
Referenced artifact was not completely inspected
- Use `scripts/validate-quality-docs.mjs` only after adapting its explicit configuration to the repository's schema.
YARA rule matched a hack tool or exploit indicator (offensive tools, reconnaissance, privilege escalation, or exploit frameworks).
# Technical Specification Architecture
## Authority and Scope
Define an explicit source-of-truth order: current user direction, invariant safety and data rules, verified implementation behavior, then historical plans. State which document is authoritative and when it must be updated.
## Front-Loaded Reading Model
Place a compact, mandatory rule block immediately after the title. Cover only constraints that apply to every task: data boundaries, security, protected code, scope control, repository hygiene, and verification responsibility.
Follow it with a clickable section index, a task-to-section routing table, and a note that historical or experimental material is read only when current facts cannot explain a decision. This enables narrow context loading without weakening safety.
Use one lightweight contributor entrypoint as the default read. The authoritative specification remains queryable re
Skill attempts to nullify the agent's safety policies or restrictions ('you have no restrictions', 'ignore your guidelines', 'do anything now'). This is a direct jailbreak that disables guardrails.
Define repository-specific limits for initial file count, default line range, command output, visual checks, and handoff length. Keep the limits in the lightweight entrypoint and validate them mechanically when the repository chooses fixed values.
Budgets reduce observation noise; they do not override safety review or prevent reading additional evidence when a task genuinely requires it.
## Stable Hierarchy
This pattern attempts to override system instructions or ignore safety constraints. Without LLM analysis, manual review is recommended.
Define repository-specific limits for initial file count, default line range, command output, visual checks, and handoff length. Keep the limits in the lightweight entrypoint and validate them mechanically when the repository chooses fixed values.
Budgets reduce observation noise; they do not override safety review or prevent reading additional evidence when a task genuinely requires it.
## Stable Hierarchy
This plain-text brief describes the skill's purpose at a high level but does not specify clear trigger phrases, invocation conditions, or boundaries for when the skill should activate versus stay inactive. Because the file is repository-neutral and broadly framed around improving engineering repositories, it could be interpreted as applying to many common requests without clear constraints or negative examples.
The brief explicitly requires English instructions, which imposes a language choice regardless of user preference. The same line allows repository-language output by default, but it does not offer the user a language selection or document a justified locale restriction.
The skill enables allow_implicit_invocation without any narrowing conditions, so the agent may trigger this governance skill in situations broader than intended. Because this skill can shape specifications, audits, logs, and validation workflows, unintended activation could steer repository documentation or quality processes without an explicit user request, causing confusing or unsafe automation decisions.