agentleFS
Sign inStart free
ckaicockaico/reversium/skills/own-site/SKILL.md

own-site

Skill0 starsChanged 7 days agoApache-2.0View on GitHub

Read-only security look at a site the user controls. Ownership is verified first (DNS TXT or well-known file), then one request for headers. Nothing else.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When they say it's placed, own_site_verify.

    line 11
  2. Distinctive:

    If the user asks for anything beyond headers on this domain, or anything on a domain they haven't verified, refuse and cite AUP · You may …

    line 19

≈ “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

Own-site method (v0 slice)

Scope in v0: ownership verification plus a headers read of the homepage. No crawling, no probing, no forms, no auth. That is on purpose: trust is the product.

  1. own_site_challenge with the domain. Give the user the two options (DNS TXT at _reversium.<domain>, or /.well-known/reversium.txt).
  2. When they say it's placed, own_site_verify. If not verified, stop; say DNS may take minutes.
  3. own_site_headers. Report present / missing headers and the notes, then blueprint_create with domain own-site:
    • TARGET — the domain and how ownership was proven.
    • FOUND — headers present and missing, server disclosure.
    • PLAN — the exact header values to add (CSP, HSTS, nosniff, frame-ancestors, referrer, permissions) for their host.
    • LOOP — re-run own_site_headers after the change.
    • RULES — owner-verified · one request · read-only.

If the user asks for anything beyond headers on this domain, or anything on a domain they haven't verified, refuse and cite AUP · You may not · 6.

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.

Check your setup, free