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/6529-collections/6529seize-frontend/commit-docs-updaternpx skills add 6529-Collections/6529seize-frontend --skill commit-docs-updatergit clone --depth 1 https://github.com/6529-Collections/6529seize-frontendWrote 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/6529-collections/6529seize-frontend/commit-docs-updater)<a href="https://agentmods.dev/skills/6529-collections/6529seize-frontend/commit-docs-updater"><img src="https://agentmods.dev/badge/skills/6529-collections/6529seize-frontend/commit-docs-updater.svg" alt="Measured on agentmods" 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.00057 | $0.01629 |
| Opus 5 | $0.00028 | $0.00814 |
| Sonnet 5 | $0.00011 | $0.00326 |
| Haiku 4.5 | $0.00006 | $0.00163 |
Grade A, and why
commit-docs-updater 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 5d 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Docs Updater
Keep ops/docs continuously accurate as a site guide and navigable information architecture. A commit is discovery input only, never part of docs narration.
Inputs
- Optional commit reference (
<commit>). - If no commit is provided, use
HEAD. - Treat exactly one commit as scope. Do not expand to ranges unless explicitly requested.
Core Rules
- Commit-guided, not commit-written:
- Use commit diff only to identify what user-facing areas might need docs updates.
- Never include commit hashes, commit subjects, PR/change-log framing, or "what changed in commit" sections in
ops/docs.
- User-facing only:
- Document behavior users can observe in UI/UX, routing, messaging, states, and outcomes.
- Ignore non-user-facing changes such as tests, snapshots, internal refactors, type-only cleanup, tooling, and internal file moves unless they cause user-visible behavior changes.
- Information architecture is part of the job:
- Reorganize
ops/docswhen structure is flat, fuzzy, or hard to navigate. - Use area-based folders, clear file names, and index pages that support browsing.
- Move, rename, split, merge, or remove docs pages when needed for clarity.
- Reorganize
- Timeless docs language:
- Describe current behavior, not development history.
- Write pages so they stay valid without needing commit context.
- Current-state only:
- Keep docs reflecting the latest structure and behavior.
- Do not keep legacy compatibility pages, shim pages, or old-path placeholders.
- Scale rules:
- Root
ops/docs/README.mdmust stay concise (target<=20task links inI am trying to...). - If an area exceeds
12content pages, create subarea folders with their ownREADME.mdindexes. - If an area has a topic cluster above
8pages, split that cluster into a subarea even if total area pages are below12.
- Root
- Ownership rules:
- Each user-facing behavior has one canonical docs page.
- Cross-area visibility is handled through links, not duplicate pages.
- Scope discipline:
- Use commit scope to detect impacted capabilities, then apply enough structural cleanup to keep the docs system coherent.
- Do not write non-user-facing technical history.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 161 lines · 57 tokens per session scan A 1cd4a6de4956
commit-docs-updater is a skill published in the GitHub repository 6529-Collections/6529seize-frontend (10 stars, last pushed today), licensed Apache-2.0. It adds 57 tokens to every session and 1,629 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…