agentleFS
zyphr-labszyphr-labs/bounty-harness/.claude/skills/meme-coin-audit/SKILL.md

meme-coin-audit

Skill1 starsChanged 3 months agoMITView on GitHub

Meme coin and token security audit — rug pull detection (honeypot, hidden mint, fee manipulation, LP lock bypass), Solana SPL token analysis (freeze authority, mint authority, metadata mutability), Token-2022 extension risks (transfer hooks, permanent delegate), DEX liquidity pool attacks (sandwich amplification, LP drain, bonding curve exploits), pump.fun/Raydium/Jupiter integration risks, token_scanner.py automation, and real exploit examples from 2024-2025. Use for any token audit, rug pull assessment, meme coin security review, or pre-investment due diligence.

8 other projects use a version of this, 8 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use agentic-app-audit, bug-chaining and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • shuvonsecSkill

    agentic-app-audit

    Black-box security audit of a DEPLOYED AI agent (not the MCP server behind it) — tool-call hijacking, cross-session memory poisoning, confused-deputy via connected tools, agent-to-agent IDOR, excessive agency / unconfirmed destructive actions, and privilege compromise where the agent holds broader perms than the user. Use when the target is a live assistant/agent product with tool access (bookings, email, payments, file/RAG, browsing) rather than a raw LLM chat box or an MCP server you can read.

    Also in 3 projects that use this

  • shuvonsecSkill

    bug-chaining

    Standalone bug chaining skill — synthesized from omni-killchain, omni-references/chaining-impact, triage-validation, apex-hunter, web2-vuln-classes, bug-bounty, and bb-methodology. Covers the complete chaining mindset: 10-question filter, 15 proven chain patterns (A–O) with payout data, escalation ladders per vuln class, conditional-chain table (when a standalone bug needs a gadget), impact-writing rules, CVSS chain multipliers, and 30-minute chain-or-move decision clock. Use when you have a low/medium finding and want to know how to chain it to Critical, or when strategizing what to hunt for maximum payout. Authorized testing only — bug bounty in-scope, pentest engagement, or CTF.

    Also in 3 projects that use this

  • Mikacr1138Skill

    web2-vuln-classes

    Complete reference for 18 web2 bug classes with root causes, detection patterns, bypass tables, exploit techniques, and real paid examples. Covers IDOR, auth bypass, XSS, SSRF (11 IP bypass techniques), SQLi, business logic, race conditions, OAuth/OIDC, file upload (10 bypass techniques), GraphQL, LLM/AI (ASI01-ASI10 agentic framework), API misconfig, ATO taxonomy, SSTI, subdomain takeover, cloud/infra misconfigs, HTTP smuggling, cache poisoning. Use when hunting a specific vuln class or studying what makes bugs pay.

    Also in 4 projects that use this

  • +7 more from shuvonsec

The file

We split this skill into the rules it gives an agent

1 rule. 1 is common, 0 are distinctive, and 0 are very specific to this project.

  • 1

    Common

    Most of the 8 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Common:

    No social presence / anonymous deployer with no history

    line 38

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “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

MEME COIN & TOKEN SECURITY AUDIT

Overview

Fast-kill rug pull detection and deep token security analysis for EVM and Solana meme coins. The one rule: "Check ALL authorities and owner functions. The retained authority IS the rug vector." Every rug pull requires a privileged operation: mint, blacklist, fee change, LP removal, or authority abuse. Find the privilege, find the bug.

Safety: static source analysis is passive. On-chain verification (Solscan/Etherscan authority checks, DEX pool inspection, PoC execution) is intrusive — require explicit authorization.

Quick Reference

Hard kills (skip immediately)

  • Contract not verified on Etherscan/Solscan → cannot audit source
  • Deployer wallet has a history of rug pulls
  • Token age < 1 hour AND no known team
  • Mint authority retained (Solana) AND no cap → infinite mint = certain rug
  • Freeze authority retained (Solana) on a meme coin → honeypot confirmed
  • Transfer hook present (Token-2022) with mutable hook program → honeypot vector
  • Permanent delegate extension (Token-2022) → can steal all holder tokens

Soft kills (proceed with extreme caution)

  • Top holder > 20% of supply (excluding DEX pools)
  • LP not burned or locked in a verified contract
  • Contract is upgradeable / proxy with retained admin
  • Less than $5K liquidity in the pool
  • No social presence / anonymous deployer with no history

Bug classes

#ClassShare of rugs
1Hidden mint / unlimited supply35%
2Honeypot / transfer restriction25%
3Fee manipulation20%
4Liquidity pool drain—
5Bonding curve manipulation—
6Authority retention (Solana)—
7Fake renounce / hidden ownership—
8Sandwich amplification by design—

Workflow Selection

SituationWorkflow
Static token source review (EVM or Solana)token-scan
Retained-authority grep across sourcesscripts/authority_check.py
On-chain authority / LP / holder verificationmanual (intrusive — runbooks/onchain-checks.md)

Available Workflows

token-scan

Runs the token red-flag scanner (8 bug classes via regex) over Solidity or Rust/Anchor token sources. Passive — local files only, no API calls.

python3 .claude/skills/meme-coin-audit/scripts/token_scanner.py \
  "${CONTRACTS_DIR:?Set CONTRACTS_DIR}" --recursive > $OUTDIR/web3/token_scan.txt

Outputs: $OUTDIR/web3/token_scan.txt. Safety tier: passive.

Evidence Required

ArtifactFile
Token scanner report$OUTDIR/web3/token_scan.txt
Authority grep output$OUTDIR/web3/authority_check.txt
On-chain state (intrusive): mint/freeze authority, LP lock, holder distevidence/<finding>/onchain.json

References

  • Scanner limitations: it does NOT check on-chain state, holder distribution, LP lock status, or deployer history — those are manual (intrusive) checks
  • Solana quick checks: runbooks/onchain-checks.md
  • Token exploits Foundry template: runbooks/token-exploit-poc.md
  • Pre-dive kills: runbooks/kill-signals.md
  • Scanner usage: runbooks/token-scan.md
  • Redaction policy: evidence stays local-only under $OUTDIR; redact wallet addresses, RPC endpoints, and any private keys before committing.

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.