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 skills add bishopZ/2026-Boilerplate --skill rebrandgit clone --depth 1 https://github.com/bishopZ/2026-BoilerplateWrote 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/bishopz/2026-boilerplate/rebrand)<a href="https://agentmods.dev/skills/bishopz/2026-boilerplate/rebrand"><img src="https://agentmods.dev/badge/skills/bishopz/2026-boilerplate/rebrand/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/bishopz/2026-boilerplate/rebrand"><img src="https://agentmods.dev/badge/skills/bishopz/2026-boilerplate/rebrand.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.00054 | $0.00795 |
| Opus 5 | $0.00027 | $0.00398 |
| Sonnet 5 | $0.00011 | $0.00159 |
| Haiku 4.5 | $0.00005 | $0.00080 |
Grade A, and why
rebrand 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 11d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rebrand
Use this skill when a developer has cloned the boilerplate and wants to turn it into their own project identity.
Required Inputs
site_title: The new project/site name shown to users.site_description: A short project summary used in metadata and docs.
If either input is missing, pause and ask for it before editing files.
Goal
Replace boilerplate branding so the project is clearly the developer's new project.
Files To Update
1) index.html
Update title/description branding in metadata to use the new values.
Required replacements:
<title><meta name="title"><meta name="description">
2) src/client/utilities/constants.ts
Update centralized metadata constants used by PageMeta:
- Any boilerplate-specific values (author, preview image URL, social handle, keywords, fallback canonical host, locale, and mobile meta defaults) that should change for the new project.
3) src/client/ui/page-meta.tsx
Confirm PageMeta still receives title and description and maps them to the full metadata set using React 19 metadata tags (<title>, <meta>, <link rel="canonical">).
4) Page metadata calls
Update page-level PageMeta calls in:
src/client/pages/Home.tsxsrc/client/pages/About.tsxsrc/client/pages/Login.tsxsrc/client/pages/Product.tsxsrc/client/pages/Privacy.tsxsrc/client/pages/Terms.tsxsrc/client/pages/NotFound.tsx
Required replacements:
- Page title values passed to
title. - Page description values passed to
description.
5) package.json
Update package metadata:
name: kebab-case package name that matches the new project title.description: usesite_description.
6) README.md
Update the README so it no longer reads as a boilerplate identity.
- Replace the H1 title with the new project title.
- Replace the short description under the H1 with
site_description. - Update opening paragraphs that still brand the repo as "2026 Boilerplate" so they describe the new project.
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.
- 11d ago First seen · 87 lines · 54 tokens per session scan A fdae379eae26
rebrand is a skill published in the GitHub repository bishopZ/2026-Boilerplate (24 stars, last pushed 1mo ago), licensed MIT. It adds 54 tokens to every session and 795 once invoked, about $0.0003 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
draft-release-notes
Author the committed release-notes file for a Prisma 8 release (stable or 8.0.0-rc.N) by enumerating the merged PRs since the previous release v tag (stable or -rc.N), resolving opaque TML-NNNN: titles via Linear context (never copied verbatim), triaging public-worthiness, and writing categorized notes — breaking…
record-upgrade-instructions
Record upgrade instructions alongside a Prisma Next breaking-change PR, so downstream consumers (users of @internal/ and authors of Prisma Next extensions) can apply the matching code translation automatically via the published upgrade skills. Use when you have refactored framework code and the test suite went red in…
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
triage-contributor-pr
Triage open pull requests from external contributors to prisma/prisma and produce a per-PR verdict with evidence. Use when a maintainer asks to triage, evaluate, assess, or review the queue of incoming contributor PRs, to decide whether a fork PR is safe to run CI on, to check whether a PR is in scope for its version…
contrib-pr
Open a high-quality external contributor PR against prisma/orm. Use when the user is an outside contributor (not a Prisma maintainer) and wants to submit a change as a pull request from a fork. Encodes the contribution flow from CONTRIBUTING.md so the resulting PR passes review on the first round.
github-review-iteration
Orchestrates a GitHub PR review loop by delegating triage and implementation to dedicated sub-agents, then repeating until actionable review items are cleared. Use when the user says “address PR review”, “triage review comments”, or “iterate until review is clean”.