Skip to contentLockpick
How it worksPricingDocs

Read

  • BlogPlain answers to common security questions
  • GuidesStep by step fixes for common setups
  • Security checksEvery check we run, explained

Learn

  • Learn with PickTwo-minute lessons on how sites get attacked
  • Lockpick for ClaudeCheck sites from Claude and other assistants
  • GlossaryThe words we use, in plain words

Company

  • ChangelogWhat changed, newest first
  • StatusWhether scans are running right now
  • Security and trustHow we check and what we never do
Sign inCheck it
Blog

Security checks your coding agent can run on your live site

By Mark KashefPublished October 8, 2026

A coding agent connected to Lockpick can check what your live site shows to strangers, read the findings and fix them in your code. It works through permissions you choose. Whatever permission you give, an assistant can only ever do what you can do yourself in that workspace.

What can it check?

CheckWhat it looks atNeeds
Quick checkA homepage and public DNS records, with no site addedThe Pulse permission
PulseAn outside look at a site in your workspaceYour confirmation that you may test it
Deep scanA careful walk through a site you proved you ownYour approval in Lockpick each time
Re-read this recordOne public DNS record again, after a fixThe Pulse permission

Every tool only reads, and the checks are the same limited, read-only checks as the web app. Reading existing results does not consume another scan.

Curious what your site shows from outside? The quick check is free and needs no account.

Check it

What can it read?

Your sites, scans, findings and each finding's repair brief, so it can explain a report in plain words or fix the code. The server never shows an assistant raw scanner output, internal prompts or how a check is run. It gets the same findings, redacted evidence and fixes you see.

How do you teach it when to use them?

Add the skills pack. The Lockpick skills teach your assistant which check to run, how to read a report and how to make each kind of fix. Then ask in your own words, like "check atlas.example and fix the most important thing on a new branch". Atlas at atlas.example is our example app; use your own address.

What it cannot do

It cannot start a Deep scan without you, sign in to your site, or change anything on it. An agent fixing your code does not prove the live site is fixed either. Ask it to check again after you deploy.

Questions people ask

Does reading a report cost a scan?

No. Reading existing results is free. Starting a Pulse or a Deep scan uses that scan from your allowance.

Can an agent see how Lockpick checks work inside?

No. It sees the same findings, redacted evidence and fixes you see, never raw scanner output or internal prompts.

See what your site shows from outside

A quick check reads your homepage the way a visitor would and gives you a score. No account needed.

Check your site

Related pages

  • Run a Lockpick scan from Claude Code or Cursor
  • Fix it with your AI, prompts for Lovable, Bolt, Replit, v0, Cursor and Claude Code
  • How Lockpick checks a site, and what we never do

Sources

  1. Hosted server and sign-in Lockpick docs, read on October 6, 2026
  2. Permissions Lockpick docs, read on October 6, 2026
  3. Skills pack Lockpick docs, read on October 6, 2026

About the author

Mark Kashef, Founder of Lockpick

I'm Mark, and I build Lockpick. I write these pages, and each one is checked against its sources before it goes live. The Updated date changes only when the page itself does.

Lockpick
PricingMethodologyDocsBlogGuidesSecurity checksLearn with PickSecurity and trustLockpick for ClaudeChangelogStatusFacts for AI assistants

Lockpick is a security scanner for vibe-coded apps. It checks what your live site exposes and what a GitHub repo or AI skill would do before you install it, then gives you a fix prompt for Lovable, Bolt, Replit, Cursor or Claude Code.

Lockpick assesses public pages you are authorized to test, and public GitHub code it never runs.

© 2026 LockpickTermsPrivacyContactSign in