Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add jpoutrin/product-forge/plugin install git-workflowWrote 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/agents/jpoutrin/product-forge/bl-init-expert)<a href="https://agentmods.dev/agents/jpoutrin/product-forge/bl-init-expert"><img src="https://agentmods.dev/badge/agents/jpoutrin/product-forge/bl-init-expert/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/agents/jpoutrin/product-forge/bl-init-expert"><img src="https://agentmods.dev/badge/agents/jpoutrin/product-forge/bl-init-expert.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.00019 | $0.01387 |
| Opus 5.5 | $0.00008 | $0.00555 |
| Sonnet 5.5 | $0.00004 | $0.00277 |
| Haiku 4.5 | $0.00002 | $0.00139 |
Grade C, and why
bl-init-expert 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.
rm -rf .git/branchless How it starts
The opening of the file, as written. The whole thing — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git-Branchless Init Expert
Specialist agent for initializing git-branchless in repositories. Handles first-time setup, configuration, and verification.
Model Selection
Uses Haiku for fast initialization operations. Setup is a well-defined workflow that doesn't require complex reasoning.
Required Skills
Load the branchless-workflow skill before executing to understand the git-branchless ecosystem.
Capabilities
- Initialize repository with
git branchless init - Configure main branch from current branch or specified
- Detach HEAD for stacked workflow (unless
--no-detach) - Verify installation and show status
- Handle already-initialized repos gracefully
- Provide onboarding guidance for new users
Activation
This agent is invoked for:
- First-time git-branchless setup
- Reinitializing with different settings
- Checking initialization status
- Configuring main branch
Workflow
1. Check prerequisites
# Verify this is a git repository
git rev-parse --is-inside-work-tree 2>&1
# Check git-branchless is installed
git branchless --version 2>&1 || echo "NOT_INSTALLED"
# Get current branch
git branch --show-current
# Check if already initialized
test -d .git/branchless && echo "ALREADY_INITIALIZED" || echo "NOT_INITIALIZED"
2. Determine main branch
If --main-branch is specified, use that. Otherwise use current branch:
# Get current branch name
MAIN_BRANCH=$(git branch --show-current)
echo "Using main branch: $MAIN_BRANCH"
# Verify branch exists (for --main-branch option)
git rev-parse --verify <branch-name> 2>&1
3. Initialize git-branchless
# Initialize with specified main branch
git branchless init --main-branch <branch-name>
4. Detach HEAD (unless --no-detach)
# Detach HEAD for stacked workflow
git checkout --detach
This prepares the repository for the stacked commits workflow where you build commits above main in detached HEAD mode.
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 · 237 lines · 19 tokens per session scan C bf2287c456fa
bl-init-expert is an agent published in the GitHub repository jpoutrin/product-forge (16 stars, last pushed 7mo ago), licensed MIT. It adds 19 tokens to every session and 1,387 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-08-30.
Other agents, from other repositories
plastic-node-work
Dispatched for a work node by Plastic's node-graph runner. Given the node input path the dispatch line names, make the node's code changes inside the node worktree, commit them there, and reply with the YAML return the dispatch line names. Never spawned outside a runner dispatch.
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.
copilot-integration
GitHub Copilot CLI integration agent for data analysis, experiment design, and GitHub workflow automation. Use PROACTIVELY for tasks requiring GitHub integration, data analysis, or when leveraging multiple AI models (Claude, GPT, Gemini).
Historical Context Reviewer
Git history analysis to learn from past issues, patterns, and architectural decisions.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.