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 HiAgencia/hi-claude --skill updategit clone --depth 1 https://github.com/HiAgencia/hi-claudeWrote 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/hiagencia/hi-claude/update)<a href="https://agentmods.dev/skills/hiagencia/hi-claude/update"><img src="https://agentmods.dev/badge/skills/hiagencia/hi-claude/update/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/hiagencia/hi-claude/update"><img src="https://agentmods.dev/badge/skills/hiagencia/hi-claude/update.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.00151 | $0.01634 |
| Opus 5 | $0.00076 | $0.00817 |
| Sonnet 5 | $0.00030 | $0.00327 |
| Haiku 4.5 | $0.00015 | $0.00163 |
Grade A, and why
update 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 10d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What the plugin offers now, and what this project should do about it
This is not a changelog and it is not an audit. A changelog says what changed and leaves the reading to you; an audit asks whether everything is healthy. This asks ONE question: of what the plugin offers, what is this project not using yet — and does it pay here?
A project can be perfectly healthy and still be missing every capability listed below. That gap is invisible to every other check, because nothing else knows what the plugin gained.
How to run it
- Read the panorama below. It carries what a project may not be using yet, why each one pays, and how to measure it.
- Measure THIS project by EFFECT — count the characters, open the directory, run the command. Never one text against another, and never assume from the version number: a project may have adopted something by hand long before it shipped.
- Report only what applies, each with ITS NUMBER for this project. "Your open-work block is 11.755 characters and 4.000 arrive" moves someone; "consider using the horizon" does not. What is already adopted gets one line saying so, and nothing else.
- PROPOSE, never apply. Say what you would change, in which file, and what it buys. The user
decides. Anything touching CLAUDE.md or memory follows
hi-claude:memory-protocol, and anything touching the register followshi-claude:roadmap.
If nothing applies, say so in one line and stop. A skill that always finds something to do is one that gets run once.
The panorama
Rewritten at every release, never stacked. This is not a history: it is the state of what a project may still be missing. An item leaves when it stops being adoptable — because
setupgenerates it and no new project can lack it, or because the capability went away. Git keeps what leaves.Only what asks something OF THE PROJECT enters. A change that just works — a permission decided better, a demand scaled to the change, a consultation that stopped repeating — asks nothing and does not belong here. Without that filter this becomes the changelog it exists to replace.
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.
- 10d ago First seen · 105 lines · 151 tokens per session scan A b067afe55fac
update is a skill published in the GitHub repository HiAgencia/hi-claude (2 stars, last pushed 20d ago), licensed MIT. It adds 151 tokens to every session and 1,634 once invoked, about $0.0008 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…
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…
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…