Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/mojoapp-ai/agent-skills/nextra-update)<a href="https://agentmods.dev/skills/mojoapp-ai/agent-skills/nextra-update"><img src="https://agentmods.dev/badge/skills/mojoapp-ai/agent-skills/nextra-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/mojoapp-ai/agent-skills/nextra-update"><img src="https://agentmods.dev/badge/skills/mojoapp-ai/agent-skills/nextra-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.00081 | $0.01205 |
| Opus 5 | $0.00041 | $0.00602 |
| Sonnet 5 | $0.00016 | $0.00241 |
| Haiku 4.5 | $0.00008 | $0.00120 |
Grade A, and why
nextra-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 9d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
nextra-update
Mirror the user-facing docs from the mojo-apps repo's nextra/content/ into this repo's skills/mojo-app-docs/references/, so the bundled skill reflects what docs.mojoapp.ai is currently publishing.
Prerequisites
- You are at the repo root:
agent-skills/withskills/mojo-app-docs/references/visible. - The mojo-apps repo is checked out locally. By default it's expected at
/Users/Hana/Agents/mojo/repos/mojo-apps. Override withMOJO_APPS_PATH=/some/other/pathif needed. - Working tree of
agent-skillsis clean.
If anything's missing, stop and tell the user.
Step 1 — Make sure mojo-apps is up to date
MOJO_APPS="${MOJO_APPS_PATH:-/Users/Hana/Agents/mojo/repos/mojo-apps}"
NEXTRA="$MOJO_APPS/nextra/content"
if [ ! -d "$NEXTRA" ]; then
echo "ERROR: $NEXTRA does not exist. Set MOJO_APPS_PATH or clone mojo-apps."
exit 1
fi
# Bring nextra/content to the tip of its branch
git -C "$MOJO_APPS" fetch
git -C "$MOJO_APPS" status --short
If the mojo-apps working tree is dirty, ask the user whether they want to:
(a) sync from whatever's on disk right now (use as-is),
(b) git stash + git pull first, then sync from the freshly-pulled state.
Don't decide for them — local dirty trees often have in-progress edits.
Step 2 — Record the source SHA (for the commit message)
NEXTRA_SHA=$(git -C "$MOJO_APPS" rev-parse --short HEAD)
echo "Source SHA: $NEXTRA_SHA"
Step 3 — Mirror with rsync
TARGET="$(git rev-parse --show-toplevel)/skills/mojo-app-docs/references"
rsync -av --delete \
"$NEXTRA/" \
"$TARGET/"
Notes on the flags:
--deleteremoves files in$TARGETthat no longer exist in$NEXTRA. This is what you want — the references should be an exact mirror, not an accumulation.- The trailing slash on
$NEXTRA/matters. With it, rsync copies the contents into$TARGET/. Without it, rsync creates$TARGET/content/.
Step 4 — Diff preview
cd "$(git rev-parse --show-toplevel)"
git status --short skills/mojo-app-docs/references
git diff --stat skills/mojo-app-docs/references | tail -20
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.
- 9d ago First seen · 126 lines · 81 tokens per session scan A e658a55646cc
nextra-update is a skill published in the GitHub repository mojoapp-ai/agent-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 81 tokens to every session and 1,205 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
claude-md-improver
Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintenance" or "project…
agent-platform-rag-engine-management
Manage and query Agent Platform RAG Engine Corpora and retrieve grounded contexts using the Google GenAI SDK. Use when listing RAG corpora or files, inspecting a corpus, retrieving contexts, or generating content grounded in a RAG corpus. Do not use for standard database queries (use SQL/Spanner skills), Google…
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
agent-platform-model-registry
Agent Platform Model Registry Management. Use when you need to upload, list, describe, update, or delete machine learning models (and their versions) in the Agent Platform Model Registry. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform models.
google-cloud-solution-agentic-analytics-spark-knowledge-catalog
Discovers requirements and generates guidance to design and deploy a governed, secure agentic-analytics solution for data that's distributed across Google Cloud, other cloud providers, or on-premises. Data that's outside Google Cloud (such as data from Databricks, Snowflake, Salesforce, SAP, or Oracle systems) is…