Borrowing it
Nothing to install: this file belongs to actionhero/keryx. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/actionhero/keryx/main/.claude/agents/docs-sync.mdgit clone --depth 1 https://github.com/actionhero/keryxWrote 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/agents/actionhero/keryx/docs-sync)<a href="https://agentmods.dev/agents/actionhero/keryx/docs-sync"><img src="https://agentmods.dev/badge/agents/actionhero/keryx/docs-sync/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/agents/actionhero/keryx/docs-sync"><img src="https://agentmods.dev/badge/agents/actionhero/keryx/docs-sync.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.00587 |
| Opus 5.5 | $0.00000 | $0.00235 |
| Sonnet 5.5 | $0.00000 | $0.00117 |
| Haiku 4.5 | $0.00000 | $0.00059 |
Grade A, and why
docs-sync 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 2mo 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docs Sync
Check whether documentation needs updating after backend or framework code changes.
Instructions
1. Identify what changed
Run git diff main --name-only (or git diff HEAD~1 --name-only if already on main) to get the list of changed files. Focus on:
packages/keryx/— framework codeexample/backend/— example app code
Ignore changes to test files, .env files, and the docs/ directory itself.
2. Map code changes to docs
Use this mapping to identify which docs might need updates:
| Code Area | Relevant Docs |
|---|---|
classes/Action.ts, action files |
docs/guide/actions.md, docs/reference/actions.md |
classes/API.ts, api.ts |
docs/reference/classes.md |
| Initializer files | docs/guide/initializers.md, docs/reference/initializers.md |
classes/Channel.ts, channel files |
docs/guide/channels.md |
| MCP/OAuth code | docs/guide/mcp.md |
| Config files | docs/guide/config.md, docs/reference/config.md |
| Server/web files | docs/reference/servers.md |
| Middleware files | docs/guide/middleware.md |
| Task/fan-out code | docs/guide/tasks.md |
| Zod helpers, utilities | docs/reference/utilities.md |
| CLI/generators | docs/guide/cli.md |
| TypedError, Connection, Logger | docs/reference/classes.md |
| Auth-related code | docs/guide/authentication.md |
| Observability code | docs/guide/observability.md |
3. Check for staleness
For each relevant doc:
- Read the doc file
- Read the changed source code
- Compare: does the doc accurately reflect the current code?
Look for:
- Changed signatures — method parameters, return types, or names that differ from what the doc shows
- New features — exported classes, methods, config options, or action properties not mentioned in docs
- Removed features — things documented that no longer exist in code
- Changed defaults — config defaults, timeout values, etc. that have been updated
- Incorrect examples — code snippets in docs that would no longer work
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.
- 2mo ago First seen · 58 lines · 0 tokens per session scan A a10e9637c91c
docs-sync is an agent published in the GitHub repository actionhero/keryx (46 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 587 tokens. 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 agents, from other repositories
reviewer
Code review specialist for quality/security analysis.
Application Security Engineer
AppSec specialist who secures the software development lifecycle through threat modeling, secure code review, SAST/DAST integration, and developer security education that makes secure code the default.
Codebase Archaeologist
Multi-session, multi-tool drift detection specialist who audits codebases touched by several AI coding tools (Claude, Cursor, Copilot, Windsurf, etc.) over time, finding silent logic mismatches, dead code, and doc-vs-code divergence that no single session would ever notice on its own.
Minimal Change Engineer
Engineering specialist focused on minimum-viable diffs — fixes only what was asked, refuses scope creep, prefers three similar lines over a premature abstraction. The discipline that prevents bug-fix PRs from becoming refactor avalanches.
code-reviewer
Use proactively after completing code changes, or when the user asks for a code review. Reviews diffs against the base branch for correctness, test quality, conventions, duplication, security, and simplicity. Returns structured findings.
pr-reviewer
State-of-the-art QA & security reviewer for PRs in the opencode-swarm plugin. Reconstructs intent, verifies implementation, and hunts for defects, security issues, and shipped-vs-claimed mismatches. Operates read-only. Never approves without positive evidence. Never invents repository facts.