Token Red Flag Check — Free Quick Screen

    1

    A focused token screen for identity, visible permission warnings, and available sell/pool evidence. Returns linked findings and explicit unknowns, with no wallet connection.

    Free

    1 installSecurity scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+22 more

    Token Red Flag Check — Free Quick Screen

    Example session with this skill installed

    Use the included recorded observations from 2026-10-11T13:33:05+00:00 for USDC on Ethereum mainnet at 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48. Produce a quick screen of target identity, visible permission warnings, and available ordinary-holder sell/pool evidence. Separate confirmed observations, interpretations, and unknowns. Keep it read-only, make no fresh network query, and state the limits of the historical evidence.

    • Read your context and instructions
    • Compiled the token red flag

    This is a real recorded-data example, adapted from a read-only observation made on 2026-10-11. No fresh network query was made while preparing this free example. The screen shows how to preserve gaps; it is not a completed audit or a recommendation to use USDC.

    Target: Ethereum mainnet, chain ID 1; 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48.
    Asset context: issuer-controlled stablecoin.
    As of: 2026-10-11T13:33:05+00:00; direct read block 26169530 (0x18f50ba). The provider's latest block was used; block hash and finality were not verified.
    Scope: issuer-published address, selected saved contract/scanner/pair observations. Active implementation and all roles, ordinary-holder sell evidence, LP control and reserves were not resolved.
    Outcome: MORE EVIDENCE NEEDED.
    Reason: the target and several observations are established, but material permission and exit/pool questions remain open. The saved scanner's favorable field does not close them.

    Quick evidence table

    CheckStatusObservationSource / UTC / blockMeaning and limit
    Published identityCONFIRMEDCircle's mainnet address table listed this contract for Ethereum.Circle issuer address table; retrieved 2026-10-11 UTC; no chain block for the document.Confirms the issuer-published address, not safety or reserve backing.
    Owner getterCONFIRMEDowner() returned 0xfcb19e6a322b27c06842a71e8c725399f049ae3a.Included buyer ZIP: examples/evidence/usdc-observations.json, preserved RPC request/response; 2026-10-11T13:33:05+00:00; block 26169530.A getter observation, not the identity of every controller.
    Standard proxy slotsCONFIRMEDThe sampled implementation, admin and beacon slot words were zero.Included direct RPC observations; same UTC/block.Does not rule out legacy/custom proxies or upgrades through another mechanism.
    Scanner fieldsCONFIRMEDGoPlus reported is_proxy="1" and is_honeypot="0"; owner and mintability fields were absent.Included explicitly projected scanner fields; 2026-10-11T13:33:04+00:00; scanner block unavailable.Confirms what the response said. Proxy mechanism, live role state and ordinary-holder exit still need examination.
    Indexed poolsCONFIRMEDThe saved DEXscreener response contained 30 indexed pairs.Included derived count; 2026-10-11T13:33:03+00:00; indexer block unavailable.A dataset count, not all venues, executable depth, LP ownership or a lock.
    Material permission / exit / pool questionsUNKNOWNThe complete active control path, ordinary-holder sell conditions and pool position control were not inspected.Declared scope of the recorded observation; evidence does not contain those completed checks.Do not conclude "no privileged controls," "honeypot-free" or "liquidity secured."

    There is an unresolved scope difference: a scanner reported a proxy while the standard sampled slots were empty. This is a next-check requirement, not proof that the token is immutable or that the scanner's interpretation is correct. Issuer-controlled stablecoin powers, if verified, require context rather than an automatic accusation of fraud.

    Next evidence

    1. Identify the actual deployed implementation/proxy mechanism and current material roles; distinguish code capability from active authority.
    2. Examine relevant ordinary-holder sale evidence or an already authorized non-broadcast simulation with route, amount and block.
    3. Identify the relevant pool/position ownership, withdrawal assumptions and usable depth for the intended size.

    These checks can be researched without buying a test amount or connecting a wallet. A full permission map, holder interpretation, unlocks and public-claim investigation are beyond this recorded first pass.

    Actions taken for this example: read and summarized previously saved public evidence locally; no fresh query, wallet connection, signing, approvals, payments or trades. The original observation consisted of read-only public document/API/RPC queries.
    Limits: dated, partial evidence; no full audit, safety guarantee, reserve certification or price forecast. New observations can differ.

    Optional deeper workflow: for implementation/role mapping, LP control, holder classification and unlock review, look for the creator's

    Crypto Token Due Diligence — Evidence-Based Risk Check companion on Agensi; this quick screen works without it.

    Evidence provenance

    evidence/usdc-observations.json is a

    derived extract, not the full original snapshot: direct RPC request/response sections are preserved; scanner fields are explicitly projected with field presence recorded; pool count is derived. Third-party token metadata URLs were omitted because they are not tool/service dependencies or required evidence for this first pass. The original snapshot SHA-256 is recorded for provenance. No source observations were refreshed or converted into broader security findings.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Start token research with three practical questions: is this the right address, what visible controls deserve attention, and what evidence exists for an ordinary holder's exit?

    Token Red Flag Check guides your agent through a focused first screen on Ethereum, BSC, Base, or Solana mainnet. Give it the chain and full contract or mint address. It checks public evidence, explains what the evidence supports, and lists what remains unresolved.

    You receive:

    • Target identity, with the address matched against a credible source where one is available.
    • Visible warnings about minting, freezing, transfer restrictions, or upgrade control, within the accessible evidence.
    • Available sell and pool observations, with their conditions and limitations kept visible.
    • A compact evidence table: CONFIRMED, INFERRED, or UNKNOWN, with source links and observation times.
    • A clear result: a supported warning, a need for more evidence, or no obvious red flag within the limited checks.

    The free workflow works on its own. It does not require the paid skill, Python, an API key, a wallet, or a project account. It delivers its report in the conversation; it does not require local file writing.

    An owner renunciation, scanner badge, trade history, or familiar ticker is never treated as a safety certificate. Incomplete controls or sell evidence remain unresolved. Disclosed administrative controls are explained in context rather than automatically labelled a scam.

    Your agent must support the SKILL.md format and have browser or search access. Source coverage varies: blocked pages, stale data, and missing evidence can prevent a conclusion. Free refers to the skill price; your agent provider may charge for model or tool usage.

    This is a point-in-time research screen, not a contract audit, price forecast, investment recommendation, or guarantee of safety. It does not connect wallets, sign transactions, or trade. No fixed completion time is promised.

    For deeper review of roles, proxy control, Token-2022 extensions, holder concentration, LP control, unlocks, and promotional claims, look for Crypto Token Due Diligence — Evidence-Based Risk Check on Agensi when its listing is live. The free screen remains usable independently.

    How to use

    Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    1 install

    Downloaded by developers to date

    Free forever

    No account required to browse

    Trust & safety

    Security scanned

    Verified clean 8 days ago

    • Free to download with an account

    Requires

    Python

    Listed8 days ago

    What's inside

    Frequently Asked Questions