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 commands/evol-ai/skillcompass/post-install-onboardinggit clone --depth 1 https://github.com/Evol-ai/SkillCompassWrote 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/commands/evol-ai/skillcompass/post-install-onboarding)<a href="https://agentmods.dev/commands/evol-ai/skillcompass/post-install-onboarding"><img src="https://agentmods.dev/badge/commands/evol-ai/skillcompass/post-install-onboarding.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.00000 | $0.00674 |
| Opus 5 | $0.00000 | $0.00337 |
| Sonnet 5 | $0.00000 | $0.00135 |
| Haiku 4.5 | $0.00000 | $0.00067 |
Grade B, and why
post-install-onboarding scanned grade B with 1 finding 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 4d 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.
Check whether `~/.claude/settings.json` already has a `statusLine` configured. How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Post-Install Onboarding
Triggered by the SessionStart hook (hooks/scripts/session-tracker.js), which compares the current SkillCompass version against the last recorded version. On first install, reinstall, or version change the hook injects a context message instructing Claude to load this file and follow it on the user's first interaction.
Do not wait for a slash command. Execute the steps below in order as soon as the session starts.
Step 1: Introduce
🧭 SkillCompass
Evaluate skill quality, find the weakest area, and improve it.
Also tracks usage to help you spot idle or risky skills.
Step 2: Quick Scan (automatic, no permission needed)
Silently run skill discovery — scan immediate children */SKILL.md in each skill root (same as /setup Step 3; do NOT recurse) — and run a D1+D2+D3 quick scan on every discovered skill. Save the results to .skill-compass/setup-state.json. Then show one of the two result summaries below.
If any risks found:
Scanning installed skills...
Found {N} skill(s){, including M collections if any}.
{K} have security or structural risks; the rest passed the quick scan ✓
[View risky skills / Continue]
If all clean:
Scanning installed skills...
Found {N} skill(s){, including M collections if any}, all passed the quick scan ✓
[Continue]
Step 3: StatusLine Configuration
Check whether ~/.claude/settings.json already has a statusLine configured.
If NO existing statusLine:
SkillCompass tracks skill usage automatically.
When suggestions exist, the status line shows 🧭 N pending — type /skillcompass to view.
[Enable status line 🧭 / Skip]
If the user chooses Enable, offer two modes:
[Minimal — just the 🧭 hint / Full HUD — model, context, and more]
- Minimal: write the statusLine config to
~/.claude/settings.jsonpointing toscripts/hud-extra.js. - Full HUD: check for claude-hud; if present, configure its
--extra-cmd; otherwise fall back to Minimal. - Skip: do nothing.
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.
- 4d ago First seen · 84 lines · 0 tokens per session scan B aa19d76bafa2
post-install-onboarding is a command published in the GitHub repository Evol-ai/SkillCompass (215 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 674 tokens. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
audit_docs
Audit all project metadata files for stale counts, version mismatches, broken references, and missing entries. Reports discrepancies without auto-fixing.
merge_session
Merge session branch(es) into main via rebase + fast-forward push. Use from inside a session worktree pane to land your work, or with --all to batch merge all sessions from the main repo.
submit_to_list
Fork an external GitHub repo, add an entry to a curated list (e.g. awesome-), and open a PR — all via gh CLI.
cherry_pick_pr
Cherry-pick one or more commits onto a new branch from main and open a PR. Useful when a commit landed on the wrong branch or you want to split a multi-commit branch into separate PRs.
cti-report
Render case deliverables — relationship graph (PNG/SVG/Mermaid) and a polished PDF/DOCX assessment. Usage: /cti-report [--graph|--pdf].
sync_artifacts
Stage, commit, and push changes in the swarm-artifacts repo. Handles pre-commit validation and Co-Authored-By automatically.