Skip to content
TrustedSkillsbeta
Back to all skills

Tokenx Auth

Checked
navikt·vlatest·security·MIT

Authenticates requests against Navikt's TokenX system, verifying user identity and authorization for secure data access.

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 navikt/copilot --skill tokenx-auth -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

navikt

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 navikt/copilot at 0bee4f53f4.

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

Commit
0bee4f53f4
Manifest
skills/tokenx-auth/SKILL.md
Scanned
2 files, 376 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 tokenx-auth skill provides authentication and authorization capabilities. It allows AI agents to securely access resources requiring authentication, handling token management and user verification. This enhances security by ensuring only authorized users or services can interact with protected systems.

When to use it

  • Secure API Access: Granting an agent access to a third-party API that requires OAuth 2.0 credentials.
  • Internal Service Authentication: Allowing an agent to securely call internal microservices requiring authentication.
  • User Impersonation (with permission): Enabling an agent to perform actions on behalf of a user after proper authorization and consent.
  • Automated Workflows: Integrating authentication into automated processes, such as data extraction or report generation.

Key capabilities

  • OAuth 2.0 support
  • Token management
  • User verification

Example prompts

  • "Authenticate to the Acme API using client ID xyz and secret abc."
  • "Get a new access token for user [email protected]."
  • "Refresh the existing access token."

Tips & gotchas

The skill requires proper configuration of authentication credentials (client IDs, secrets, etc.) before use. Ensure you have the necessary permissions to perform actions on behalf of users when impersonating them.