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/daaain/claude-code-log/update-tools-coveragenpx skills add daaain/claude-code-log --skill update-tools-coveragegit clone --depth 1 https://github.com/daaain/claude-code-logWhat 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.00059 | $0.01333 |
| Opus 5 | $0.00030 | $0.00666 |
| Sonnet 5 | $0.00012 | $0.00267 |
| Haiku 4.5 | $0.00006 | $0.00133 |
Grade A, and why
update-tools-coverage 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 2d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Tool Coverage
Keeps dev-docs/tools-coverage.md in
sync with the upstream contracts and our implementation:
- Upstream — the documented tool list at https://code.claude.com/docs/en/tools-reference.
- Us —
TOOL_INPUT_MODELS/TOOL_OUTPUT_PARSERSinclaude_code_log/factories/tool_factory.py. - Codex — the installed version's generated app-server
ThreadItemschema, plus the rollout adapters inproviders/codex.py,providers/codex_tools.py, andproviders/codex_javascript.py.
The doc grades each documented tool Full (typed input + typed output),
Input only (typed input, generic output), or Generic (no registry
entry → params-table + raw-<pre> fallback), and separately lists tools we
support that upstream no longer documents (renames like Task→Agent,
supersessions like MultiEdit, legacy aliases, undocumented features).
Claude Code procedure
-
Fetch the upstream tool names. WebFetch the reference and ask only for the tool-table names (the page is ~80 KB; a targeted prompt keeps it manageable):
WebFetch
https://code.claude.com/docs/en/tools-reference— "List the exact tool names in the main tools table, one per line. Names only, no descriptions."Note any tool the page marks deprecated/renamed — that's a candidate for the second table.
-
Compute the truth mechanically. Feed those names to the bundled helper (run from the repo root;
uv runis required sopydanticresolves — barepython3fails withModuleNotFoundError: pydantic):printf 'Agent Artifact AskUserQuestion ... Write' \ | uv run python .claude/skills/update-tools-coverage/check_coverage.pyIt prints each tool's support level, the totals, the "we register but upstream doesn't document" set, and — if the doc exists — a drift report (missing / mismatched / stale rows). If it says
in sync [OK]and the upstream name set is unchanged, there is nothing to do.
What ships with it
2 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.
- 2d ago First seen · 115 lines · 59 tokens per session scan A 05cf29db482b
update-tools-coverage is a skill published in the GitHub repository daaain/claude-code-log (1,201 stars, last pushed 2d ago), licensed MIT. It adds 59 tokens to every session and 1,333 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-30.
Other skills, from other repositories
mcporter
List, auth, and call MCP servers/tools from the terminal.
agent-messaging
Send and receive cryptographically signed messages between AI agents using the Agent Messaging Protocol (AMP). Use when the user asks to "send a message to an agent", "check agent inbox", "message another agent", "reply to a message", "notify an agent", or any inter-agent communication task.
📝 任务完成后归档
重要提醒: 每次完成复杂调试或开发任务后，主动执行此流程！ 将学到的经验归档为 skill，供以后参考。不要等用户提醒。.
oracle
Best practices for using the oracle CLI (prompt + file bundling, engines, sessions, and file attachment patterns).
agent-mode
Unified tool for managing agent LLM modes (add, remove, update, list, switch).
agento11y-prod-setup
Sets up production evaluation and guardrails for a DEPLOYED AI agent in Grafana Agent Observability, grounded in the agent's own code and its real ingested traffic. The judgment layer on top of the agento11y skill: it reads the agent's source (system prompt, tools, entrypoint) AND samples its live traffic via gcx…