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/mr-devs/cc-academic-website/update-site-datanpx skills add mr-devs/cc-academic-website --skill update-site-datagit clone --depth 1 https://github.com/mr-devs/cc-academic-websiteWrote 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/mr-devs/cc-academic-website/update-site-data)<a href="https://agentmods.dev/skills/mr-devs/cc-academic-website/update-site-data"><img src="https://agentmods.dev/badge/skills/mr-devs/cc-academic-website/update-site-data.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.00075 | $0.00722 |
| Opus 5 | $0.00037 | $0.00361 |
| Sonnet 5 | $0.00015 | $0.00144 |
| Haiku 4.5 | $0.00007 | $0.00072 |
Grade A, and why
update-site-data 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 5d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Site Data
Manage all website content updates. Every page section is rendered from a JSON file under data/; this skill routes any content change to the right file and workflow.
Input
$ARGUMENTS
If no input is provided or the content type is unclear, ask the user (with AskUserQuestion) which kind of update this is before proceeding.
Ground truth: the code, not this skill
This site may have been redesigned since this skill was written. Before any edit:
- Read the target
data/*.jsonfile to see the schema actually in use. - If a field's purpose is unclear, read the JS module that renders it (find it by grepping
js/for the data filename or container id). - references/schemas.md documents the schemas as last recorded — if the live data/renderer has diverged from it, trust the code, follow the live schema, and offer to update schemas.md to match.
Routing
| Request | Action |
|---|---|
| New preprint / working paper | Follow references/add-working-paper.md |
| Working paper got published | Follow references/convert-to-published.md |
| News item / announcement | Follow references/add-news-item.md |
| Talk, software, ongoing project, teaching entry, profile/bio change, or a direct edit (fixing a typo, updating a URL) | Handle inline — see below |
Read the routed reference file before acting; do not work from memory of its contents.
Inline workflow (simple files and direct edits)
- Read the relevant schema and example in references/schemas.md.
- Read the target
data/*.jsonfile (this is the ground truth — see above). - Gather any missing required fields from the user (AskUserQuestion for structured choices, plain questions otherwise).
- Draft the entry and show it to the user for approval before writing.
- Insert newest-first (top of the array, or top of the matching year group) unless the file is ordered otherwise.
- Write the file.
What ships with it
4 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.
- 5d ago First seen · 57 lines · 75 tokens per session scan A ca3e091e0757
update-site-data is a skill published in the GitHub repository mr-devs/cc-academic-website (5 stars, last pushed 24d ago), licensed MIT. It adds 75 tokens to every session and 722 once invoked, about $0.0004 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…
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…