agentleFS
zen-mcpzen-mcp/browser/.agents/skills/safe-login/SKILL.md

safe-login

Skill2 starsChanged 7 months agoApache-2.0View on GitHub

Authenticate through a standard email and password login form while protecting credentials. Use when a browser task requires a logged-in session and the site does not provide an API.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill for ordinary email/password forms.

    line 15
  2. Very specific:

    Use get_page_snapshot to identify email/username, password, remember-me, and submit controls.

    line 29
  3. Distinctive:

    If a TOTP field appears, ask the user for the current code unless one was already provided.

    line 34
  4. Very specific:

    Use take_screenshot after login only if evidence is needed and it will not expose private account data.

    line 37
  5. Distinctive:

    Never log or return passwords, TOTP codes, cookies, or auth headers.

    line 48
  6. Distinctive:

    Never persist credentials in artifacts.

    line 49
  7. Distinctive:

    Never attempt to bypass CAPTCHA, SSO, passkeys, or account recovery controls.

    line 50

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Safe Login

When To Use

Use this skill for ordinary email/password forms. Do not use it for SSO, OAuth, passkeys, CAPTCHA solving, or flows that require bypassing security controls.

Inputs

  • login_url
  • email
  • password
  • success_selector or visible text that confirms login succeeded.
  • totp_code if the user provides a one-time code during the session.

Procedure

  1. navigate(login_url) and wait for the login form.
  2. Use get_page_snapshot to identify email/username, password, remember-me, and submit controls.
  3. Type credentials with type_text. Do not repeat credential values in any response or log.
  4. Submit with click or press_key("Enter").
  5. If a TOTP field appears, ask the user for the current code unless one was already provided.
  6. wait_for the success selector or success text.
  7. Use take_screenshot after login only if evidence is needed and it will not expose private account data.

Failure Modes

  • CAPTCHA or bot challenge: stop and report captcha.
  • Password field not found: capture a page snapshot and report no-form.
  • Invalid credentials: report the site error text without echoing secrets.

Never

  • Never log or return passwords, TOTP codes, cookies, or auth headers.
  • Never persist credentials in artifacts.
  • Never attempt to bypass CAPTCHA, SSO, passkeys, or account recovery controls.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.