agentleFS
Sign inStart free
TidalPaladinTidalPaladin/skills/token-file-auth/SKILL.md

token-file-auth

Skill1 starsChanged 24 days agoApache-2.0View on GitHub

Load a named API token from a local secret file without exposing its value.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    Use ~/.codex/env/<secret_name>, or TOKEN_FILE_AUTH_BASE_DIR when explicitly set.

    line 9
  2. Very specific:

    Avoid ~/.codex/.env, which can interfere with Codex startup.

    line 10
  3. Very specific:

    Use scripts/token_file_auth.sh for validation or source that helper to call load_token_from_file.

    line 12
  4. Distinctive:

    Keep token values in memory.

    line 17
  5. Very specific:

    If the file is absent, report its expected location.

    line 20

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Token File Auth

Accept $token-file-auth <secret_name>. Use ~/.codex/env/<secret_name>, or TOKEN_FILE_AUTH_BASE_DIR when explicitly set. Avoid ~/.codex/.env, which can interfere with Codex startup.

Use scripts/token_file_auth.sh for validation or source that helper to call load_token_from_file. Never source the secret file itself.

The helper validates the name against [A-Za-z0-9._-]+ and rejects path traversal. Require a readable, non-empty regular file that is not a symlink. Keep token values in memory. Do not print them or put them in command arguments. Unset token variables when custom requests finish.

If the file is absent, report its expected location. Have the user supply the secret through a secure mechanism. Use directory mode 700 and file mode 600. Return only sanitized diagnostics.

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