Skip to content
TrustedSkillsbeta
Back to all skills

Mapbox Token Security

Official
mapbox·vlatest·security·MIT

Safeguards Mapbox access tokens, preventing unauthorized use and data exposure through secure storage and automated rotation.

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 mapbox/mapbox-agent-skills --skill mapbox-token-security -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

mapbox

Matched to the vendor's own GitHub organisation.

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 failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • No undeclared network calls: failed

    Contacts 1 host that is neither well-known infrastructure nor declared in the skill's frontmatter: staging.myapp.com.

    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.

    Hosts contacted

    127.0.0.1localstaging.myapp.comundeclared

    What it found

    • skills/mapbox-token-security/evals/evals.json:20contacts staging.myapp.com
      "expected_output": "Should explain that '*' means the token works on any website, making it trivially abusable if leaked. Should provide correct patterns: prod…

  • 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 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 mapbox/mapbox-agent-skills at f71cd72b8d.

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

Commit
f71cd72b8d
Manifest
skills/mapbox-token-security/SKILL.md
Scanned
6 files, 755 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

This skill enables AI agents to securely manage Mapbox access tokens, ensuring that sensitive authentication keys are handled with strict security protocols. It prevents token exposure in logs or public repositories by enforcing secure storage and retrieval practices within the agent's workflow.

When to use it

  • Integrating Mapbox maps into applications where the AI agent must generate or refresh map tiles dynamically.
  • Deploying agents that require long-term access to geospatial data without risking credential leakage.
  • Automating workflows that need to validate token expiration and rotate keys automatically.
  • Building production-grade mapping features where security compliance is a mandatory requirement.

Key capabilities

  • Securely store and retrieve Mapbox access tokens from encrypted environments.
  • Enforce token rotation policies to minimize the window of exposure if a key is compromised.
  • Validate token permissions before executing map-related operations.
  • Prevent accidental logging or transmission of tokens in unsecured channels.

Example prompts

  • "Generate a secure Mapbox access token and store it using the agent's vault system."
  • "Check if the current Mapbox token has expired and rotate it if necessary."
  • "Validate that the stored token has permission to render high-resolution map tiles before proceeding."

Tips & gotchas

Ensure your AI agent environment supports encrypted storage mechanisms, as this skill relies on secure vaults rather than plain-text variables. Always verify that the agent's execution context does not inadvertently expose tokens through debug logs or network requests.