Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/joris887/exosuitnpx agentmods add skills/joris887/exosuit/weekly-maintenanceWrote 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/joris887/exosuit/weekly-maintenance)<a href="https://agentmods.dev/skills/joris887/exosuit/weekly-maintenance"><img src="https://agentmods.dev/badge/skills/joris887/exosuit/weekly-maintenance.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.1 | $0.00034 | $0.02762 |
| Opus 5 | $0.00017 | $0.01381 |
| Sonnet 5 | $0.00007 | $0.00552 |
| Haiku 4.5 | $0.00003 | $0.00276 |
Grade A, and why
weekly-maintenance 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 7d 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 — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
weekly-maintenance
Execute comprehensive weekly maintenance routine (1-2 hours, Friday recommended):
1. Codebase Health Check
Run the project's quality/health tools (from CLAUDE.md Commands section):
# Use project-specific commands, e.g.:
# just health, npm run lint, cargo clippy, etc.
Report on:
- Complexity trends (should be stable or decreasing)
- Duplication percentage (target: <5%)
- High-churn files that may need attention
- Dead code: unused exports, orphaned functions (run monthly or when codebase > 5K LOC)
2. Code Quality Agent Review
Use the code-quality skill to analyze the entire codebase:
- Flag any functions with CCN >10
- Identify duplication patterns
- Check for pattern consistency violations
3. Documentation Review
Check key documentation for accuracy:
- @CLAUDE.md accuracy (commands, paths, patterns still correct?)
- @docs/progress.md completeness
- Any drift between docs and implementation
- Documentation efficiency: Key context files (CLAUDE.md, progress.md, BACKLOG_INDEX.md) are loaded every session — keep them lean. Archive stale content, deduplicate, condense verbose sections.
- Metrics freshness: If
docs/progress.md→## Sprint Historyhas ≥2 data rows but## Metricstable still shows "—" values, sprint-end is not computing metrics — flag as a measurement gap. The feedback loop is broken: data collected but not surfaced.
4. Dependency Review
Check for outdated dependencies using the project's package manager:
# npm outdated, pip list --outdated, cargo outdated, etc.
Dependency Health Check
Run dependency auditing tools:
# npm audit / pip-audit / cargo audit / bundler-audit
Flag and report:
- Recently added packages (added since last maintenance) — verify they exist in the registry and are well-established
- Young packages (< 7 days old) — flag as supply chain risk
- Known vulnerabilities — categorize by severity
- Lockfile sync — verify lockfile matches dependency manifest
- Recently deprecated packages — check for deprecation notices
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.
- 7d ago First seen · 263 lines · 34 tokens per session scan A 045fa52ef0d2
weekly-maintenance is a skill published in the GitHub repository joris887/exosuit (4 stars, last pushed 17d ago), licensed MIT. It adds 34 tokens to every session and 2,762 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-31.
Other skills, from other repositories
issue-triage
3-phase issue backlog management with audit, deep analysis, and validated triage actions. Use when triaging GitHub issues, sorting bug reports, cleaning up stale tickets, or detecting duplicate issues. Args: 'all' to analyze all, issue numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit only.
orchestrator-lanes
A file-based project-management playbook for a specific Claude Code development orchestrator. It organizes work into lanes, plans, dependency steps, validation phases, and shipping stages.
project-life
A system for keeping project ideas, tasks, plans, progress, decisions, and lessons in one place. A monorepo-style project workflow is implied, but the input does not define the storage format in full.
lane-contract
A file-based task contract system for describing coding tasks in YAML, including which files a task owns and how it must be checked.
plan-pipeline
Orchestrates the complete planning pipeline: product direction (ceo-review) -> architecture (eng-review) -> implementation plan (start) -> validation (validate) -> execution (execute). Run stages individually or let the orchestrator coordinate the full flow.
seo-project-life
A guide to the files, commands, stages, and working process of an SEO project. SEO, or search-engine optimization, is the work of improving a site's visibility in search results.