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 report-feature-changesgit 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/report-feature-changes)<a href="https://agentmods.dev/skills/fabis94/universal-ai-config/report-feature-changes"><img src="https://agentmods.dev/badge/skills/fabis94/universal-ai-config/report-feature-changes/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/report-feature-changes"><img src="https://agentmods.dev/badge/skills/fabis94/universal-ai-config/report-feature-changes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00064 | $0.01661 |
| Opus 5 | $0.00032 | $0.00830 |
| Sonnet 5 | $0.00013 | $0.00332 |
| Haiku 4.5 | $0.00006 | $0.00166 |
Grade A, and why
report-feature-changes 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 8d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Report Feature Changes
Compare uac's implementation against the latest upstream documentation for each supported AI tool. Produce a structured report of out-of-date assumptions so the user can decide what to change.
This skill does not modify uac source files. It only produces a report. Any code/doc changes are a follow-up step.
Inputs
Parse $ARGUMENTS:
--tool <name>— restrict to one tool (claude,copilot,cursor). Defaults to all supported tools.--feature <category>— restrict to one Part 1 feature category from the reference (e.g.hooks,mcp,frontmatter,tools). Defaults to all categories.
If no arguments are provided, ask the user with AskUserQuestion whether they want to validate everything (slow, thorough) or scope down to a single tool/feature first.
Step 1: Load the Validation Reference
Read upstream-validation-reference.md — the companion file in this skill directory. It defines:
- Part 1 — the feature categories to validate (file locations, frontmatter, hooks, tools, MCP, permissions, models, etc.) and where each is implemented in uac (
src/targets/<tool>/index.ts, etc.). - Part 2 — per-tool documentation URLs grouped by tier. Tier 1 is authoritative (vendor reference docs). Tier 2 is for dating changes (changelogs). Tier 3 is community/supporting evidence only.
- Part 5 — known documentation quality caveats (beta-API churn, in-product-only docs, vendor terminology drift, multiple doc surfaces).
Treat this reference as the source of truth for what to check and where to look. Do not invent new URLs — if a needed doc page is missing from the reference, note it as a gap in the final report.
Step 2: Snapshot uac's Current Assumptions
Before fetching any docs, read uac's current implementation for each tool in scope so you have a concrete baseline to compare against. For each tool:
src/targets/<tool>/index.ts—outputDir,supportedTypes,frontmatterMapfor each template type,EVENT_NAME_MAP,transform*Hooks(),transform*MCP().src/types.ts—UniversalFrontmatter,UniversalHookHandler,UniversalMCPServer,UniversalMCPInput,TemplateTypeunion.src/seed-types/meta-instructions/templates/instructions/uac-template-guide.md— documentation claims (frontmatter field tables, hook event mapping table, tools tables). Drift here is a finding too.src/core/writer.ts—CLEAN_PATHS,CLEAN_MCP_PATHS.
What ships with it
1 file 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.
- 8d ago First seen · 132 lines · 64 tokens per session scan A aa184712de78
report-feature-changes is a skill published in the GitHub repository fabis94/universal-ai-config (11 stars, last pushed 12d ago), licensed MIT. It adds 64 tokens to every session and 1,661 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
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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…