Agent To Agent Auth

Organization

RedHatProductSecurity

agent-to-agent-auth

Enforce SPIFFE/SPIRE plus mTLS for agent-to-agent communication. Use when designing, building, or reviewing authentication between AI agents or multi-agent systems.

Overview

Publisher	RedHatProductSecurity
Repository	`prodsec-skills`
Skill name	`agent-to-agent-auth`
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 Agent To Agent Auth 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/agent-to-agent-auth
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/agent-to-agent-auth

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/agent-to-agent-auth .claude/skills/agent-to-agent-auth

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

Use it in TypingMind

Enable Agent To Agent Auth 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 Agent To Agent Auth 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 Agent To Agent Auth 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.

Agent-to-Agent Authentication

Security Requirement

Agent-to-agent communication MUST follow the service-to-service recommendation and implement SPIFFE/SPIRE+mTLS.

Why SPIFFE/SPIRE for Agent-to-Agent

Agents are software workloads, making SPIFFE the natural identity framework
No credentials exchanged over the network (SPIRE handles attestation and certificate issuance)
Mutual authentication ensures both agents verify each other's identity
Short-lived X.509 certificates (SVIDs) are automatically rotated
Each agent gets a unique SPIFFE ID that can be used for authorization decisions

Architecture


Agent A                          Agent B
  │                                │
  ├── SPIFFE ID:                   ├── SPIFFE ID:
  │   spiffe://domain/agent/a      │   spiffe://domain/agent/b
  │                                │
  ├── Gets SVID from SPIRE Agent   ├── Gets SVID from SPIRE Agent
  │                                │
  └── mTLS connection ────────────→└── Validates Agent A's SVID
      (presents SVID)                  (presents own SVID)

SPIFFE ID Convention for Agents

Use a consistent SPIFFE ID naming convention:


spiffe://<trust-domain>/agent/<agent-type>/<instance-id>

Examples:

spiffe://example.com/agent/data-analyst/prod-01
spiffe://example.com/agent/code-reviewer/staging-02

Implementation Checklist

Deploy SPIRE server and agents for the agent infrastructure
Register each agent type as a SPIRE workload entry
Configure agents to obtain SVIDs from the SPIRE agent
Implement mTLS for all agent-to-agent communication
Extract peer agent's SPIFFE ID from the TLS certificate for authorization
Define authorization policies based on SPIFFE IDs (which agents can communicate)
Monitor SVID rotation and certificate expiration

Frequently asked questions

What does the Agent To Agent Auth AI skill do?

Enforce SPIFFE/SPIRE plus mTLS for agent-to-agent communication. Use when designing, building, or reviewing authentication between AI agents or multi-agent systems.

Why use Agent To Agent Auth on TypingMind?

Because you install it once and use it with any model. Agent To Agent Auth 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 Agent To Agent Auth in TypingMind?

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

Which AI models can use Agent To Agent Auth?

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 Agent To Agent Auth?

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

Is the Agent To Agent Auth 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

Openclaw Testing

openclaw

OrganizationPopular

Choose proportional OpenClaw tests and checks, diagnose failures, and route environment-sensitive or release proof to its owner.

Release Openclaw Ci

Run, watch, debug, and summarize OpenClaw full release CI, release checks, live provider gates, install/update proofs, and release-secret preflights.

Release Openclaw Mac

Run or recover OpenClaw macOS release signing, notarization, appcast, and asset promotion.

Release Openclaw Maintainer

openclaw

OrganizationPopular

Prepare, publish, recover, or verify OpenClaw beta, stable, and extended-stable releases, including approved backports.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Agent-to-Agent Authentication

Security Requirement

Why SPIFFE/SPIRE for Agent-to-Agent

Architecture

SPIFFE ID Convention for Agents

Implementation Checklist

Frequently asked questions

Related AI Skills

Set up your own AI workspace now