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 skills/packmindhub/packmind/packmind-onboardnpx skills add PackmindHub/packmind --skill packmind-onboardgit clone --depth 1 https://github.com/PackmindHub/packmindWrote 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/packmind/packmind-onboard)<a href="https://agentmods.dev/skills/packmindhub/packmind/packmind-onboard"><img src="https://agentmods.dev/badge/skills/packmindhub/packmind/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 | $0.00038 | $0.02205 |
| Opus 5 | $0.00019 | $0.01103 |
| 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 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.
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.
Copies of this mod
2 near-identical copies found in the catalogue:
- packmind-onboard — 98% identical, 13 lines differ
- packmind-onboard — 98% identical, 13 lines differ
How it starts
The opening of the file, as written. The whole thing — 330 lines — stays where its author put it; the contents beside it link to each section on GitHub.
packmind-onboard
Run "packmind --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
- 0.35.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 whoami and extract the Host: value from the output. Remember this URL for the completion summary.
What ships with it
33 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
- packmind-versions/0.35.0/completion-summary.md 2.5 KB
- packmind-versions/0.35.0/create-items.md 4.1 KB
- packmind-versions/0.35.0/create-package.md 398 B
- packmind-versions/0.35.0/list-packages.md 66 B
- packmind-versions/0.35.0/select-package.md 359 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
- steps/edge-cases.md 667 B
- steps/step-0-introduction.md 218 B
- steps/step-1-get-repository-name.md 331 B
- steps/step-10-completion-summary.md 172 B
- steps/step-2-package-handling.md 1.8 KB
- steps/step-3-announce.md 128 B
- steps/step-4-detect-existing-config.md 809 B
- steps/step-5-detect-project-stack.md 730 B
- steps/step-6-run-analyses.md 783 B
- steps/step-7-generate-drafts.md 594 B
- steps/step-8-present-summary.md 973 B
- steps/step-9-create-items.md 153 B
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 · 330 lines · 38 tokens per session scan A da01f3bbe31c
packmind-onboard is a skill published in the GitHub repository PackmindHub/packmind (308 stars, last pushed today), licensed Apache-2.0. It adds 38 tokens to every session and 2,205 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-30.
Other skills, from other repositories
token-saver-config
Configure and diagnose token-saver compression settings. Use when the user asks about adjusting compression levels, checking processor status, debugging hook issues, or reviewing savings statistics.
sdd
Execute the Liatrio Spec-Driven Development (SDD) workflow when explicitly invoked by the user. NOTE: this skill is NOT intended to be dynamically loaded or automatically triggered; it should only ever be explicitly called by the user.
loadout-import-workflow
Import another repo's command/skill suite into loadout as a workflow. Use when the user points at an agent framework, plugin, or command pack (e.g. a GitHub repo, a .claude/commands/ directory, a skills pack) and wants its process turned into a loadout [[workflows]] entry — "import this workflow", "turn this plugin…
loadout-migrate
Migrate existing global AI agent instructions into loadout. Use when adopting loadout, importing a CLAUDE.md / AGENTS.md / global agent rules into loadout, setting up /.config/loadout/config.toml, or turning prose agent instructions into reusable fragments and stack-targeted profiles.
loadout-remember
Save a durable, cross-project user preference into loadout's global fragments/profiles — or update the fragment it contradicts. Use when the user states lasting guidance that should follow them across projects and agents ("always X", "never Y", "stop doing Z"), especially when it conflicts with guidance the loadout…
orchestrator
Use this skill when running as an ephemeral orchestrator subagent for a Taniwha project. The skill instructs the agent to read project state from disk, decide the single next action the dispatcher should take, write that decision back to disk, and exit. Trigger this whenever the dispatcher has invoked an orchestrator…