Avoid Api Keys

Organization

RedHatProductSecurity

avoid-api-keys

Avoid using API keys in production AI systems. Use when reviewing authentication mechanisms, designing production deployments, or auditing credential management in AI and agentic systems.

Overview

Publisher	RedHatProductSecurity
Repository	`prodsec-skills`
Skill name	`avoid-api-keys`
Stars	56
Forks	9
Bundled files	Instructions only
License	Apache-2.0
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by RedHatProductSecurity on GitHub. Read the source before you install it.

Installation

Install the Avoid Api Keys AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/RedHatProductSecurity/prodsec-skills/tree/main/module/skills/avoid-api-keys
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/RedHatProductSecurity/prodsec-skills/tree/main/module/skills/avoid-api-keys

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/RedHatProductSecurity/prodsec-skills.git /tmp/prodsec-skills
mkdir -p .claude/skills
cp -r /tmp/prodsec-skills/module/skills/avoid-api-keys .claude/skills/avoid-api-keys

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Avoid Api Keys in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Avoid Api Keys on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Avoid Api Keys is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Avoid API Keys in Production

Security Recommendation

API keys SHOULD NOT be used in production environments. Short-lived, scoped bearer tokens issued by an identity provider are preferable.

Why API Keys Are Problematic

Issue	Impact
Long-lived	Extended exposure window if compromised
Difficult to rotate	Rotation requires coordination across all consumers
Lack fine-grained scoping	Cannot limit permissions per request or context
No sender binding	Any holder of the key can use it from anywhere
No standard revocation	No instant revocation mechanism across distributed systems
Poor audit trail	API keys don't carry identity claims about the caller

Preferred Alternative

Use short-lived, scoped bearer tokens from an OIDC Identity Provider:

Property	API Key	IdP-Issued Token
Lifetime	Long-lived (months/years)	Short-lived (≤15 minutes)
Scoping	Broad or none	Per-request scopes
Revocation	Manual, slow	Instant via IdP + local blacklist
Identity	Opaque	Rich claims (sub, iss, aud, scope)
Rotation	Manual	Automatic via refresh tokens
Sender binding	None	DPoP or mTLS certificate binding

Migration Path

For systems currently using API keys:

Deploy an API gateway that accepts API keys from legacy clients
Gateway exchanges API keys for short-lived IdP tokens
Backend services only accept IdP tokens (never raw API keys)
Set deprecation timeline for API key consumers
Migrate consumers to OIDC flows
Retire API key support

Credential Storage

Credentials (API keys, tokens, secrets) MUST NEVER be stored in source code. This applies to all credentials including those used to connect to third-party model endpoints. Credentials must be managed and stored securely using:

Secret management systems (e.g., HashiCorp Vault, Kubernetes Secrets, AWS Secrets Manager)
Environment variables injected at runtime (not baked into images)
Encrypted configuration files with access controls

Implementation Checklist

Frequently asked questions

What does the Avoid Api Keys AI skill do?

Avoid using API keys in production AI systems. Use when reviewing authentication mechanisms, designing production deployments, or auditing credential management in AI and agentic systems.

Why use Avoid Api Keys on TypingMind?

Because you install it once and use it with any model. Avoid Api Keys is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Avoid Api Keys in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/RedHatProductSecurity/prodsec-skills/tree/main/module/skills/avoid-api-keys. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Avoid Api Keys?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Avoid Api Keys?

As many as you like. As long as a model supports skills, you can use Avoid Api Keys with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Avoid Api Keys AI skill free?

Yes. It is published on GitHub by RedHatProductSecurity under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Architecture Decision Records

affaan-m

CommunityPopular

コーディングセッション中にアーキテクチャ決定を構造化ADRとして記録し、自動的に決定の瞬間を検出し、コンテキスト、検討された代替案、根拠を記録します。今後の開発者がコードベースの形成理由を理解するためのADRログを維持します。

Automation Audit Ops

ECC用の証拠ベースの自動化インベントリとオーバーラップ監査ワークフロー。ユーザーがどのジョブ、フック、コネクタ、MCPサーバー、またはラッパーがライブか、壊れているか、冗長であるか、修正前に不足しているかを知りたい場合に使用します。

Grok

Delegate coding to xAI Grok Build CLI (features, PRs).

Setup Wizard Generator

NousResearch

OrganizationPopular

Generate a bash wizard guiding a human through manual setup.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Avoid API Keys in Production

Security Recommendation

Why API Keys Are Problematic

Preferred Alternative

Migration Path

Credential Storage

Implementation Checklist

Frequently asked questions

Related AI Skills

Set up your own AI workspace now