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 fabis94/universal-ai-config --skill update-ai-configgit clone --depth 1 https://github.com/fabis94/universal-ai-configWrote 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/fabis94/universal-ai-config/update-ai-config)<a href="https://agentmods.dev/skills/fabis94/universal-ai-config/update-ai-config"><img src="https://agentmods.dev/badge/skills/fabis94/universal-ai-config/update-ai-config/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/fabis94/universal-ai-config/update-ai-config"><img src="https://agentmods.dev/badge/skills/fabis94/universal-ai-config/update-ai-config.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.00030 | $0.01080 |
| Opus 5 | $0.00015 | $0.00540 |
| Sonnet 5 | $0.00006 | $0.00216 |
| Haiku 4.5 | $0.00003 | $0.00108 |
Grade A, and why
update-ai-config 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 11d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manage AI Config Templates
IMPORTANT: This project uses universal-ai-config (uac). All AI configuration lives in the <%= config.templatesDir %>/ directory as universal templates. NEVER edit generated target-specific files (e.g. .claude/, .github/copilot-instructions.md, .cursor/, .codex/, AGENTS.md at root, .agents/skills/) directly — those are overwritten on every uac generate run. Always modify the source templates in <%= config.templatesDir %>/.
When the user wants to add or change AI configuration for this project, follow these steps:
1. Understand the Request
Read the template guide at <%= instructionPath('uac-template-guide') %> to understand the available template types and when to use each.
2. Determine the Template Type
Based on the user's request, decide which type of template to work with:
- Persistent context, rules, or guidelines → Instruction template
- Repeatable task, workflow, or slash command → Skill template
- Specialized AI persona with restricted tools → Agent template
- Automatic lifecycle automation (on events) → Hook template
- MCP server configuration → MCP template
Examples:
- "Add a rule about error handling" → Instruction
- "Create a deploy workflow" → Skill
- "Set up a code reviewer" → Agent
- "Run linting after file edits" → Hook
- "Add an MCP server for GitHub" → MCP
If the intent is ambiguous, ask the user to clarify before proceeding.
3. Delegate
Read the detailed guide for the chosen template type and follow its instructions:
- Instructions →
<%= skillPath('update-instruction') %> - Skills →
<%= skillPath('update-skill') %> - Agents →
<%= skillPath('update-agent') %> - Hooks →
<%= skillPath('update-hook') %> - MCP →
<%= skillPath('update-mcp') %>
These skills primarily create or modify files inside <%= config.templatesDir %>/. They may also modify files in directories listed under additionalTemplateDirs in the config — but only with explicit user confirmation, since those are shared templates that may affect other projects. Never edit generated output files in .claude/, .cursor/, .github/, .codex/, AGENTS.md at root, .agents/skills/, or similar target-specific directories — those are regenerated from templates and any direct changes will be lost.
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.
- 11d ago First seen · 72 lines · 30 tokens per session scan A 3296fbac95fa
update-ai-config is a skill published in the GitHub repository fabis94/universal-ai-config (11 stars, last pushed 14d ago), licensed MIT. It adds 30 tokens to every session and 1,080 once invoked, about $0.0002 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
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…