Borrowing it
Nothing to install: this file belongs to PackmindHub/skillsight. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/PackmindHub/skillsight/main/.claude/skills/packmind-onboard/SKILL.mdgit clone --depth 1 https://github.com/PackmindHub/skillsightWrote 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/packmindhub/skillsight/packmind-onboard)<a href="https://agentmods.dev/skills/packmindhub/skillsight/packmind-onboard"><img src="https://agentmods.dev/badge/skills/packmindhub/skillsight/packmind-onboard.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.00038 | $0.02203 |
| Opus 5 | $0.00019 | $0.01102 |
| Sonnet 5 | $0.00008 | $0.00441 |
| Haiku 4.5 | $0.00004 | $0.00220 |
Grade A, and why
packmind-onboard 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 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.
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.
This is a copy
98% identical to packmind-onboard — 13 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 329 lines — stays where its author put it; the contents beside it link to each section on GitHub.
packmind-onboard
Run "packmind-cli --version" to get the current cli installation.
Find the highest version at or below the cli version in this list:
- 0.16.0
- 0.23.0 Remember this value as $PACKMIND_CLI_VERSION for the rest of the skill.
Action skill. Provides complete automated onboarding for Packmind:
- Creates or selects a package
- Analyzes codebase for patterns
- Generates draft Standards and Commands
- Creates items via CLI
Automatic package creation when none exist, user selection when packages are available.
Guarantees
- Read-only analysis. Analysis phase does not modify any project files.
- Drafts before creation. All items are written as drafts first, allowing review before creation.
- Preserve existing. Never overwrite existing artifacts. If a slug already exists, create
-2,-3, etc. - Evidence required. Every reported insight must include file-path evidence (and line ranges when feasible).
- Focused output. Max 5 Standards and 5 Commands generated per run.
- Graceful failure. Partial failures don't lose successful work; failed drafts are preserved.
- User control. When packages exist, users confirm package selection before creation.
Definitions
- Pattern (non-linter): a convention a linter cannot reliably enforce (module boundaries, cross-domain communication, workflow parity, error semantics, etc).
- Evidence:
path[:line-line]entries; omit line ranges only when the file isn't text-searchable.
Step 0 — Introduction
Print exactly:
I'll start the Packmind onboarding process. I'll create your first standards and commands and send them to your Packmind organization. This usually takes ~3 minutes.
Step 1 — Get Repository Name
Get the repository name for package naming:
basename "$(git rev-parse --show-toplevel)"
Remember this as the repository name for package creation in Step 2.
Also run packmind-cli whoami and extract the Host: value from the output. Remember this URL for the completion summary.
What ships with it
16 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- LICENSE.txt 9.9 KB
- packmind-versions/0.16.0/completion-summary.md 2.1 KB
- packmind-versions/0.16.0/create-items.md 5.4 KB
- packmind-versions/0.16.0/create-package.md 90 B
- packmind-versions/0.16.0/list-packages.md 71 B
- packmind-versions/0.16.0/select-package.md 146 B
- packmind-versions/0.23.0/completion-summary.md 2.5 KB
- packmind-versions/0.23.0/create-items.md 4.2 KB
- packmind-versions/0.23.0/create-package.md 406 B
- packmind-versions/0.23.0/list-packages.md 70 B
- packmind-versions/0.23.0/select-package.md 363 B
- README.md 1.6 KB
- references/ci-local-workflow-parity.md 3.7 KB
- references/file-template-consistency.md 3.1 KB
- references/role-taxonomy-drift.md 4.3 KB
- references/test-data-construction.md 2.4 KB
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 · 329 lines · 38 tokens per session scan A 2a64854151dd
packmind-onboard is a skill published in the GitHub repository PackmindHub/skillsight (9 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 38 tokens to every session and 2,203 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to packmind-onboard, differing in 13 lines, and is treated as a copy.
Other skills, from other repositories
repo-hygiene
Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
chinese-documentation
A Chinese technical-documentation style guide covering spacing, punctuation, numbers, terminology, and links when Chinese and English appear together.
build-teaql-app
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…
find-simplifications
Use for a periodic repo-wide sweep of qwen-code for accumulated excess surface — dead components and files, orphaned locale keys, exports nothing consumes, added-then-removed scaffolding — filing candidates on a tracking issue and landing only what a maintainer has said yes to. Repo-wide and evidence-first; every…
workflow-start
Primary entry point for the spec-superflow state-machine workflow. Invoke when the user is inside an active spec-superflow change directory (look for .spec-superflow.yaml, changes/ /, proposal.md, specs/, design.md, tasks.md, or execution-contract.md) and asks to start, continue, resume, implement, plan, or figure out…