AdBraze Plans plans.adbraze.dev

Drop a plan.
Keep the URL forever.

plans.adbraze.dev stores finished plans, reports and technical write-ups as single self-contained HTML documents. No account, no token, no edit history. One publish flow in, one immutable URL out.

Acceptsself-contained .html
Max size5 MiB
Writesonce — no edit, no delete
Indexingnoindex, nofollow

Publish a document

Drag a file onto this panel, or choose one. Nothing is sent until you pick a file.

self-contained HTML/5 MiB limit/anonymous/write-once

02

Publish from an agent

SKILL.md · helper · template

The same endpoint works from a terminal or from an agent. Install publish-html-plan and the agent can turn source material into a dark AdBraze report, publish it, verify it and hand back the URL without leaving the session.

The package includes a concise skill, a standard-library Python publisher and the full Claude-designed report template. There is no account or API token to configure.

publish-html-plan/SKILL.md Markdown 
Loading the current skill definition…
03

Anonymous, write-once publishing

Five rules, no exceptions
  1. 01
    No account

    Publishing is a single unauthenticated request. There is no sign-up, no API key and no session cookie. Privacy-preserving network hashes are retained only to enforce abuse limits.

  2. 02
    Write once

    A published document is frozen. There is no PATCH and no re-upload to the same address. Correcting a plan means publishing a new one; the old URL keeps serving exactly the bytes it served on day one.

  3. 03
    Readable canonical URLs

    Each plan uses the requested readable slug at /launcher-refactor. If that slug already belongs to different bytes, the service adds a deterministic content suffix instead of overwriting the original.

  4. 04
    Not indexed

    Every plan page and this homepage ship noindex,nofollow,noarchive,nosnippet,noimageindex as both a meta tag and an X-Robots-Tag header. Links are shared deliberately, not discovered.

  5. 05
    No delete endpoint

    Nothing in the public API edits or removes a plan. Operators keep a separate takedown path for abuse, accidental secrets and legal requests.

BEFORE YOU PUBLISH — treat every upload as permanent and world-readable to anyone holding the link. Do not publish credentials, tokens, customer data, or anything you would need to retract.