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 agents/actionhero/keryx/docs-syncgit clone --depth 1 https://github.com/actionhero/keryxWhat 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.00000 | $0.00587 |
| Opus 5 | $0.00000 | $0.00293 |
| Sonnet 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 yesterday.
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.
- yesterday First seen · 58 lines · 0 tokens per session scan A a10e9637c91c
docs-sync is an agent published in the GitHub repository actionhero/keryx (33 stars, last pushed 9d 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
switchboard
This project uses the Switchboard protocol for cross-IDE agent collaboration.
tool-developer
Builds new UEFN Toolbelt tools autonomously. Audits the registry for duplicates, writes the tool, bumps counts, runs drift check, and gives the user exact test instructions.
verse-deployer
Verse codegen and error-fix loop for UEFN Toolbelt. Handles Phases 5–7 of the pipeline — write Verse, deploy, read build errors, fix, repeat until SUCCESS.
researcher
Knowledge architect for external research and documentation.
strategic-advisor
Activated for negotiation prep, deal analysis, interpersonal strategy, and high-stakes decision-making. Combines game theory with psychological awareness.
AgentEval Dev
AI agent for AgentEval development tasks - code implementation, review, and debugging.