Credentials. The terminal and Discord audit flow connects to your configured setup, so keep any wallet or API keys out of shared logs and screenshots.
Who it is forA trader who has found a token on Robinhood Chain and wants a security check before deciding whether to buy.
The problemChecking a token's security across several sources by hand is slow, and a single missed red flag can cost real money.
The outcomeA live token audit from the Terminal TUI or the #audit-on-demand channel that shows the security results before any trade decision.
What you need first
- Node.js and npm installed
- Git installed to clone the repository
- API keys and chat credentials for the onboarding wizard (for example Discord or Telegram setup)
- Familiarity with a terminal on Windows, Linux, or macOS
Steps
- Run
npm installandnpm run buildfrom inside the Noraz Agent folder. - Run
noraz terminal(ornpm run terminal) to open the standalone Terminal TUI. - Choose the live token audit option and enter the token contract address you want to check.
- If you prefer Discord, post the token address in the
#audit-on-demandchannel and wait for the audit reply. (inferred, check the README) - Review the GMGN and GoPlus security results before deciding whether to act.
Prompt for your agent
Using the noraz-agent repo, run a live token audit on <token-address> through the Terminal TUI or the #audit-on-demand channel. Expected output: an audit summary that includes the GMGN and GoPlus security results. Verify that the audit result is shown before any buy or swap action is taken.
Caveat. An audit is only one input; the README describes the tool as experimental research with no guarantee of results and says to do your own research.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page