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 skills add Muriel-Salvan/x_aeon_agents --skill updating-docgit clone --depth 1 https://github.com/Muriel-Salvan/x_aeon_agentsWrote 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/muriel-salvan/x_aeon_agents/updating-doc)<a href="https://agentmods.dev/skills/muriel-salvan/x_aeon_agents/updating-doc"><img src="https://agentmods.dev/badge/skills/muriel-salvan/x_aeon_agents/updating-doc/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/skills/muriel-salvan/x_aeon_agents/updating-doc"><img src="https://agentmods.dev/badge/skills/muriel-salvan/x_aeon_agents/updating-doc.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.00055 | $0.01107 |
| Opus 5.5 | $0.00022 | $0.00443 |
| Sonnet 5.5 | $0.00011 | $0.00221 |
| Haiku 4.5 | $0.00006 | $0.00111 |
Grade A, and why
updating-doc 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Updating documentation
Sequential steps to be followed when using this skill
When updating documentation, follow those steps.
Create the updating-doc Execution Checklist (MANDATORY)
- Before executing anything, create a checklist named updating-doc Execution Checklist with all steps of these instructions.
- The updating-doc Execution Checklist must include all numbered steps explicitly.
- After completing each step of these instructions, mark the item in the updating-doc Execution Checklist as completed.
- Do not skip any item.
- If an item cannot be executed, explicitly explain why.
- Never mark the task as completed while any item from the updating-doc Execution Checklist remains open.
1. Inform the user
- Always tell the user "SKILL: I am updating documentation" to inform the user that you are running this skill.
2. Check the existing README content
- Always read the existing README content and think about which parts of it should be updated with the task you just implemented.
- Always adapt the content to what is relevant for the task you implemented.
For example, if README.md has such a section:
## Main features
This executable processes input data files (*.csv) to output statistics.
and you just implemented a feature adding a timeout feature, then you should update this README section like this:
## Main features
This executable processes input data files (*.csv) to output statistics.
### 3. Timeout
If processing a file takes more than a given number of seconds, then processing stops and an error is returned (timeout behaviour).
4. Update the README CLI usage section
- Always check if the real CLI options are documented correctly in the Usage section of the README file.
For example, if README.md has such a section:
## CLI options
* `--process FILE`: Specify the file to process
and you just implemented a feature adding a CLI timeout option, then you should update this README section like this:
## CLI options
* `--process FILE`: Specify the file to process
* `--timeout SECS`: Specify the number of seconds before processing times out (default: 60)
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 · 172 lines · 55 tokens per session scan A 78e1eebf8866
updating-doc is a skill published in the GitHub repository Muriel-Salvan/x_aeon_agents (2 stars, last pushed 3d ago), licensed BSD-3-Clause. It adds 55 tokens to every session and 1,107 once invoked, about $0.0002 per session on Opus 5.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-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…