Borrowing it
Nothing to install: this file belongs to PackmindHub/packmind. 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/packmind/main/.agents/skills/packmind-update-playbook/SKILL.mdgit 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-update-playbook)<a href="https://agentmods.dev/skills/packmindhub/packmind/packmind-update-playbook"><img src="https://agentmods.dev/badge/skills/packmindhub/packmind/packmind-update-playbook/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/packmindhub/packmind/packmind-update-playbook"><img src="https://agentmods.dev/badge/skills/packmindhub/packmind/packmind-update-playbook.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00181 | $0.01661 |
| Opus 5.5 | $0.00072 | $0.00664 |
| Sonnet 5.5 | $0.00036 | $0.00332 |
| Haiku 4.5 | $0.00018 | $0.00166 |
Grade A, and why
packmind-update-playbook 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 1mo 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-update-playbook — 97% identical, 7 lines differ
- packmind-update-playbook — 97% identical, 7 lines differ
How it starts
The opening of the file, as written. The whole thing — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Playbook
Run "packmind --version" to get the current cli installation.
Find the highest version at or below the cli version in this list:
- 0.21.0
- 0.23.0
- 0.35.0 Remember this value as $PACKMIND_CLI_VERSION for the rest of the skill.
Evaluate the user's intent against existing Packmind artifacts (standards, commands, skills) to identify what needs creating or updating. Produce a structured change report, then apply approved changes using the playbook CLI workflow.
⚠️ MANDATORY WORKFLOW — This skill defines a strict sequence: Understanding Your Request → Summarizing Changes → Analyzing Playbook → Change Report → Applying Changes. Do NOT skip steps or edit artifact files directly. Even for a single-line change, follow every step. The workflow ensures changes are reviewed, approved, submitted, and propagated correctly.
Understanding Your Request
STOP. This phase runs FIRST, before anything else. No file reads, no CLI commands, no subagents until this gate passes.
Analyze the user's input and conversation context to determine intent:
Case A: No prior conversation / empty input
The skill was invoked standalone with no context. Ask:
"What Packmind artifact do you want to modify? For example: a standard (coding rule/convention), a command (multi-step workflow), or a skill (specialized capability). Please describe what you'd like to change."
BLOCK — do not proceed until the user responds.
Case B: Explicit intent found
The user explicitly asked to update, add, fix, or change a Packmind artifact. Extract an intent summary:
- Target artifact(s): which standard(s), command(s), or skill(s) to modify (or "new")
- Kind of change: create or update
- Specifics: any details the user provided about the change
Proceed to Summarizing Changes with this validated intent.
Case C: Opportunity detected from conversation
The conversation reveals a playbook update opportunity — e.g., a convention was established, a pattern emerged, a workflow was changed, or a known artifact is now stale — but the user did not explicitly ask for a playbook update. Summarize the opportunity and ask:
What ships with it
11 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.21.0/apply-changes.md 3.7 KB
- packmind-versions/0.23.0/apply-changes.md 5.9 KB
- packmind-versions/0.35.0/apply-changes.md 5.9 KB
- references/agent-skills-specification.md 7.3 KB
- references/create-command-procedure.md 3.7 KB
- references/create-skill-procedure.md 4.7 KB
- references/create-standard-procedure.md 2.7 KB
- steps/analyze-commands.md 2.4 KB
- steps/analyze-skills.md 4.2 KB
- steps/analyze-standards.md 3.2 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.
- 1mo ago First seen · 145 lines · 181 tokens per session scan A b10bff6478a5
packmind-update-playbook is a skill published in the GitHub repository PackmindHub/packmind (319 stars, last pushed 4d ago), licensed Apache-2.0. It adds 181 tokens to every session and 1,661 once invoked, about $0.0007 per session on Opus 5.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
ce-compound
Document a recently solved problem or durable project vocabulary in docs/solutions/ or CONCEPTS.md. Use when capturing a learning after work.
ce-work
Execute a plan or concrete work prompt end-to-end. Use when implementing from docs/plans, a spec path, or a clear build request; use ce-debug for open-ended bugs.
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…
ce-commit-push-pr
Commit, push, and open a PR. Use when asked to ship/open a PR, or for PR-description-only flows like writing, rewriting, or describing a PR body.
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.