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/themulea/codex-agent-core-template/update-roadmapsnpx skills add TheMuleA/codex-agent-core-template --skill update-roadmapsgit clone --depth 1 https://github.com/TheMuleA/codex-agent-core-templateWhat 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.00029 | $0.00920 |
| Opus 5 | $0.00015 | $0.00460 |
| Sonnet 5 | $0.00006 | $0.00184 |
| Haiku 4.5 | $0.00003 | $0.00092 |
Grade A, and why
update-roadmaps 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 3d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
update-roadmaps
Назначение
Поддерживает planning items, project roadmaps, project pending items и work plans будущего развития Agent Core, инфраструктуры и выбранного project layer.
Канонические правила
- Маршрутизацию идей, pending items и work plans выполнять по
agent/protocols/status-and-planning-protocol.md. - Подробные правила не дублировать в этом skill.
Scope routing
Перед изменением определить scope:
- Agent Core — развитие самого агента, его правил, protocols, skills, boot, safety и структуры.
- Infrastructure — Git, GitHub, qmd, MCP, локальный поиск, автоматизация, integrations и tooling.
- Project — выбранный project layer, проектная роль и business backlog.
- Output — временные результаты и отчёты, которые не должны попадать в planning или roadmap.
Фактический project_id берётся из projects/index.md после выбора active project.
Файлы
Agent Core / Infrastructure
agent/planning.md— единый рабочий файл для Agent Core / infrastructure идей, открытых вопросов, ближайших решений, future directions и later / parking lot items.agent/work-plans/index.md— долгие agent/infrastructure work plans.
Project
projects/<project_id>/roadmaps/knowledge-base-fill.md— данные, которые нужно добавить в project knowledge base.projects/<project_id>/roadmaps/role-and-skills-development.md— навыки, компетенции и развитие выбранной роли.projects/<project_id>/pending-items.md— ожидающие business data и project questions.projects/<project_id>/work-plans/index.md— долгие project/business work plans.
Как выбирать место
- Agent planning — идея, открытый вопрос, future direction, ближайшее решение или later item по Agent Core / infrastructure.
- Project roadmap — направление будущего развития selected project layer, его базы знаний или роли.
- Pending item — открытый вопрос, хвост, ожидаемые данные или ближайшее нерешённое действие внутри selected project layer.
- Work plan — большая цель с горизонтом, шагами, критерием готовности и следующим конкретным шагом.
- Logs — уже выполненное действие.
- Raw — первичный источник данных.
- Устойчивое знание — потенциальный факт, событие, решение или принцип, который нужно сохранить в действующем рабочем месте своего scope с источником и подтверждением.
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.
- 3d ago First seen · 67 lines · 29 tokens per session scan A 96159d6f27be
update-roadmaps is a skill published in the GitHub repository TheMuleA/codex-agent-core-template (11 stars, last pushed 3mo ago), licensed MIT. It adds 29 tokens to every session and 920 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…