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/nirecom/agents/update-infrastructurenpx skills add nirecom/agents --skill update-infrastructuregit clone --depth 1 https://github.com/nirecom/agentsWrote 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/nirecom/agents/update-infrastructure)<a href="https://agentmods.dev/skills/nirecom/agents/update-infrastructure"><img src="https://agentmods.dev/badge/skills/nirecom/agents/update-infrastructure.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 | $0.00016 | $0.00558 |
| Opus 5 | $0.00008 | $0.00279 |
| Sonnet 5 | $0.00003 | $0.00112 |
| Haiku 4.5 | $0.00002 | $0.00056 |
Grade A, and why
update-infrastructure 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update infrastructure.md to reflect infrastructure changes across all stacks and hosts
Target files
-
infrastructure.mdpath: read from the project'sCLAUDE.local.mdbefore proceeding. (The path is not stored here because this skill lives in a public repo.) -
Source repos (for detecting changes):
- langchain-stack:
../langchain-stack/→[email protected]:nirecom/langchain-stack.git - open-webui-stack:
../open-webui-stack/→[email protected]:nirecom/open-webui-stack.git - portable-llm-server:
../portable-llm-server/→[email protected]:nirecom/portable-llm-server.git
- langchain-stack:
-
Related design docs (already-documented changes to reflect):
langchain/architecture.md(subdirectory of infrastructure.md's directory)langchain/ops.md(subdirectory of infrastructure.md's directory)
Procedure
UI-1. Gather recent changes: For each source repo, run git log --oneline -20. Also check langchain/architecture.md and langchain/ops.md for recently documented changes not yet in infrastructure.md
UI-2. Read current infrastructure.md: Understand what is already documented
UI-3. Identify gaps: Compare against infrastructure.md. Look for:
- Host service changes (Windows host services, Mac services, QNAP docker-stacks)
- Stack additions or removals
- Port allocation changes
- Connection topology changes
- Docker network changes
- Hardware or network equipment changes UI-4. Propose updates: Present a summary of proposed changes to the user:
- Which sections need updating and why
- Specific additions or modifications UI-5. Apply after confirmation: Edit the file only after user approval
Rules
- Language: Japanese/English mixed (match existing style per section)
- infrastructure.md is pasted into a Claude.ai web project — keep it concise (~200 lines)
- Show structure only — do not add operational procedures (those belong in
langchain/ops.md) - Do not duplicate design details — reference
langchain/architecture.mdinstead - Do not add phase progress — reference
langchain/progress.mdinstead - The "Coding Guidelines" and "Agent Context File Conventions" sections are maintained separately; do not modify unless explicitly requested
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 · 49 lines · 16 tokens per session scan A dd61f4f69ad4
update-infrastructure is a skill published in the GitHub repository nirecom/agents (3 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 558 once invoked, about $0.0001 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-03.
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…
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…