agentleFS
Sign inStart free
daniilganievdaniilganiev/telegram-dev/skills/audit-project/SKILL.md

audit-project

Skill0 starsChanged 36 days agoMITView on GitHub

Pre-release audit of a Telegram bot or Mini App, with or without TON — secrets scan, typecheck, lint and tests, Telegram-specific checks, then the security reviewer agents. Run before a release or any mainnet discussion.

  • Reads credentials

8 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Secrets scan: Search tracked files (not git-ignored ones such as .env) for bot tokens (\d{8,10}:[A-Za-z0-9_-]{35}), seed phrases, 64-hex …

    line 11
  2. Very specific:

    Build and tests: Run the project's typecheck, lint and tests (package.json scripts, or pyproject.toml tooling such as ruff, mypy and …

    line 15

“Common” is measured: kept by at least 6 in 10 of the 6 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

Audit project

Work through these in order and report each result. Don't fix anything silently; list findings and ask before changing code.

  1. Secrets scan. Search tracked files (not git-ignored ones such as .env) for bot tokens (\d{8,10}:[A-Za-z0-9_-]{35}), seed phrases, 64-hex private keys, API keys, and for .env or wallets.toml tracked by git (git ls-files). Check the built front-end bundle too. Report file and line; never print the secret value.
  2. Build and tests. Run the project's typecheck, lint and tests (package.json scripts, or pyproject.toml tooling such as ruff, mypy and pytest).
  3. Telegram checks. initData validated on the server with an auth_date limit; webhook checks its secret token; allowed_updates matches the handlers; handlers idempotent; 429 and 403 handled in broadcasts.
  4. Payments (if present). Delegate to the telegram-security-reviewer agent.
  5. Contracts (if Acton.toml exists). acton build, acton check, acton test --coverage (WSL on Windows). Then delegate to the ton-security-reviewer agent.
  6. Summary. One table: area, status (passed, failed or skipped), top finding. Then go through the telegram-launch checklist for what automation can't check. End with a verdict: ready for release, ready for a human audit, or not ready. Never call anything "safe for mainnet".

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.

Check your setup, free