Agent skill

Ak Dev New Guardrail Provider

by yaalalabs in yaalalabs/agent-kernel

Step-by-step guide for adding a new guardrail provider to Agent Kernel.

Apache-2.0Auto-check passedAI & LLM Engineering

Install Ak Dev New Guardrail Provider

skills CLI
$ npx skills add yaalalabs/agent-kernel --skill ak-dev-new-guardrail-provider -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install yaalalabs/agent-kernel ak-dev-new-guardrail-provider --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/yaalalabs/agent-kernel.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/ak-dev-new-guardrail-provider .claude/skills/ak-dev-new-guardrail-provider && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
ak-dev-new-guardrail-provider
GitHub stars
192
Token cost
~3.5k tokens
SKILL.md length
748 words
Files
1
Skills in repo
23
Repo updated
First seen
Licence
Apache-2.0

At a glance

Step-by-step guide for adding a new guardrail provider to Agent Kernel.

  • Works in 10 steps: Create the Guardrail Provider File → Implement the Base Provider Class → Implement the Input Guardrail → …
  • You need to integrate a new content safety
  • SKILL.md covers Existing Providers, Architecture Overview, Step-by-Step and Checklist
  • Needs WALLED_API_KEY

What it does

Ak Dev New Guardrail Provider is an agent skill from yaalalabs/agent-kernel. Step-by-step guide for adding a new guardrail provider to Agent Kernel. Use this skill when you need to integrate a new content safety or guardrail service (beyond OpenAI Guardrails, AWS Bedrock Guardrails, and Walled AI). Covers implementing input/output guardrails, factory registration, configuration, and testing.

Its SKILL.md is about 3.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in AI & LLM Engineering, covering LLM guardrails. It works with OpenAI and Amazon Bedrock. The repository describes itself as: The Operating System for Scalable Enterprise AI Agents - Run, orchestrate, and deploy Compliant Enterprise AI Agents at scale across frameworks, without lock-in, rewrites or… The licence is Apache-2.0.

When your agent uses it

  • You need to integrate a new content safety
  • Guardrail service (beyond OpenAI Guardrails
  • AWS Bedrock Guardrails

Example prompts

  • “/ak-dev-new-guardrail-provider”

Requirements

  • Python 3
  • A credential in WALLED_API_KEY

Workflow steps

10 steps, taken from the step headings in SKILL.md.

  1. Create the Guardrail Provider File
  2. Implement the Base Provider Class
  3. Implement the Input Guardrail
  4. Implement the Output Guardrail
  5. Register with the Factory
  6. Add Configuration
  7. Add Optional Dependencies
  8. Add Tests
  9. Add Example
  10. Add Documentation

What it can do on your machine

Read from SKILL.md and the folder at commit 97fa8d9. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are python, yaml and toml).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • WALLED_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Ak Dev New Guardrail Provider loads about 3.5k tokens when it runs. Until then it costs about 87 tokens; SKILL.md has 748 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~87
When it runs · the whole SKILL.md, loaded when a task matches
~3.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from yaalalabs/agent-kernel at commit 97fa8d9, republished under its Apache-2.0 licence (© yaalalabs). 748 words, ~3,549 tokens.

