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 commands/scenario-labs/skills/squash-messagegit clone --depth 1 https://github.com/scenario-labs/skillsWrote 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/commands/scenario-labs/skills/squash-message)<a href="https://agentmods.dev/commands/scenario-labs/skills/squash-message"><img src="https://agentmods.dev/badge/commands/scenario-labs/skills/squash-message.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.1 | $0.00000 | $0.00337 |
| Opus 5 | $0.00000 | $0.00169 |
| Sonnet 5 | $0.00000 | $0.00067 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
squash-message 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.
What it actually says
Generate a single squash commit message for the current PR.
- Run
git fetch origin main --quiet && git log --oneline $(git merge-base HEAD origin/main)..HEADto see all commits in this branch - Analyze the net diff against main (
git diff $(git merge-base HEAD origin/main)..HEAD): what the PR adds, fixes, or refactors relative to main. The commit list is context, not content: the message describes the diff, not the journey. - Write ONE conventional commit message that summarizes the entire PR and passes
commitlint.config.js:- Title: max 120 chars, conventional commit format (feat/fix/docs/chore), scope from the skill directory names or the cross-cutting scopes (skills, agents, ci, deps, docs, tooling)
- Body: bullet points of key changes, grouped by category
- Footer: Co-Authored-By line
- Preserve distinct meaningful changes instead of flattening everything into one vague line, but only changes that exist in the net diff. A branch commit that fixes or reworks something introduced earlier in the same branch is development churn: fold it into the item it amends, never list it as a fix. Label a body item
featorfixonly when the PR mixes both kinds of net change relative to main; a PR that only adds one thing gets plain bullets describing what landed. - Verify the title passes:
echo "TITLE" | pnpm exec commitlint - Copy the message to clipboard with
echo "MESSAGE" | pbcopy - Tell me the message you copied
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 · 13 lines · 0 tokens per session scan A 1f29fa73a57e
squash-message is a command published in the GitHub repository scenario-labs/skills (10 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 337 tokens. 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 commands, from other repositories
commit
Run when user calls /commit or asks to generate a commit message. Analyzes staged changes and writes a structured commit message.
fix-comments
Address PR review comments by implementing requested changes automatically.
validate-pr-description
Use when validating a PR title and description for conventional commit format, issue linking keywords, and template compliance before submission.
commit
Analyze uncommitted changes, create a branch if needed, and commit with a well-structured message.
fw-setup-use
Workspace FDK stack switch — nvm use from .nvmrc or explicit 10/9 (Node 24.11 vs 18); optional --write-nvmrc and --global flags.
fdk-migrate
Migrate a legacy Freshworks app from platform-version 2.3 (2.x), FDK 9.x, and Node 18 to Platform 3.0 with FDK 10.0.1 and Node 24.11.0. Transforms manifest, request templates, Crayons UI, and validates on the new toolchain. Does not install fdk/Node—use fw-setup (or prompt user to add it) per SKILL.md.