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 DorianSchlede/nexus-template --skill maintaingit clone --depth 1 https://github.com/DorianSchlede/nexus-templateWrote 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/dorianschlede/nexus-template/maintain)<a href="https://agentmods.dev/skills/dorianschlede/nexus-template/maintain"><img src="https://agentmods.dev/badge/skills/dorianschlede/nexus-template/maintain/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/dorianschlede/nexus-template/maintain"><img src="https://agentmods.dev/badge/skills/dorianschlede/nexus-template/maintain.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.00000 | $0.00964 |
| Opus 5 | $0.00000 | $0.00482 |
| Sonnet 5 | $0.00000 | $0.00193 |
| Haiku 4.5 | $0.00000 | $0.00096 |
Grade D, and why
maintain scanned grade D with 2 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
1. Clean old sessions: `find .claude/sessions -mtime +7 -delete` Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
2. Clean Python cache: `find . -type d -name __pycache__ -exec rm -rf {} +` How it starts
The opening of the file, as written. The whole thing — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/maintain - Nexus Codebase Maintenance
Overview
Validates maintenance operations, runs health checks, and helps keep the Nexus codebase clean and up-to-date. Combines deterministic maintenance scripts with intelligent analysis.
Arguments
--interactiveor-i: Enable human-in-the-loop mode for guided maintenance
Workflow
Step 1: Check for Interactive Mode
IF arguments contain "--interactive" or "-i":
→ Execute interactive maintenance workflow (see below)
→ STOP here, do not continue to Step 2
Step 2: Read Maintenance Log
Read the maintenance log to understand what the maintenance hook did:
File: .claude/logs/maintenance.log
If the log doesn't exist, inform the user they should run just maintenance or claude --maintenance first.
Step 3: Additional Health Checks
Run checks beyond what the deterministic script does:
Git Status:
- Any uncommitted changes?
- Is the branch up to date with remote?
- Any stale branches to clean up?
Dependency Health:
- Are there any security vulnerabilities in dependencies?
- Are major version updates available?
Nexus-Specific:
- Any orphaned build directories?
- Is user-config.yaml valid?
- Are there stale session files?
Disk Usage:
- How much space is the .claude directory using?
- Are there large files that shouldn't be tracked?
Step 4: Generate Report
Create a summary document at .claude/logs/maintenance-report.md:
# Nexus Maintenance Report
Generated: [timestamp]
## Status: [HEALTHY | NEEDS_ATTENTION | ACTION_REQUIRED]
## Deterministic Checks (from script)
[Summarize what the maintenance script found]
## AI-Powered Analysis
[Additional findings from intelligent checks]
## Recommendations
[Prioritized list of actions]
## Metrics
- Total disk usage: X MB
- Session files: X (X old)
- Uncommitted changes: X files
Step 5: Report to User
Display maintenance status:
- If healthy: Confirm everything looks good
- If issues found: Explain each and offer to help fix
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 · 156 lines · 0 tokens per session scan D 66779b3a19cd
maintain is a skill published in the GitHub repository DorianSchlede/nexus-template (8 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 964 tokens. A static security scan graded it D with 2 findings (reads agent configuration directories, recursive force delete). 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…
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…