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/feature-spec/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/feature-spec)<a href="https://agentmods.dev/skills/packmindhub/packmind/feature-spec"><img src="https://agentmods.dev/badge/skills/packmindhub/packmind/feature-spec/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/feature-spec"><img src="https://agentmods.dev/badge/skills/packmindhub/packmind/feature-spec.svg" alt="Reviewed on agentmods" width="80" 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.00095 | $0.01717 |
| Opus 5.5 | $0.00038 | $0.00687 |
| Sonnet 5.5 | $0.00019 | $0.00343 |
| Haiku 4.5 | $0.00010 | $0.00172 |
Grade A, and why
feature-spec 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.
How it starts
The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Spec Skill
Generate a comprehensive feature specification grounded in Packmind's hexagonal architecture, frontend gateway/PM-UI conventions, and the OSS/proprietary fork boundary.
When to Use
Use this skill when the user wants to:
- Plan a new feature, fix, or refactor that spans Packmind's stack
- Convert a GitHub issue, design doc, or rough idea into a structured spec
- Get fine-grained validation of data structures, routes, and components before committing to a plan
Do NOT use for trivial one-line fixes or pure dependency bumps.
Packmind Repo Layout (essential context)
- Closed-source fork (
packmind-proprietary): the current working directory when this skill runs. - Open-source repo (
packmind): the sibling directory at../packmind(cloned next to the proprietary repo). Resolve to an absolute path at runtime withrealpath ../packmind. - Most feature work happens on the OSS repo and auto-merges into the proprietary fork. The proprietary fork only contains paid/closed features (e.g.
packages/editions, certainpackages/deploymentsextensions). After an OSS merge, you typically pull on the proprietary side. - Architecture: hexagonal (
packages/{domain}/{domain,application,infra}), NestJS API atapps/api, React+@packmind/uifrontend atapps/frontend, TypeORM, Jest+@swc/jest.
Input Sources
| Source | Examples | Detection |
|---|---|---|
| GitHub | #123, owner/repo#123, full issue URL |
Pattern #\d+ or github.com/.../issues/ |
| File | file:spec.md, path/to/spec.md |
Prefix file: or readable file |
| URL | https://... |
HTTP(S) URL (non-GitHub) |
| Prompt | Any other text | Default |
Workflow Phases
Execute phases sequentially. Phases 1 and 4 run seamlessly (no approval gate). Phases 2 and 3 require user approval before proceeding.
| Phase | File | Purpose | Gate |
|---|---|---|---|
| 1 | phase-1-resolve-source.md |
Detect source type, fetch content, decide OSS-vs-proprietary routing, create state | seamless |
| 2 | phase-2-discovery-and-spec.md |
Research Packmind patterns (reference domain, hex layers, frontend conventions), draft acceptance criteria, generate functional spec | approval |
| 3 | phase-3-implementation.md |
Technical approach + implementation plan (4 subtasks below) | 4 approvals |
| 3A | ↳ Subtask 3A | Validate domain data structures (entities, value objects, events, migrations) | approval |
| 3B | ↳ Subtask 3B | Validate ports, contracts, use cases, services, adapters, NestJS routes | approval |
| 3C | ↳ Subtask 3C | Validate frontend components, gateways, query hooks, PM-UI usage | approval |
| 3D | ↳ Subtask 3D | Generate full implementation plan (task breakdown, grouping, coverage) | approval |
| 4 | phase-4-finalize.md |
Generate context.md, mark spec complete, report (no commit — artifacts live in tmp/) |
seamless |
What ships with it
7 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.
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 · 135 lines · 95 tokens per session scan A 130bcf76e0d9
feature-spec is a skill published in the GitHub repository PackmindHub/packmind (319 stars, last pushed 4d ago), licensed Apache-2.0. It adds 95 tokens to every session and 1,717 once invoked, about $0.0004 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-09-22.
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.