// Keeps README badge + inline counts in sync with the real number of skills, agents, graph nodes/edges, communities, converted pipelines, and pytest tests. Runs automatically on every commit via a git pre-commit hook. Use when the README drifts from reality or before publishing a release.
Repo-aware recommendation manager for ctx. Scans the active repository, identifies stack and workflow signals, recommends a capped set of skills, agents, and MCP servers, and unloads helpers that no longer match the current work after user confirmation. Harnesses are recommended by the custom-model onboarding flow and then attach to the same recommendation layer.
Design or audit a repo-local markdown knowledge graph with wiki links, source-code backlinks, drift checks, and searchable sections. Use when AGENTS.md/CLAUDE.md is too flat for a large codebase or when a custom harness needs durable structured project memory.
Create or review an AGENTS.md file so coding agents get stable repo-local instructions: environment setup, testing, style, security boundaries, PR policy, and handoff rules. Use when a repo lacks durable agent guidance or when a custom harness needs a predictable context file.
Pre/post dev toolbox — named bundles of skills/agents loaded before development work and councils of experts invoked after. Run /toolbox or the toolbox.py CLI to list, activate, initialize, export, import, and validate toolboxes. Invoke at the start or end of a dev session, when setting up a new repo, or when sharing toolboxes with a team.
Discover installable agent skills from ctx's shipped Skills.sh catalog, the Skills.sh search API, and the npx skills CLI. Use when a user asks whether a skill exists, wants to add/update a skill, or needs a repeatable procedure for finding candidate skills safely.
Alive skill router — reads the current project's stack and loads/unloads skills dynamically. Invoke at session start or when project context changes.
| name | repo-stats-autoupdate |
| description | Keeps README badge + inline counts in sync with the real number of skills, agents, graph nodes/edges, communities, converted pipelines, and pytest tests. Runs automatically on every commit via a git pre-commit hook. Use when the README drifts from reality or before publishing a release. |
| type | maintenance |
| priority | 30 |
| always_load | false |
Reads the authoritative sources for the ctx repo's key numbers and patches README.md in place so badges and inline counts never drift:
| Number | Source of truth |
|---|---|
| Skills | ~/.claude/skill-wiki/graphify-out/graph.json — count nodes where type == "skill" |
| Agents | same file — count nodes where type == "agent" |
| Graph nodes | len(graph["nodes"]) |
| Graph edges | len(graph["edges"]), formatted as 642K / 1.2M |
| Communities | graph/communities.json → total_communities |
| Converted pipelines | ~/.claude/skill-wiki/converted/ subdir count |
| Tests | pytest --collect-only -q from src/ |
Fields that can't be resolved (e.g. wiki not deployed) are left untouched — the updater never blocks a commit.
One-time install (per clone):
git config core.hooksPath .githooks
After that, every git commit runs .githooks/pre-commit which calls the updater and re-stages README.md if any number drifted.
Manual run:
python src/update_repo_stats.py # patch README
python src/update_repo_stats.py --check # exit 1 if stale (for CI)
graph/wiki-graph.tar.gz takes minutes and churns a large artifact — too heavy for per-commit. Run ctx-wiki-graphify, then python src/validate_graph_artifacts.py --deep, and repack the tarball manually when the skill catalog changes materially.graphify-out/graph.json is corrupt, you'll get junk numbers. Run the wiki health check (python src/wiki_orchestrator.py --check) separately.README.md — the target being kept in sync