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-submitgit 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-submit)<a href="https://agentmods.dev/skills/jpoutrin/product-forge/bl-submit"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/bl-submit/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-submit"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/bl-submit.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.01256 |
| Opus 5.5 | $0.00008 | $0.00502 |
| Sonnet 5.5 | $0.00004 | $0.00251 |
| Haiku 4.5 | $0.00002 | $0.00126 |
Grade A, and why
bl-submit 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 — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/bl-submit - Git-Branchless PR Submission
Category: Git Workflow
Submit commits from your stack as pull requests. Creates branches, pushes to remote, and guides stacked PR configuration.
Usage
/bl-submit [options]
Options
| Option | Description |
|---|---|
| (none) | Submit current commit (creates branch if needed) |
--all |
Create branches and submit entire stack |
--update |
Update all existing PR branches |
<name> |
Specify branch name for current commit |
Examples
# Submit current commit with auto-generated branch name
/bl-submit
# Submit current commit with custom branch name
/bl-submit pr/user-authentication
# Submit entire stack (creates branches for all commits)
/bl-submit --all
# Update all existing PRs after changes
/bl-submit --update
Execution
This command delegates to the bl-submit-expert agent:
Task(subagent_type="git-workflow:bl-submit-expert",
prompt="Execute submit: <options>")
Execution Instructions
-
Verify Prerequisites
- Check git-branchless is installed
- Check remote is configured
-
Show Current State
- Run
git slto display stack with branches - Identify commits without branches
- Run
-
Execute Submission
- For single: Create branch at current commit, push
- For all: Navigate stack, create branches, push each
- For update: Force-push all existing branches
-
Guide PR Configuration
- Explain stacked PR base branches
- Provide table of branch → base relationships
-
Confirm Result
- Show branches on remote
- Display final state with
git sl
Interactive Flow
User: /bl-submit pr/user-auth
Agent: Submitting current commit...
Current position:
● def5678 feat: add user authentication
Creating branch...
git switch -c pr/user-auth
Pushing to remote...
git submit -c @
✓ Branch pr/user-auth pushed to origin
◆ abc1234 (main) initial commit
┃
● def5678 (ᐅ pr/user-auth) feat: add user authentication
You can now create a PR on GitHub:
Base: main
Compare: pr/user-auth
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 · 203 lines · 19 tokens per session scan A 906b54debea4
bl-submit is a skill 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,256 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
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.