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/jimmypaolini/codebase/refresh-documentationnpx skills add JimmyPaolini/codebase --skill refresh-documentationgit clone --depth 1 https://github.com/JimmyPaolini/codebaseWhat 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.00051 | $0.00654 |
| Opus 5 | $0.00026 | $0.00327 |
| Sonnet 5 | $0.00010 | $0.00131 |
| Haiku 4.5 | $0.00005 | $0.00065 |
Grade A, and why
refresh-documentation 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refresh Documentation
This skill guides a systematic review and refresh of all documentation across the codebase. It is also invoked automatically each week by the refresh-documentation GitHub Actions workflow, which creates a GitHub issue assigned to Copilot.
When to Use This Skill
- When asked to "refresh documentation", "update docs", or "audit documentation"
- When documentation may be stale after significant code changes
- On the weekly scheduled cadence (triggered automatically via GitHub issue)
Scope
Documentation to review and update:
| Path | Description |
|---|---|
README.md |
Root codebase README |
documentation/**/*.md |
Core documentation files |
AGENTS.md |
Workspace-level Copilot instructions — skill table must stay in sync |
*/AGENTS.md |
Per-project Copilot instructions |
*/README.md |
Project README files |
.github/skills/**/SKILL.md |
Skill files (mirrored to documentation/skills/) |
Step-by-Step Workflow
Phase 1 — Audit
For each path in scope, read the documentation and cross-check it against the actual codebase. Classify every finding into one of three categories:
| Category | Criteria | Action |
|---|---|---|
| Deprecated | Documents a feature, command, file, or API that no longer exists | Remove the section or file |
| Outdated | Content exists but is inaccurate — wrong path, outdated command, incorrect description | Update to match current reality |
| Missing | A feature, project, convention, or workflow exists in the codebase but is undocumented | Create new documentation |
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 · 61 lines · 51 tokens per session scan A 6c488a5ff47e
refresh-documentation is a skill published in the GitHub repository JimmyPaolini/codebase (0 stars, last pushed yesterday), licensed MIT. It adds 51 tokens to every session and 654 once invoked, about $0.0003 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-09-01.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…