Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add yaalalabs/agent-kernel --skill ak-add-integrationgit clone --depth 1 https://github.com/yaalalabs/agent-kernelWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/yaalalabs/agent-kernel/ak-add-integration)<a href="https://agentmods.dev/skills/yaalalabs/agent-kernel/ak-add-integration"><img src="https://agentmods.dev/badge/skills/yaalalabs/agent-kernel/ak-add-integration/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/yaalalabs/agent-kernel/ak-add-integration"><img src="https://agentmods.dev/badge/skills/yaalalabs/agent-kernel/ak-add-integration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 124 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 292 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Data Exfiltration · line 83 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 254 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00059 | $0.02941 |
| Opus 5.5 | $0.00024 | $0.01176 |
| Sonnet 5.5 | $0.00012 | $0.00588 |
| Haiku 4.5 | $0.00006 | $0.00294 |
Grade A, and why
ak-add-integration scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
4. Check health: `curl http://localhost:8000/health` How it starts
The opening of the file, as written. The whole thing — 435 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add a Messaging Integration
Use this skill to add a messaging platform integration to your Agent Kernel project.
Instructions for the Agent
When the user wants to add a messaging integration, follow this workflow:
Step 1: Identify the Project
Check the user's current project for:
- An existing
pyproject.tomlwithagentkerneldependency - An agent definition file (e.g.,
app.py,server.py,demo.py) - An existing
config.yaml
If not found, suggest using the ak-init skill first.
Step 2: Ask Which Integration
Which messaging platform would you like to integrate?
- Slack — Bot that responds in Slack channels and threads
- WhatsApp — Bot via WhatsApp Business API (Meta)
- Facebook Messenger — Bot via Messenger Platform (Meta)
- Instagram — Bot via Instagram Messaging API (Meta)
- Telegram — Bot via Telegram Bot API
- Teams — Bot via Microsoft Teams (Azure Bot Framework)
- Gmail — Email-based agent via Gmail API (polling)
Step 3: Generate Changes
The snippets below mount each integration with IOHandler.run(...), the local/containerized
pipeline. If the project deploys on AWS Lambda (the ak-serverless Terraform module), host the
same handler in the request-handler Lambda instead, and add the platform extra to both the
request-handler and the response-handler packages (agentkernel[aws,<platform>], not the api extra):
# lambda_request_handler.py
from agentkernel.aws import Lambda, LambdaWebhookHost
from agentkernel.integration.adapter import WebhookRESTRequestHandler
from agentkernel.slack import SlackInboundAdapter # or the platform's inbound adapter
slack = LambdaWebhookHost(WebhookRESTRequestHandler(SlackInboundAdapter()))
@Lambda.register("/slack/events", method="POST") # the adapter's webhook_path
def slack_events(event, context):
return slack.handle(event, context)
handler = Lambda.handler
- WhatsApp, Messenger and Instagram also register the handshake:
Lambda.register("/<platform>/webhook", method="GET")(host.challenge).
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 11d ago Changed ba8ab3e2f589
- 12d ago Changed · +38 lines 1521f77e22dd
- 25d ago Changed 1689b85dca1b
- 28d ago Changed cb9775f9b3e9
- 1mo ago Changed · +10 lines f7b7a569a7bf
- 1mo ago Changed 05d67810c304
- 1mo ago Changed 659f3f4404b3
- 1mo ago First seen · 387 lines · 59 tokens per session scan A 98e160858a12
ak-add-integration is a skill published in the GitHub repository yaalalabs/agent-kernel (192 stars, last pushed yesterday), licensed Apache-2.0. It adds 59 tokens to every session and 2,941 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
notion
Notion workspace integration for searching pages, managing databases, creating postmortems, and exporting RCA findings.
datadog
Datadog monitoring integration for querying logs, metrics, monitors, events, traces, hosts, and incidents during RCA investigations.
postmortem
Postmortem generation and management tools for writing, reading, and versioning incident postmortems.
coroot
Coroot eBPF-powered observability integration for kernel-level infrastructure monitoring, incidents, traces, logs, service maps, deployments, nodes, costs, and risks.
github
GitHub code repository integration for investigating code changes, deployments, commits, PRs, and suggesting fixes during RCA.
slack
Slack integration tools for reading channel messages and thread replies.