Authentication surface — login endpoints, JWT/OAuth/SAML/SSO/API-key mechanism identification.
60
70%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Critical
Do not install without reviewing
Fix and improve this skill with Tessl
tessl review fix ./packages/decepticon/decepticon/skills/standard/recon/web-recon/auth-mapping/SKILL.mdSecurity
2 findings: 1 critical severity, 1 high severity. Installing this skill is not recommended: please review these findings carefully if you do intend to do so.
Detected high-risk code patterns in the skill content — including its prompts, tool definitions, and resources — such as data exfiltration, backdoors, remote code execution, credential theft, system compromise, supply chain attacks, and obfuscation techniques.
This document explicitly instructs how to enumerate authentication endpoints, capture credentials/session tokens, and hand off recon data for exploitation, indicating clear intent to enable unauthorized access and credential theft.
The skill handles credentials insecurely by requiring the agent to include secret values verbatim in its generated output. This exposes credentials in the agent’s context and conversation history, creating a risk of data exfiltration.
The prompt explicitly instructs the agent to "Record per mechanism: ... credentials used" and to produce "Required session state" (cookies, JWTs, API keys), which requires capturing and outputting secret values verbatim for recon→exploit handoff.
31e1c8e
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.