Borrowing it
Nothing to install: this file belongs to atra-consulting/coding-with-ai-lab. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/atra-consulting/coding-with-ai-lab/main/.claude/skills/update-agent-files/SKILL.mdgit clone --depth 1 https://github.com/atra-consulting/coding-with-ai-labWrote 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/atra-consulting/coding-with-ai-lab/update-agent-files)<a href="https://agentmods.dev/skills/atra-consulting/coding-with-ai-lab/update-agent-files"><img src="https://agentmods.dev/badge/skills/atra-consulting/coding-with-ai-lab/update-agent-files/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/atra-consulting/coding-with-ai-lab/update-agent-files"><img src="https://agentmods.dev/badge/skills/atra-consulting/coding-with-ai-lab/update-agent-files.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.00068 | $0.05757 |
| Opus 5.5 | $0.00027 | $0.02303 |
| Sonnet 5.5 | $0.00014 | $0.01151 |
| Haiku 4.5 | $0.00007 | $0.00576 |
Grade A, and why
update-agent-files 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 9d 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 — 413 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Agent Files
Claude Code + Copilot CLI: this skill runs in both. "Ask the user" =
AskUserQuestion(Claude Code) /ask_user(Copilot CLI). "Start a subagent" =Agent/Tasktool (Claude Code) /tasktool (Copilot CLI), with the agent's name as the type.$ARGUMENTS= the text typed after the skill name.
You keep this project's docs in sync with its code. Targets: .claude/agents/*.md, docs/specs/*.md (the SPECS*.md set plus DOMAIN.md), and CLAUDE.md.
This project: Node/Express/TypeScript backend (backend/) + Angular 21 frontend (frontend/), Drizzle ORM over libSQL/SQLite. Curated spec set. Curated agent roster. Default: you update existing docs in place. You may create a missing spec or agent file, or delete an obsolete one, but only when the code clearly demands it — see Create & Delete Docs below.
Writing Style
Short and brief. Short sentences. Simple words non-native speakers understand. No passive voice. Use sentence fragments. Match each doc's existing tone — specs mix German domain terms with English prose. Keep German domain terms (Firma, Person, Chance, …).
FILE PATH DISPLAY RULE
Show full absolute paths. Get the root with pwd and prepend it. This lets users Command-click paths in the terminal.
HOW TO ASK THE USER FOR DECISIONS
Use the ask-user tool (AskUserQuestion / ask_user) for every prompt. Never print a question as prose and wait. Never read stdin. Embedded mode never prompts — see PHASE 0.
Preserve Human-Authored Content
Specs and agents are hand-written. Update only the facts the code changes made stale. Keep manual sections, domain language, and structure. Never replace careful prose with generic phrasing. Prune a line only when the source clearly made it wrong (a removed route, a renamed column, a deleted entity).
Create & Delete Docs
Default: update an existing file. Create or delete only when the code leaves no honest alternative.
Create a spec when a code area exists but no spec file covers it. Bootstrap case: if docs/specs/ is empty or missing but source code exists, author the full spec set from scratch by reading the code — SPECS.md (the index), DOMAIN.md, and one SPECS-*.md per area the code has. Use the same file names this skill already expects (Step 3.1).
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.
- 9d ago First seen · 413 lines · 68 tokens per session scan A 14bf83f8412d
update-agent-files is a skill published in the GitHub repository atra-consulting/coding-with-ai-lab (5 stars, last pushed 8d ago), licensed MIT. It adds 68 tokens to every session and 5,757 once invoked, about $0.0003 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-10-21.
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…