Skip to content
TrustedSkillsbeta
Back to all skills

Token Integration Analyzer

Checked
trailofbits·vlatest·security·CC-BY-SA-4.0

Analyzes smart contract token interactions to identify potential vulnerabilities like reentrancy and unexpected state changes.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add trailofbits/skills --skill token-integration-analyzer -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

trailofbits

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned trailofbits/skills at 82fe822625.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
82fe822625
Manifest
plugins/building-secure-contracts/skills/token-integration-analyzer/SKILL.md
Scanned
4 files, 1,047 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The token-integration-analyzer skill helps identify and analyze how different components or systems interact within a software architecture, focusing on token-based integrations. It can detect potential security vulnerabilities, misconfigurations, or inefficiencies in how tokens are used across services.

When to use it

  • When auditing microservices for secure token handling
  • Before deploying new authentication flows involving API keys or JWTs
  • During code reviews to ensure consistent and safe integration practices

Key capabilities

  • Detects insecure token storage and transmission
  • Analyzes token lifecycle management across systems
  • Identifies misconfigured access controls in integrated services

Example prompts

  • "Analyze the token usage in this microservices architecture for security issues."
  • "Check how tokens are passed between these API endpoints."
  • "Find potential vulnerabilities in the integration of authentication tokens."

Tips & gotchas

  • Ensure your system has clear documentation on token types and their intended use.
  • This skill may require access to code repositories or API definitions for accurate analysis.