token-safety-check skillA
token-safety-check is agent-read markdown (skill) from nirholas/three.ws: Run on-chain safety diligence on a Solana token before anyone buys it - mint and freeze authority, liquidity lock or burn, holder concentration, sell simulation - and give a plain verdict with the evidence. Use when the user asks "is this token safe", "is it a rug", "check this mint", "should I ape", or pastes a mint address and asks about buying..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Token safety check You are doing pre-buy diligence on one Solana token. Your job is to find the facts that decide whether a holder can be robbed, report them plainly, and never let enthusiasm stand in for evidence. A clean result is not a recommendation to buy; it only means the token cannot be drained in the obvious ways. ## Inputs - The mint address (base58, 32 to 44 characters). If the user gave a name or ticker instead of an address, ask for the address. Names are not unique and copycat tokens reuse them on purpose. - The size they are thinking about, in SOL, if they mentioned one. It sets the sell simulation. ## The five checks, in order 1. **Mint authority.** If it is not revoked, the issuer can print unlimited supply and dilute every holder to zero. Live mint authority is a hard fail for a trading token. 2. **Freeze authority.** If it is not revoked, the issuer can freeze any holder's account so they can never sell. Hard fail. 3. **Token-2022 extensions.** A permanent delegate, a transfer hook, a transfer fee, a default-frozen account state or a pause switch each keep power in the issuer's hands. Name every one you find and say what it lets the issuer do. …
Read the whole file at its exact version.
How to install
mdr add nirholas/three.ws/token-safety-check@git:20260922.9a96a70mdr add nirholas/three.ws/token-safety-check@sha256:48a500dc388ff569Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_5lpyatv5jm3omr24)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5265 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
nirholas/three.ws · 211 stars · license Apache-2.0 · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_5lpyatv5jm3omr24 GET https://markdownregistry.com/api/v1/resolve?ref=nirholas/three.ws/token-safety-check GET https://markdownregistry.com/api/v1/blob/48a500dc388ff569e49c57bc78359fe1c42df291a5c992a7b4cb5bed305e6409
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.