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 jpoutrin/product-forge --skill bl-stackgit clone --depth 1 https://github.com/jpoutrin/product-forgeWrote 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/jpoutrin/product-forge/bl-stack)<a href="https://agentmods.dev/skills/jpoutrin/product-forge/bl-stack"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/bl-stack/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/jpoutrin/product-forge/bl-stack"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/bl-stack.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.00018 | $0.00962 |
| Opus 5.5 | $0.00007 | $0.00385 |
| Sonnet 5.5 | $0.00004 | $0.00192 |
| Haiku 4.5 | $0.00002 | $0.00096 |
Grade A, and why
bl-stack 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 1mo 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/bl-stack - Git-Branchless Stack Management
Category: Git Workflow
Manage commit stacks using git-branchless. View your stack, navigate between commits, and edit any commit in the stack with automatic restacking.
Usage
/bl-stack [action] [options]
Actions
| Action | Description |
|---|---|
show |
Display the commit stack (default) |
prev [N] |
Move to parent commit (N commits up) |
next [N] |
Move to child commit (N commits down) |
amend |
Amend current commit + restack descendants |
reword |
Change commit message + restack descendants |
restack |
Rebase descendants onto amended commit |
reorder |
Interactive rebase to reorder/squash commits |
Examples
# View current stack
/bl-stack
/bl-stack show
# Navigate
/bl-stack prev # Go up one commit
/bl-stack prev 2 # Go up two commits
/bl-stack next # Go down one commit
# Edit commits
/bl-stack amend # After making changes, amend current commit
/bl-stack reword # Change current commit's message
# Reorganize
/bl-stack reorder # Interactive rebase (pick, squash, drop, reorder)
/bl-stack restack # Fix abandoned commits after manual amend
Execution
This command delegates to the bl-stack-expert agent:
Task(subagent_type="git-workflow:bl-stack-expert",
prompt="Execute stack operation: <action>")
Execution Instructions
-
Verify Prerequisites
- Check git-branchless is installed
- Check repository is initialized for branchless
-
Show Current State
- Run
git slto display the stack - Explain smartlog icons (◆ ◯ ● ✕)
- Run
-
Execute Action
- For
show: Display and explain the stack - For
prev/next: Navigate and confirm position - For
amend: Stage changes and rungit amend - For
reword: Open editor for message change - For
restack: Rebase descendants onto current commit - For
reorder: Rungit rebase -i main
- For
-
Confirm Result
- Show final state with
git sl
- Show final state with
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.
- 1mo ago First seen · 153 lines · 18 tokens per session scan A 2eb12a78720d
bl-stack is a skill published in the GitHub repository jpoutrin/product-forge (16 stars, last pushed 7mo ago), licensed MIT. It adds 18 tokens to every session and 962 once invoked, about $0.0001 per session on Opus 5.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
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.