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-initgit 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-init)<a href="https://agentmods.dev/skills/jpoutrin/product-forge/bl-init"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/bl-init/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-init"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/bl-init.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.00016 | $0.01049 |
| Opus 5.5 | $0.00006 | $0.00420 |
| Sonnet 5.5 | $0.00003 | $0.00210 |
| Haiku 4.5 | $0.00002 | $0.00105 |
Grade C, and why
bl-init scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
1. Remove: rm -rf .git/branchless .git/hooks/post-* How it starts
The opening of the file, as written. The whole thing — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/bl-init - Git-Branchless Repository Initialization
Category: Git Workflow
Initialize git-branchless in the current repository, using the current branch as the main branch by default. Automatically detaches HEAD so you're ready to start stacking commits.
Usage
/bl-init [options]
Options
| Option | Description |
|---|---|
| (none) | Initialize using current branch as main, then detach HEAD |
--main-branch <branch> |
Specify a different branch as main |
--no-detach |
Initialize without detaching HEAD |
Examples
# Initialize with current branch as main
/bl-init
# Initialize with a specific branch as main
/bl-init --main-branch develop
Execution
This command delegates to the bl-init-expert agent:
Task(subagent_type="git-workflow:bl-init-expert",
prompt="Initialize git-branchless: <options>")
Execution Instructions
-
Check Prerequisites
- Verify this is a git repository
- Check if git-branchless is installed
- Check if already initialized
-
Determine Main Branch
- Use current branch if no
--main-branchspecified - Validate the branch exists
- Use current branch if no
-
Initialize Git-Branchless
- Run
git branchless init --main-branch <branch> - Configure recommended settings
- Run
-
Detach HEAD (unless
--no-detach)- Run
git checkout --detach - This prepares you for the stacked commits workflow
- Run
-
Verify Installation
- Run
git slto confirm working - Show current state with detached HEAD
- Run
-
Provide Next Steps
- Explain basic commands (
git sl,git sync,git submit)
- Explain basic commands (
Interactive Flow
User: /bl-init
Agent: Initializing git-branchless...
Current branch: main
Repository: /path/to/project
Checking prerequisites...
✓ Git repository detected
✓ git-branchless is installed (v0.9.0)
✗ Not yet initialized
Initializing with main branch: main
$ git branchless init --main-branch main
Created config file at .git/branchless/config
Installed hooks at .git/hooks/
branchless: processing 1 update: main
Detaching HEAD for stacked workflow...
$ git checkout --detach
✓ Git-branchless initialized successfully!
Current state:
◆ abc1234 (main) Latest commit message
┃
● abc1234 (HEAD) ← You are here (detached)
Ready to stack commits! Next steps:
1. Use `git record -m "msg"` to create commits
2. Use `git sl` to see your commit stack
3. Use `git sync --pull` to sync with remote
4. Use `git submit` to create/update PRs
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 · 175 lines · 16 tokens per session scan C 689d747bdac7
bl-init is a skill published in the GitHub repository jpoutrin/product-forge (16 stars, last pushed 7mo ago), licensed MIT. It adds 16 tokens to every session and 1,049 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.