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 bengous/claude-code-plugins/plugin install repo-bootstrapWrote 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/bengous/claude-code-plugins/submodule-setup)<a href="https://agentmods.dev/skills/bengous/claude-code-plugins/submodule-setup"><img src="https://agentmods.dev/badge/skills/bengous/claude-code-plugins/submodule-setup/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/bengous/claude-code-plugins/submodule-setup"><img src="https://agentmods.dev/badge/skills/bengous/claude-code-plugins/submodule-setup.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.00066 | $0.01063 |
| Opus 5.5 | $0.00026 | $0.00425 |
| Sonnet 5.5 | $0.00013 | $0.00213 |
| Haiku 4.5 | $0.00007 | $0.00106 |
Grade A, and why
submodule-setup 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 24d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Submodule Setup
Result:
parent-repo/
├── src/
├── docs/ <- submodule (always present)
└── exports/ <- submodule (always present)
Reference material
This skill is phase-driven and the phase bodies are long. Load what the current step needs rather than reading everything up front:
| File | Read it when |
|---|---|
references/phases.md |
Running any phase — full bodies for Phases 0-10 and Finalization |
references/protocols.md |
You need the manual-intervention handoff format, state-file schema, or default escalation rules |
references/troubleshooting.md |
A phase fails or a submodule misbehaves |
references/decision-rationale.md |
The user asks why submodules over alternatives |
Templates live in assets/, helper scripts in scripts/. Resolve both through
${CLAUDE_PLUGIN_ROOT} — never a hardcoded install path.
Prerequisites
"${CLAUDE_PLUGIN_ROOT}/skills/submodule-setup/scripts/validate-prerequisites.sh"
Required:
- GitHub CLI (
gh) installed and authenticated - Git 2.x+
- Repository with push access
- Ability to create fine-grained PAT
Phase 0: Backup → Phase 1: Parameters → Phase 2: Create Repos → Phase 3: PAT/Secrets
↓
Phase 10: Validate ← Phase 9: Docs ← Phase 8: Hooks ← Phase 7: Scripts ← Phase 6: Actions
↑
Phase 5: Add Submodules ← Phase 4: Migrate (conditional)
| Phase | Purpose |
|---|---|
| 0 | Backup checkpoint — recovery point before any modification |
| 1 | Parameter collection |
| 2 | Create submodule repos |
| 3 | PAT and secrets setup |
| 4 | Content migration (conditional — see below) |
| 5 | Add submodules to parent |
| 6 | Deploy GitHub Actions |
| 7 | Deploy local scripts |
| 8 | Claude Code hooks (optional) |
| 9 | Update documentation |
| 10 | Validation |
What ships with it
14 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- assets/notify-dependent.yml 1.9 KB
- assets/notify-parent.yml 1.6 KB
- assets/README-template.md 1.5 KB
- assets/update-submodules-push.yml 3.5 KB
- assets/update-submodules.yml 2.4 KB
- references/decision-rationale.md 8.1 KB
- references/phases.md 25 KB
- references/protocols.md 3.7 KB
- references/troubleshooting.md 9.6 KB
- scripts/check-nested-repos.sh 4.2 KB runs code
- scripts/create-backup.sh 4.9 KB runs code
- scripts/setup-dev.sh 7.8 KB runs code
- scripts/test-scripts.sh 4.7 KB runs code
- scripts/validate-prerequisites.sh 4.8 KB runs code
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.
- 24d ago Changed · -5 lines 1fec7870ea82
- 1mo ago Changed · +1 lines e637dc56381c
- 1mo ago First seen · 121 lines · 66 tokens per session scan A 6b10bbf7c5f7
submodule-setup is a skill published in the GitHub repository bengous/claude-code-plugins (5 stars, last pushed today), licensed MIT. It adds 66 tokens to every session and 1,063 once invoked, about $0.0003 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
flow-next-land
Resolve feedback and CI for one named pull request, then merge when authorized and ready. Emits LANDVERDICT. Use when asked to land a pull request.
flow-next-worktree-kit
Manage git worktrees (create/list/switch/cleanup) and copy .env files. Use for parallel feature work, isolated review, clean workspace, or when user mentions worktrees.
development-workflow
Detailed development workflow with modular patterns for git, review, testing, and deployment.
stepwise-task-execution
Master workflow for an implementation task. Use when you pick up any task or bug that changes product code, including a needrevision bounce.
github-cli
A command-line tool connection for GitHub tasks that built-in tools do not cover. It uses GitHub's command-line program to work with issues, pull requests, releases, workflows, searches, and the GitHub API.
incremental-commits
Commit boundaries and messages on a task branch. Use when deciding where to cut a commit or how to word one while implementing.