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/laurigates/claude-plugins/code-scaffold-backportnpx skills add laurigates/claude-plugins --skill code-scaffold-backportgit clone --depth 1 https://github.com/laurigates/claude-pluginsWrote 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/laurigates/claude-plugins/code-scaffold-backport)<a href="https://agentmods.dev/skills/laurigates/claude-plugins/code-scaffold-backport"><img src="https://agentmods.dev/badge/skills/laurigates/claude-plugins/code-scaffold-backport.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.00042 | $0.00957 |
| Opus 5 | $0.00021 | $0.00478 |
| Sonnet 5 | $0.00008 | $0.00191 |
| Haiku 4.5 | $0.00004 | $0.00096 |
Grade A, and why
code-scaffold-backport 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 today.
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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Back-Port Instance Fixes Into Their Scaffold/Generator
When to Use This Skill
| Situation | Skill |
|---|---|
Fixing, reviewing, or auditing a file a generator emitted — cookiecutter/copier template, justfile new-* recipe, a *-scaffold skill, a "copy the example app" doc |
This skill — patch the generator in the same sweep |
| Repeated code inside one codebase, with no generator behind it | code-quality-plugin:dry-consolidation |
| Auditing a whole fleet of generated instances against their template | The inverse direction — .claude/rules/generated-fleet-drift.md; an instance may legitimately be ahead of the template, so never auto-apply template → instance |
When fixing something that was generated — a site scaffolded by a
justfile recipe, a repo from a cookiecutter template, a config from a
new-* skill — check whether the bug came from the generator, and if
so, fix the generator in the same sweep. A fix applied only to the
deployed instance leaves every future generation broken in the same
way, and the gap is invisible until the next person scaffolds.
The failure mode
Canonical case (FVH sites monorepo, 2026-06): two PRs fixed the
deployed example-static site — service.targetPort: 8080 for the
non-root nginx image, numeric runAsUser for Kyverno — but the
just new-site template that had produced those broken values was
never touched. Every subsequently scaffolded site would have shipped
with chart-default port-80 probes against an 8080 listener: pod never
Ready, stuck Progressing, no error anywhere. Found and back-ported
only weeks later during a readiness audit (sites#11).
The shape is always the same:
- An instance misbehaves; someone fixes the instance. PR merges, done.
- The generator still emits the pre-fix content.
- The next generation reproduces the bug — often for someone without the context of fix #1.
The rule
- When fixing a generated artifact, ask: "did the generator produce this bug?" If yes, patch the generator template in the same PR (or an immediately linked one) — not as a someday follow-up.
- When reviewing a fix to a known-scaffolded file (e.g.
deploy/values.yamlin a monorepo with anew-*recipe, anything under a directory a cookiecutter emits), check the template for the same defect before approving. - When auditing a scaffold for readiness, diff the template's output against the oldest working instance — accumulated instance-only fixes show up as the delta.
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.
- today First seen · 87 lines · 42 tokens per session scan A 807bf34d2ebe
code-scaffold-backport is a skill published in the GitHub repository laurigates/claude-plugins (57 stars, last pushed yesterday), licensed MIT. It adds 42 tokens to every session and 957 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.
Other skills, from other repositories
feature-branch-pr-writing
Use this skill when the user asks to write, draft, create, or improve a PR description for a Shopware core repository PR — AND that PR targets a non-trunk feature branch (not trunk itself). Trigger phrases like "write a PR description", "draft the PR", "what should I put in the PR body". The skill detects the target…
ci-log-interpretation
Use this skill when reading or analyzing CI logs from a Shopware GitHub Actions workflow to figure out why a build failed — phrases like "why did CI fail", "what broke the build", "check the pipeline", "interpret these logs", "debug this red build" — or whenever raw run logs, job logs, or check annotations from a…
a0-create-plugin
Create, extend, or modify Agent Zero plugins. Follows strict full-stack conventions (usr/plugins, plugin.yaml, Store Gating, AgentContext, plugin settings). Use for UI hooks, API handlers, lifecycle extensions, or plugin settings UI.
a0-contribute-plugin
Guide for publishing an Agent Zero plugin to the community Plugin Index (a0-plugins repo). Covers GitHub repo setup, index.yaml creation, CI validation rules, and PR submission. Use when the user wants to share, publish, submit, or contribute a plugin to the Plugin Hub so other Agent Zero users can find and install it.
repo-activity
Scan all git repositories under /repos and report recent activity — last commit age, branch, uncommitted changes — in age-bucketed tables. Use when the user asks for a repo activity overview, "what have I been working on", portfolio status, or which repos are active/dormant.
a0-plugin-router
Main entry point for all Agent Zero plugin tasks. Routes to specialist skills for creating, reviewing, contributing, managing, or debugging plugins. Use when the user mentions plugins, asks how the plugin system works, wants to build/install/uninstall/publish/debug a plugin, or asks about the Plugin Hub.