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 agentmods add skills/yaalalabs/agent-kernel/ak-dev-sync-docs-from-branchnpx skills add yaalalabs/agent-kernel --skill ak-dev-sync-docs-from-branchgit 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-dev-sync-docs-from-branch)<a href="https://agentmods.dev/skills/yaalalabs/agent-kernel/ak-dev-sync-docs-from-branch"><img src="https://agentmods.dev/badge/skills/yaalalabs/agent-kernel/ak-dev-sync-docs-from-branch.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00077 | $0.01788 |
| Opus 5 | $0.00039 | $0.00894 |
| Sonnet 5 | $0.00015 | $0.00358 |
| Haiku 4.5 | $0.00008 | $0.00179 |
Grade A, and why
ak-dev-sync-docs-from-branch scanned grade A with 0 findings 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 5d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sync Documentation From Branch Changes
Use this skill when a feature branch or bugfix branch is functionally ready and you need to align Agent Kernel documentation with what actually changed.
This skill is for documentation maintenance driven by code diff, not for implementing the feature itself.
Goal
Read the branch delta, infer what user-facing and contributor-facing documentation changed, then update the relevant docs across the repository.
Required documentation surfaces covered by this skill:
ak-py/README.md- docs website content under
docs/— update existing pages, add pages, remove obsolete pages, and adjust intro/getting-started/reference sections as needed - README files under
ak-deployment/ - example README files when an example was added or changed, plus docs-site references to those examples
- root
README.md - root
DEVELOPER_GUIDE.md
When to Use This Skill
Use this skill when all of the following are true:
- The developer is on a feature or bugfix branch.
- The implementation is already done or nearly done.
- There are new commits on the branch and/or uncommitted local changes.
- The branch changes behavior, setup, APIs, integrations, deployment flows, examples, capabilities, or contributor workflows in ways documentation should reflect.
Do not use this skill as the first step of a feature. Use it near the end, before merge or PR finalization.
Step 1: Determine the Comparison Base
Find the correct baseline branch first.
Preferred order:
- The PR target branch if it is known.
- The upstream tracking branch for the current branch.
origin/develop.develop.
For this repository, prefer origin/develop or develop as the default base branch unless the PR target or upstream tracking branch says otherwise.
Use Git to identify the merge base between the current branch and that baseline.
Minimum evidence to gather:
- current branch name
- merge base commit
- commits since merge base
- staged changes
- unstaged changes
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.
- 5d ago First seen · 237 lines · 77 tokens per session scan A 0fe6e8036265
ak-dev-sync-docs-from-branch is a skill published in the GitHub repository yaalalabs/agent-kernel (166 stars, last pushed yesterday), licensed Apache-2.0. It adds 77 tokens to every session and 1,788 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. 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.
scaleway
Scaleway cloud integration for managing instances, Kapsule Kubernetes clusters, object storage, and managed databases via CLI and Terraform.
bitbucket
Bitbucket code repository integration for managing repos, branches, PRs, issues, and CI/CD pipelines.
cloudflare
Cloudflare integration for DNS, CDN, WAF, edge diagnostics, and remediation with zone management, analytics, security events, and cache control.
github
GitHub code repository integration for investigating code changes, deployments, commits, PRs, and suggesting fixes during RCA.