vibe-spec-packager

vibe-spec-packager is a skill for Claude Code from richfrem/agent-plugins-skills. It costs 31 tokens per session (1,152 once invoked), scanned A, original, MIT.

A packaging and scaffolding tool that turns approved specifications into organised specification files and a starter codebase. It includes rules, requirements, architecture details, implementation tasks, and acceptance criteria.

In plain words
What is it for?
Use it to create a Spec Kit package, define what to preserve or replace, scaffold a clean project directory, and prepare phased implementation work.
Why use it?
It removes the manual work of organising design decisions into a consistent package before coding begins. It gives developers a prepared structure for implementing the target system.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions subagents.

Part of the exploration-cycle-plugin plugin — 20 skills, 15 agents shipped together

Good fit Use it to create a Spec Kit package, define what to preserve or replace, scaffold a clean project directory, and prepare phased implementation work.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/richfrem/agent-plugins-skills/vibe-spec-packager
Install

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.

Any agent
npx skills add richfrem/agent-plugins-skills --skill vibe-spec-packager
Clone the repo
git clone --depth 1 https://github.com/richfrem/agent-plugins-skills

Made for: Claude Code.

Or install exploration-cycle-plugin, the plugin that ships this one along with the rest of its 20 skills, 15 agents.

Wrote 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.

agentmods badge for vibe-spec-packager

README.md
[![agentmods](https://agentmods.dev/badge/skills/richfrem/agent-plugins-skills/vibe-spec-packager/github.svg)](https://agentmods.dev/skills/richfrem/agent-plugins-skills/vibe-spec-packager)
Your own site
<a href="https://agentmods.dev/skills/richfrem/agent-plugins-skills/vibe-spec-packager"><img src="https://agentmods.dev/badge/skills/richfrem/agent-plugins-skills/vibe-spec-packager/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.

agentmods 80×15 button for vibe-spec-packager

Your own site · 80×15
<a href="https://agentmods.dev/skills/richfrem/agent-plugins-skills/vibe-spec-packager"><img src="https://agentmods.dev/badge/skills/richfrem/agent-plugins-skills/vibe-spec-packager.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,152 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00031 $0.01152
Opus 5 $0.00015 $0.00576
Sonnet 5 $0.00006 $0.00230
Haiku 4.5 $0.00003 $0.00115

Measured 5d ago against content hash 113607d5f012, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

vibe-spec-packager 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 5d 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.

plugins/exploration-cycle-plugin/skills/vibe-spec-packager/SKILL.md · 73 lines

How it starts

The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Specification Packaging & Codebase Scaffolding (v2)

You are a Principal DevOps and Systems Scaffolding Specialist. Your job is to compile verified and approved architectural specs into a Spec Kit-compatible specification package, generate a Superpowers-ready execution package, and bootstrap a clean target sandbox codebase directory.


Scaffolding & Packaging Workflow

Step 1: Consolidate Specifications into Spec-Kit compatible package

Locate the verified specs directory and generate a fully-compliant Spec Kit package under /speckit/:

  1. speckit/constitution.md: Draft the architectural governing rules and principles (e.g. Spec-First, TDD requirement, Domain Purity, absolute rewrite restrictions).
  2. speckit/spec.md: Compile all requirements from requirements extraction, classifying each behavior as PRESERVE, REPLACE, QUESTION, or DEPRECATE.
  3. speckit/plan.md: Pre-populate clean architecture implementation details, target structures, and migration strategies.
  4. speckit/tasks.md: Generate the phased implementation plan containing granular Work Packages (WPs) complete with spec references, TDD requirements, and acceptance criteria.
  5. speckit/traceability.md: Create a bidirectional requirements traceability matrix mapping requirements to design patterns and source prototype components.
  6. speckit/open-questions.md: Extract any unresolved items and LOW confidence rules from the session memory.
  7. speckit/risk-register.md: Document the Migration Risk Score results, including any AUTONOMOUS_REWRITE_FORBIDDEN exception clearances.
  8. speckit/domain-lexicon.json: Materialize the canonical glossary lexicon mapped from REQS.md.
  9. speckit/certification-manifest.yaml: Consolidate all dynamic validator results.

Read the full file on GitHub · 73 lines

Files

What ships with it

2 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.

Changes

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.

  1. 5d ago First seen · 73 lines · 31 tokens per session scan A 113607d5f012

Subscribe to this mod's changes

vibe-spec-packager is a skill published in the GitHub repository richfrem/agent-plugins-skills (6 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 1,152 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-09-03.