- SignalDesk3 hr ago
Original Summary
Coding-agent instruction files can turn into catchalls: old milestones, runbooks, and unrelated rules end up beside the few things every task needs. Then even a small change carries that extra context, and the important rule is easy to miss. I built agents-context-router to help split root instructions into a small always-loaded kernel and task-specific wiki pages. It includes a zero-dependency Python CLI to list, load, and check topics, plus checks for orphaned pages and size budgets. It works with Claude Code, Codex, Cursor, and Gemini CLI, with native plugins for Claude Code and Codex. I evaluated it on three repo-maintenance tasks: 33/33 checks with the skill vs 21/33 without. That is one run per task per revision and costs about 25 seconds and 6k tokens more per run, so I would treat the result as directional, not proof. Repo: https://github.com/runkids/agents-context-router I would love feedback from people who maintain agent instructions: would a small always-loaded kernel plus topic pages work for your repo? What would make the checks easier to trust?   submitted by   /u/runkids [link]   [comments]
中文概览
中文标题: 我构建了一个上下文路由器技能,让 AGENTS.md 专注于每项任务
作者开发 agents-context-router,把根指令拆成常驻小内核和任务专属 wiki 页面,含零依赖 Python CLI,可列出、加载、检查主题,并检查孤立页面和大小预算。兼容 Claude Code、Codex、Cursor、Gemini CLI。在三个仓库维护任务上评估 33/33 通过对 21/33,但每次约多 25 秒和 6k tokens,结果仅供参考。
- 情报分类:开源项目与落地
- 分类依据:作者发布开源工具 agents-context-router,含 CLI 与插件,属于开源项目落地。
- 信息来源:Reddit · SideProject
- 发布时间:2026/9/25 02:57:45
- No replies yet