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/nasrulhazim/claude/kickoff-patchnpx skills add nasrulhazim/claude --skill kickoff-patchgit clone --depth 1 https://github.com/nasrulhazim/claudeWrote 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/nasrulhazim/claude/kickoff-patch)<a href="https://agentmods.dev/skills/nasrulhazim/claude/kickoff-patch"><img src="https://agentmods.dev/badge/skills/nasrulhazim/claude/kickoff-patch.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.00460 | $0.03750 |
| Opus 5 | $0.00230 | $0.01875 |
| Sonnet 5 | $0.00092 | $0.00750 |
| Haiku 4.5 | $0.00046 | $0.00375 |
Grade A, and why
kickoff-patch 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.
How it starts
The opening of the file, as written. The whole thing — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kickoff Patch — Bring a Kickoff-based project up to the latest baseline
/kickoff patch upgrades a Laravel project that was scaffolded from
CleaniqueCoders Kickoff to the current
Kickoff baseline — pulling in new packages, menu items, settings, UI fixes, components,
config, and CI changes — without clobbering the developer's own work. It is a
preview-first, approve-per-category merge — 3-way when the original version is
available, 2-way otherwise — not a file copy.
Mental model (read this first — it determines everything)
Kickoff is not a Laravel skeleton you fork or a dependency you track. It is a
one-shot Symfony Console scaffolder: kickoff start <owner> <name> runs laravel new,
copies stubs/ over the fresh app, and composer requires a hardcoded package set —
then walks away. After scaffolding there is no link back: cleaniquecoders/kickoff
never appears in composer.lock, and there is no version marker. Consequences:
- Two sources of truth define a Kickoff baseline at any version:
- Files under
stubs/(copied 1:1 onto the project root). - Imperative logic in
src/StartCommand.php— the composer package list,composer.jsonscripts/autoload,vendor:publishtags, npm installs, and post-install artisan commands.composer.jsonis rewritten in code, never shipped as a stub, so you cannot diff a stubcomposer.json.
- Files under
- The latest baseline is the locally-installed kickoff. The patch REQUIRES
cleaniquecoders/kickoffinstalled globally (composer global require cleaniquecoders/kickoff) and reads itsstubs/+StartCommand.phpas latest. Acomposer globalinstall is dist-based (no git tags) — it is a single version. - A patch is a 3-way merge (base = original version, theirs = latest, mine = your files), never an overwrite. The project and Kickoff both evolve; e.g. 1.4.2 → 1.24.0 is ~20 versions of drift with files changed on both sides, so overwriting either direction destroys real work. The original-version base comes from a git tag when a git source exists; otherwise the patch degrades to a lower-precision 2-way compare.
- Version detection is inferred, then confirmed, because no marker exists today. The first patch stamps a marker so every subsequent run is exact.
What ships with it
4 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.
- 5d ago First seen · 234 lines · 460 tokens per session scan A 3f19be9824bd
kickoff-patch is a skill published in the GitHub repository nasrulhazim/claude (22 stars, last pushed 3d ago), licensed MIT. It adds 460 tokens to every session and 3,750 once invoked, about $0.0023 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
laravel-actions
Build, refactor, and troubleshoot Laravel Actions using lorisleiva/laravel-actions. Use when implementing reusable action classes (object/controller/job/listener/command), converting service classes/controllers/jobs into actions, orchestrating workflows via faked actions, or debugging action entrypoints and wiring.
laravel-specialist
Build and configure Laravel 10+ applications, including creating Eloquent models and relationships, implementing Sanctum authentication, configuring Horizon queues, designing RESTful APIs with API resources, and building reactive interfaces with Livewire. Use when creating Laravel models, setting up queue workers…
laravel-best-practices
Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code. This includes creating or modifying controllers, models, migrations, form requests, policies, jobs, scheduled commands, service classes, and Eloquent queries. Triggers for N+1 and query performance issues, caching strategies, authorization…
laravel-security
Laravel security best practices for authn/authz, validation, CSRF, mass assignment, file uploads, secrets, rate limiting, and secure deployment.
integration-fixture
Create or validate a .test integration fixture under tests/php/Integration/Fixtures.
create-module
Scaffold a new Marko module — a self-contained Composer package with composer.json, namespaced src/, and Pest tests. Use this skill whenever the user asks to create, add, or scaffold a new Marko module or package. Concrete triggers: 'create a module named payment', 'scaffold an acme/blog package', 'add a new module…