What is skeleton-development?

A design guide for deciding whether new Angular/Otter logic belongs in a component, a separate logic layer, or a store that manages shared state.

Use it before designing an Angular component, service, or store, or use its review process to assess existing code.

It helps prevent business rules and state from being placed in the wrong part of an application or duplicated across multiple places.

How laravel/package-skeleton configures Claude Code and Codex

About the project

Laravel Package Skeleton is a starter repository for creating Laravel packages, with package configuration, testing, static analysis, formatting, and a workbench application already set up. Laravel package developers use it as the starting point for new packages. The catalogue add-ons support workflows around this package template.

laravel/package-skeleton · 71 stars · on GitHub

Reuse

Borrowing it

Nothing to install: this file belongs to laravel/package-skeleton. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/laravel/package-skeleton/main/.agents/skills/skeleton-development/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/laravel/package-skeleton

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/laravel/package-skeleton/skeleton-development/github.svg)](https://agentmods.dev/skills/laravel/package-skeleton/skeleton-development)

Your own site

<a href="https://agentmods.dev/skills/laravel/package-skeleton/skeleton-development"><img src="https://agentmods.dev/badge/skills/laravel/package-skeleton/skeleton-development/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/laravel/package-skeleton/skeleton-development"><img src="https://agentmods.dev/badge/skills/laravel/package-skeleton/skeleton-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 764 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.

Model	Per session	Once invoked
Fable 5.1	$0.00057	$0.00764
Opus 5.5	$0.00023	$0.00306
Sonnet 5.5	$0.00011	$0.00153
Haiku 4.5	$0.00006	$0.00076

Measured 1mo ago against content hash b5c2cb2354ae, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

skeleton-development 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.

.agents/skills/skeleton-development/SKILL.md · 54 lines

How it starts

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

Skeleton Development

Primary Goal

Evolve the starter kit without making it less useful for future package authors.

Workflow

Preserve generic placeholders such as :author_name, :package_name, :vendor_slug, and :package_slug until the configure flow replaces them.
Keep starter guidance minimal and split skeleton-maintenance rules from package-author rules.
Use temporary phase scaffold tests when proving repository shape, file parity, or generated scaffolding; delete those tests before final validation.
Maintain skeleton guidance in AGENTS.md, package guidance in AGENTS_PACKAGE.md, and package-facing local skills in .agents/skills; configure.php generates package AGENTS.md, then links CLAUDE.md to AGENTS.md and .claude to .agents during package configuration.
Keep configure.php feature and tool pruning maps, opt-in non-interactive --[feature] and --[tool] flags, service provider wiring, Composer metadata, README_PACKAGE.md, AGENTS_PACKAGE.md, AI guidance, skills, and publishable files aligned.
Keep configure-only dependencies in require-dev, include them in configure dependency checks, and prune them through the configure composer remove --no-install step so the configured package's composer.json and composer.lock stay in sync.
Preserve the non-interactive contract: metadata validators run against flag and default values before any file changes, results print as single-line JSON on stdout, and --no-interaction, COMPOSER_NO_INTERACTION=1, agent detection, and non-TTY stdin all trigger the mode.
Keep development-time authoring files out of Composer dist archives with .gitattributes when they are not runtime package files.

References

AGENTS.md
AGENTS_PACKAGE.md
Linked CLAUDE.md
README.md
README_PACKAGE.md
.agents/skills/
Linked .claude/
configure.php
.gitattributes
PLAN.md, REQS.md, and phases/ when present

Examples

Add or rename local guidance under AGENTS.md, AGENTS_PACKAGE.md, or .agents/skills, then update front matter names, root guidance, and any scaffold consistency checks.
Add temporary Phase tests to lock down generated file shape, run them to prove the change, then delete them before the final composer test.
Update package-facing README content in README_PACKAGE.md; README.md should stay focused on using this skeleton.
When adding a selectable package feature, add both the starter files and the matching configure pruning behavior so package authors can select or omit it cleanly.
When adding or renaming a selectable feature or tool key, verify the derived non-interactive flag includes only the expected generated files.
When adding a configure-only helper package, update dependenciesAreInstalled(), the removeConfigureDependencies() package list, and temporary copied-skeleton configure checks together.

Read the full file on GitHub · 54 lines

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.

1mo ago First seen · 54 lines · 57 tokens per session scan A b5c2cb2354ae

Subscribe to this mod's changes

skeleton-development is a skill published in the GitHub repository laravel/package-skeleton (71 stars, last pushed 13d ago), licensed MIT. It adds 57 tokens to every session and 764 once invoked, about $0.0002 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.

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

package-skeleton: Skill for Claude Code