Download SKILL.mdSave it as .claude/skills/ak-dev-new-guardrail-provider/SKILL.md (or your agent's skills folder).
name
ak-dev-new-guardrail-provider
description
Step-by-step guide for adding a new guardrail provider to Agent Kernel. Use this skill when you need to integrate a new content safety or guardrail service (beyond OpenAI Guardrails, AWS Bedrock Guardrails, and Walled AI). Covers implementing input/output guardrails, factory registration, configuration, and testing.
license
Apache-2.0
metadata.author
yaalalabs
metadata.category
developer

Adding a New Guardrail Provider

This guide walks through adding a new guardrail provider to Agent Kernel. Use the existing OpenAI (ak-py/src/agentkernel/guardrail/openai.py), Bedrock (ak-py/src/agentkernel/guardrail/bedrock.py), and Walled AI (ak-py/src/agentkernel/guardrail/walledai.py) implementations as reference.

Existing Providers

ProviderType valueFeaturesExtra
OpenAIopenaiContent moderation, jailbreak detection, PII detection (via config JSON)agentkernel[openai]
AWS BedrockbedrockAWS-managed guardrails (ID + version)agentkernel[aws]
Walled AIwalledaiContent safety + PII redaction/unmasking (via pii flag)agentkernel[walledai]

Architecture Overview

Agent Kernel's guardrail system uses the hook mechanism:

  • Input guardrails subclass the no-op InputGuardrail class in guardrail/guardrail.py (itself a PreHook) — they inspect incoming requests and can halt execution by returning an AgentReply instead of passing through
  • Output guardrails subclass the no-op OutputGuardrail class (itself a PostHook) — they inspect agent replies and can modify or replace the response
  • BaseGuardrailUtil (also in guardrail/guardrail.py) provides shared text-extraction helpers and is mixed into concrete guardrail classes
  • Factories in guardrail.py select the appropriate provider based on AKConfig.guardrail configuration; unknown types raise an exception, and the no-op classes are returned only when guardrails are disabled
  • Guardrails are registered as system hooks in Runtime, meaning they apply to all agents automatically

Step-by-Step

1. Create the Guardrail Provider File

Create ak-py/src/agentkernel/guardrail/<provider>.py.

2. Implement the Base Provider Class

The base class is a plain provider-specific class that holds shared client/config setup. The concrete input/output classes (steps 3 and 4) combine it with the no-op InputGuardrail/OutputGuardrail hooks and the BaseGuardrailUtil mixin. Real examples: class OpenAIInputGuardrail(BaseGuardrailUtil, BaseOpenAIGuardrail, InputGuardrail) in openai.py, class BedrockInputGuardrail(BaseGuardrailUtil, BaseBedrockGuardrail, InputGuardrail) in bedrock.py, and class WalledAIInputGuardrail(InputGuardrail, WalledAIGuardrailBase) in walledai.py.

python
# ak-py/src/agentkernel/guardrail/<provider>.py
import logging
import os
from abc import ABC
from agentkernel.core.config import AKConfig

logger = logging.getLogger("ak.guardrail.<provider>")


class Base<Provider>Guardrail(ABC):
    """Base class for <Provider> guardrail implementations."""

    def __init__(self):
        config = AKConfig.get().guardrail
        # Initialize the guardrail client/SDK. Secrets come from environment
        # variables, not config (e.g., Walled AI reads WALLED_API_KEY).
        # e.g., self._client = ProviderClient(api_key=os.getenv("<PROVIDER>_API_KEY"))
        logger.info("<Provider> guardrail initialized")
3. Implement the Input Guardrail

If you are modifying an input request with the guardrail, then you should make sure to return the modified request and all the other unmodified requests. For example, if you have 3 requests and the guardrail modifies the first one, then you should return a list of 3 requests with the first one modified and the other two unmodified.

python
from agentkernel.core.base import Agent, Session
from agentkernel.core.model import AgentReply, AgentReplyText, AgentRequest
from agentkernel.guardrail.guardrail import BaseGuardrailUtil, InputGuardrail, OutputGuardrail


class <Provider>InputGuardrail(BaseGuardrailUtil, Base<Provider>Guardrail, InputGuardrail):
    """Validates input requests using <Provider> guardrail service."""

    async def on_run(
        self, session: Session, agent: Agent, requests: list[AgentRequest]
    ) -> list[AgentRequest] | AgentReply:
        # 1. Extract text content from requests
        text = BaseGuardrailUtil._extract_text_from_requests(requests)
        if not text:
            return requests  # No text to validate, pass through

        # 2. Call the guardrail service
        try:
            result = await self._validate(text)
        except Exception as e:
            logger.error(f"Guardrail validation error: {e}")
            return requests  # Fail open (or fail closed based on policy)

        # 3. If content is flagged, return an AgentReply to halt execution
        if result.is_flagged:
            message = self._build_intervention_message(result)
            logger.warning(f"Input guardrail triggered: {message}")
            return AgentReplyText(
                response=message,
                prompt=text
            )

        # 4. Content is safe, pass through
        return requests

    async def _validate(self, text: str):
        """Call the guardrail provider's API to validate text."""
        # Provider-specific validation logic
        # return self._client.validate(text=text, source="INPUT")
        pass

    def _build_intervention_message(self, result) -> str:
        """Build a user-friendly message when content is blocked."""
        return "I apologize, but I'm unable to process this request as it may violate content safety guidelines."

    def name(self) -> str:
        return "<provider>_input_guardrail"
4. Implement the Output Guardrail
python
class <Provider>OutputGuardrail(BaseGuardrailUtil, Base<Provider>Guardrail, OutputGuardrail):
    """Validates agent output using <Provider> guardrail service."""

    async def on_run(
        self, session: Session, requests: list[AgentRequest], agent: Agent, agent_reply: AgentReply
    ) -> AgentReply:
        # 1. Extract text from the reply
        text = BaseGuardrailUtil._extract_text_from_reply(agent_reply)
        if not text:
            return agent_reply  # No text to validate

        # 2. Call the guardrail service
        try:
            result = await self._validate(text)
        except Exception as e:
            logger.error(f"Output guardrail validation error: {e}")
            return agent_reply  # Fail open

        # 3. If content is flagged, modify the reply
        if result.is_flagged:
            message = self._build_intervention_message(result)
            logger.warning(f"Output guardrail triggered: {message}")
            agent_reply.response = message
            return agent_reply

        # 4. Content is safe, return unchanged
        return agent_reply

    async def _validate(self, text: str):
        """Call the guardrail provider's API to validate text."""
        pass

    def _build_intervention_message(self, result) -> str:
        return "The generated response was flagged by content safety filters and has been blocked."

    def name(self) -> str:
        return "<provider>_output_guardrail"
5. Register with the Factory

Both factories in ak-py/src/agentkernel/guardrail/guardrail.py share the house pluggable-backend shape from core/util/factory.py (resolve_dotted, require_extra, AKConfigError — the same pattern used by the trace, session/thread/multimodal store, and sandbox provider factories): a short-circuit for disabled, if-per-built-in with the SDK import wrapped in require_extra (so a missing optional dependency raises an actionable ImportError naming the pip extra), then a dotted-path "bring your own" fallback for anything else:

python
_BUILTIN_GUARDRAILS = ["openai", "bedrock", "walledai"]

class InputGuardrailFactory:
    @staticmethod
    def get() -> PreHook:
        config = AKConfig.get().guardrail.input
        if not config.enabled:
            return InputGuardrail()  # OFF: pass-through hook
        gtype = config.type
        if gtype == "openai":
            with require_extra("openai", "guardrail.input.type: openai"):
                from .openai import OpenAIInputGuardrail
            return OpenAIInputGuardrail()
        if gtype == "bedrock":
            with require_extra("aws", "guardrail.input.type: bedrock"):
                from .bedrock import BedrockInputGuardrail
            return BedrockInputGuardrail()
        if gtype == "walledai":
            with require_extra("walledai", "guardrail.input.type: walledai"):
                from .walledai import WalledAIInputGuardrail
            return WalledAIInputGuardrail()
        if gtype == "<provider>":                                         # ADD THIS
            with require_extra("<provider>", "guardrail.input.type: <provider>"):
                from .<provider> import <Provider>InputGuardrail
            return <Provider>InputGuardrail()
        if "." not in gtype:
            raise AKConfigError(
                f"unknown guardrail type '{gtype}'; expected one of {_BUILTIN_GUARDRAILS} or a dotted path to an InputGuardrail subclass"
            )
        return resolve_dotted(gtype, base=InputGuardrail)()  # bring-your-own

# Same pattern for OutputGuardrailFactory.get()

A dotted type (e.g. myorg.guardrails.CustomInputGuardrail) resolves via resolve_dotted without any factory edit at all — only add an if branch here for a first-party, in-repo provider you want addressable by a short name.

Show full SKILL.md (328 more words)Show less
6. Add Configuration

Update the guardrail config in ak-py/src/agentkernel/core/config.py:

The existing _GuardrailParamConfig.type is a free-form string (no regex pattern) described as "a built-in short name (openai, bedrock, walledai) or a dotted path to an InputGuardrail/OutputGuardrail subclass" — do not add a pattern= constraint back, since that would break the bring-your-own path. Its only fields are enabled, type, pii, config_path, model, id, and version — there is no api_key field. Secrets come from environment variables (e.g., Walled AI reads WALLED_API_KEY). If your provider needs new config fields, add them to _GuardrailParamConfig in core/config.py:

yaml
# config.yaml
guardrail:
  input:
    enabled: true
    type: <provider>
    # provider-specific fields (must exist on _GuardrailParamConfig)
    config_path: guardrails_input.json
  output:
    enabled: true
    type: <provider>
    config_path: guardrails_output.json
7. Add Optional Dependencies

If the provider requires additional packages, add them to ak-py/pyproject.toml either under an existing group or a new one:

toml
[project.optional-dependencies]
# Option A: Add to existing openai group if it's an OpenAI-based provider
# Option B: Create a new group
<provider>-guardrail = [
    "provider-sdk>=x.y.z",
]
8. Add Tests

Add tests to the existing consolidated ak-py/tests/test_guardrail.py, which covers the no-op hooks, the factories (including test_get_raises_exception_for_unknown_type), and the OpenAI provider:

python
import pytest
from unittest.mock import AsyncMock, patch
from agentkernel.core.model import AgentRequestText, AgentReplyText
from agentkernel.guardrail.<provider> import (
    <Provider>InputGuardrail,
    <Provider>OutputGuardrail
)

@pytest.mark.asyncio
async def test_input_guardrail_passes_safe_content():
    guardrail = <Provider>InputGuardrail()
    # Mock the validation to return safe
    guardrail._validate = AsyncMock(return_value=MockResult(is_flagged=False))
    requests = [AgentRequestText(prompt="What is 2+2?")]
    result = await guardrail.on_run(session, agent, requests)
    assert isinstance(result, list)  # passed through

@pytest.mark.asyncio
async def test_input_guardrail_blocks_unsafe_content():
    guardrail = <Provider>InputGuardrail()
    guardrail._validate = AsyncMock(return_value=MockResult(is_flagged=True))
    requests = [AgentRequestText(prompt="unsafe content")]
    result = await guardrail.on_run(session, agent, requests)
    assert isinstance(result, AgentReplyText)  # halted
9. Add Example

Create examples/cli/guardrail/<provider>/ with:

  • demo.py — agent with guardrails enabled
  • config.yaml — guardrail configuration
  • pyproject.toml — dependencies
  • demo_test.py — tests verifying guardrail triggers
10. Add Documentation

Add guardrail provider docs to docs/docs/advanced/guardrails.md or create docs/docs/advanced/guardrails-<provider>.md.

Then update the landing page inventories in docs/src/components/*/data.tsx: add a tile to the Observability, safety & testing row in IntegrationsMarquee/data.tsx (role Guardrail, href to the provider's docs page, logo or react-icons/si glyph), and add the provider to the Content Guardrails card's tags and description under the Guard tab in FeatureExplorer/data.tsx. Logo sourcing and the build check are in ak-dev-sync-docs-from-branch, Docs-Site Landing and Features Pages.

Then check the docs-site features page (docs/src/pages/features.tsx): the Problem section's rows name the built-in guardrail providers in a with: cell ("OpenAI and Bedrock guardrails built in"); add the new provider wherever the existing ones are listed (grep docs/src/pages/*.tsx for "Bedrock").

Checklist

  • ak-py/src/agentkernel/guardrail/<provider>.py with base, input, and output classes
  • Factory registration in guardrail.py for both input and output
  • Configuration support via type: "<provider>" in config.yaml
  • Optional dependencies in pyproject.toml (if needed)
  • Unit tests added to ak-py/tests/test_guardrail.py
  • Example in examples/cli/guardrail/<provider>/
  • Documentation in docs/docs/advanced/guardrails*.md
  • Landing page inventories: marquee tile (IntegrationsMarquee/data.tsx), Content Guardrails card tags (FeatureExplorer/data.tsx); features page with: cells

© yaalalabs, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/ak-dev-new-guardrail-provider of yaalalabs/agent-kernel.

Open the folder on GitHubat commit 97fa8d9

Compare with similar skills

Ak Dev New Guardrail Provider next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Ak Dev New Guardrail Provider compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Ak Dev New Guardrail Provider this skillyaalalabs/agent-kernel192—~3.5kAutomated safety check: PassApache-2.0
Bedrockitsmostafa/aws-agent-skills1.2k—~4.9kAutomated safety check: PassMIT
Migrating Openai Agents SDK To Pydantic AIpydantic/pydantic-ai21k—~1.8kAutomated safety check: PassMIT
Openai Agentscoco-research/coco531—~3.3kAutomated safety check: PassMIT
Neo4j Genai Plugin Skillneo4j-contrib/neo4j-skills114—~3kAutomated safety check: NotesMIT
Amazon Bedrockaws/agent-toolkit-for-aws2.8k—~8.6kAutomated safety check: PassApache-2.0

Similar skills

  • Bedrock

    itsmostafa/aws-agent-skills

    AWS Bedrock foundation models for generative AI. An agent skill from itsmostafa/aws-agent-skills.

    1.2k GitHub stars~4.9k tokensUpdated 5 days ago
    AI & LLM EngineeringAuto-check passed
  • Official

    Migrate Python OpenAI Agents SDK applications to Pydantic AI and, when warranted, Pydantic AI Harness.

    21k GitHub stars~1.8k tokensUpdated today
    AI & LLM EngineeringAuto-check passed
  • Openai Agents

    coco-research/coco

    Build AI applications with OpenAI Agents SDK - text agents, voice agents, multi-agent handoffs, tools with Zod schemas, guardrails, and streaming.

    531 GitHub stars~3.3k tokensUpdated today
    AI & LLM EngineeringAuto-check passed
  • Neo4j Genai Plugin Skill

    neo4j-contrib/neo4j-skills

    Use Neo4j GenAI Plugin ai.text. An agent skill from neo4j-contrib/neo4j-skills.

    114 GitHub stars~3k tokensUpdated yesterday
    AI & LLM EngineeringAuto-check: notes
  • Amazon Bedrock

    aws/agent-toolkit-for-aws

    Official

    Builds generative AI applications on Amazon Bedrock. An agent skill from aws/agent-toolkit-for-aws.

    2.8k GitHub stars~8.6k tokensUpdated yesterday
    AI & LLM EngineeringAuto-check passed
  • AWS Cloudformation Bedrock

    giuseppe-trisciuoglio/developer-kit

    Provides AWS CloudFormation patterns for Amazon Bedrock resources including agents, knowledge bases, data sources, guardrails, prompts, flows, and inference profiles.

    357 GitHub stars~3.2k tokensUpdated 1 mo ago
    AI & LLM EngineeringAuto-check: notes

More from yaalalabs/agent-kernel

All 23 skills in this repo
  • Ak Dev Code Quality

    yaalalabs/agent-kernel

    Code quality standards, formatting, Python style rules (classes over script-style functions, configuration-field rules), commit conventions, and PR workflow for Agent Kernel development.

    192 GitHub stars~2.5k tokensUpdated 2 days ago
    Auto-check passed
  • Ak Dev New Evaluator Provider

    yaalalabs/agent-kernel

    Step-by-step guide for adding a new built-in test evaluator provider to Agent Kernel (beyond DeepEval, Opik and JEV).

    192 GitHub stars~3.4k tokensUpdated 2 days ago
    Auto-check passed
  • Step-by-step guide for adding a new knowledge base backend to Agent Kernel.

    192 GitHub stars~5.1k tokensUpdated 2 days ago
    Auto-check passed
  • Ak Dev New Messaging Integration

    yaalalabs/agent-kernel

    Step-by-step guide for adding a new messaging platform integration to Agent Kernel.

    192 GitHub stars~4.6k tokensUpdated 2 days ago
    Auto-check passed
  • Ak Dev New Multimodal Storage

    yaalalabs/agent-kernel

    Step-by-step guide for adding a new multimodal attachment storage backend to Agent Kernel.

    192 GitHub stars~4.3k tokensUpdated 2 days ago
    Auto-check passed
  • Ak Dev New Queue Transport

    yaalalabs/agent-kernel

    Step-by-step guide for adding a new queue transport to Agent Kernel's execution pipeline.

    192 GitHub stars~2.7k tokensUpdated 2 days ago
    Auto-check passed

Questions about Ak Dev New Guardrail Provider

What does Ak Dev New Guardrail Provider do?

Step-by-step guide for adding a new guardrail provider to Agent Kernel. Ak Dev New Guardrail Provider is an agent skill from yaalalabs/agent-kernel. Step-by-step guide for adding a new guardrail provider to Agent Kernel.

When should I use Ak Dev New Guardrail Provider?

Ak Dev New Guardrail Provider fits situations like: you need to integrate a new content safety; guardrail service (beyond OpenAI Guardrails; AWS Bedrock Guardrails.

How do I install Ak Dev New Guardrail Provider in Claude Code?

Run `npx skills add yaalalabs/agent-kernel --skill ak-dev-new-guardrail-provider -a claude-code`. Or copy the skill folder (.agents/skills/ak-dev-new-guardrail-provider in yaalalabs/agent-kernel) into .claude/skills/ak-dev-new-guardrail-provider in your project. Claude Code loads it when a task matches its description.

How do I install Ak Dev New Guardrail Provider in Codex?

Run `npx skills add yaalalabs/agent-kernel --skill ak-dev-new-guardrail-provider -a codex`. Or copy the skill folder (.agents/skills/ak-dev-new-guardrail-provider in yaalalabs/agent-kernel) into .agents/skills/ak-dev-new-guardrail-provider in your project. Codex loads it when a task matches its description.

Can I use Ak Dev New Guardrail Provider in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add yaalalabs/agent-kernel --skill ak-dev-new-guardrail-provider -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ak-dev-new-guardrail-provider, .gemini/skills/ak-dev-new-guardrail-provider, .github/skills/ak-dev-new-guardrail-provider and .opencode/skills/ak-dev-new-guardrail-provider in your project.

What does Ak Dev New Guardrail Provider need to run?

Going by SKILL.md and its folder, Ak Dev New Guardrail Provider needs credentials named WALLED_API_KEY. Our summary lists: Python 3; A credential in WALLED_API_KEY.

Does Ak Dev New Guardrail Provider access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Ak Dev New Guardrail Provider safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Ak Dev New Guardrail Provider use?

Ak Dev New Guardrail Provider is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Ak Dev New Guardrail Provider use?

About 3.5k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Ak Dev New Guardrail Provider?

Skills that share tags, products or a category with Ak Dev New Guardrail Provider: Bedrock (itsmostafa/aws-agent-skills, 1.2k stars), Migrating Openai Agents SDK To Pydantic AI (pydantic/pydantic-ai, 21k stars), Openai Agents (coco-research/coco, 531 stars) and Neo4j Genai Plugin Skill (neo4j-contrib/neo4j-skills, 114 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ak Dev New Guardrail Provider?

yaalalabs (a GitHub organization) maintains it in yaalalabs/agent-kernel, which has 192 GitHub stars. The repository holds 23 skills in this directory. The repository was last updated on October 9, 2026.

Source: yaalalabs/agent-kernel on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.