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 retz8/pastiche --skill rebase-feat-with-maingit clone --depth 1 https://github.com/retz8/pasticheWrote 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/retz8/pastiche/rebase-feat-with-main)<a href="https://agentmods.dev/skills/retz8/pastiche/rebase-feat-with-main"><img src="https://agentmods.dev/badge/skills/retz8/pastiche/rebase-feat-with-main/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/retz8/pastiche/rebase-feat-with-main"><img src="https://agentmods.dev/badge/skills/retz8/pastiche/rebase-feat-with-main.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.00058 | $0.00217 |
| Opus 5 | $0.00029 | $0.00109 |
| Sonnet 5 | $0.00012 | $0.00043 |
| Haiku 4.5 | $0.00006 | $0.00022 |
Grade A, and why
rebase-feat-with-main 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.
What it actually says
rebase-feat-with-main
Workflow
- Guard. Current branch must be a feature branch (
<version>/<task-name>) or sub-task branch — never main. Working tree must be clean; if not, stop and ask. git fetch origin maingit rebase origin/main- On conflict: stop immediately, show the conflicting files, and let the user decide — never auto-resolve, never
--abortwithout asking. - If the branch is already pushed:
git push --force-with-lease. Never force-push main. - Report: how many commits were replayed and whether main had moved at all (no-op is a valid outcome).
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 · 16 lines · 58 tokens per session scan A 3cfa276974e2
rebase-feat-with-main is a skill published in the GitHub repository retz8/pastiche (4 stars, last pushed 3mo ago), licensed MIT. It adds 58 tokens to every session and 217 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-31.
Other skills, from other repositories
release-retrospective
Produce a structured look-back after a major release or deprecation — capturing what the plan got right, what it missed, and what to do differently. Trigger when someone says: release retrospective, post-release review, what went wrong with the release, how did the deprecation go, release post-mortem, retro on the…
version-bump-advisor
Recommend the correct semver bump with reasoning and a generated changelog entry. Trigger when someone says: what version bump, is this a breaking change, semver recommendation, should this be major or minor, version this release, changelog entry, what kind of release is this, or anything about versioning a design…
procoder
Work like a senior developer in a repository governed by procoder: run the commit gate before calling anything done, format and lint through the binary, and drive the spec, plan, todo, backlog, and sprint chain in .procoder/. Use this skill when the repository contains a .procoder/ directory or an AGENTS.md naming…
pr-feedback
Work a reviewer's comments on a pull request to the end - all three comment surfaces enumerated before any is triaged, every comment fixed, declined with a reason, or ticketed, push before you reply. Use when a PR comes back with review feedback or a red check.
detect-task
Internal skill for commands. Detect the active task (any tracker adapter) from the task-state file / git branch name. Do not trigger on user conversation - only when commands need task detection.
loop-bb-pr
A command that prepares a repeating check for a Bitbucket pull request. A pull request is a request to review and merge code changes into a project.