Agent skill
HTML Injection Testing
This skill should be used when the user asks to "test for HTML injection", "inject HTML into web pages", "perform HTML injection attacks", "deface web applications", or "test content injection vulnerabilities". It provides comprehensive HTML injection attack techniques and testing methodologies.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/html-injection-testing-dokhacgiakhoa-antigravity-ide
Metadata
Additional technical details for this skill
- author
- zebbern
- version
- 4.1.0-fractal
SKILL.md
HTML Injection Testing
Purpose
Identify and exploit HTML injection vulnerabilities that allow attackers to inject malicious HTML content into web applications. This vulnerability enables attackers to modify page appearance, create phishing pages, and steal user credentials through injected forms.
Prerequisites
🧠 Knowledge Modules (Fractal Skills)
1. Required Tools
2. Required Knowledge
3. Phase 1: Understanding HTML Injection
4. Phase 2: Identifying Injection Points
5. Phase 3: Basic HTML Injection Testing
6. Phase 4: Types of HTML Injection
7. Phase 5: Phishing Attack Construction
8. Phase 6: Defacement Payloads
9. Phase 7: Advanced Injection Techniques
10. Phase 8: Bypass Techniques
11. Phase 9: Automated Testing
12. Phase 10: Prevention and Remediation
13. Common Test Payloads
14. Injection Contexts
15. Encoding Types
16. Attack Limitations
17. Testing Considerations
18. Severity Assessment
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?