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.
git clone --depth 1 https://github.com/KaelSensei/MagicAIBuilderWrote 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/commands/kaelsensei/magicaibuilder/create-branch)<a href="https://agentmods.dev/commands/kaelsensei/magicaibuilder/create-branch"><img src="https://agentmods.dev/badge/commands/kaelsensei/magicaibuilder/create-branch.svg" alt="Measured on agentmods" 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.00000 | $0.01878 |
| Opus 5 | $0.00000 | $0.00939 |
| Sonnet 5 | $0.00000 | $0.00376 |
| Haiku 4.5 | $0.00000 | $0.00188 |
Grade A, and why
create-branch 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 7d 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 — 293 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Branch Command – Interactive Branch Creation
When /create-branch is invoked, immediately execute the following steps to interactively create a new feature branch with proper naming conventions.
Step 1: Load Project Context & Follow All Rules
- Assume the project root as the working directory
- Load and strictly follow ALL Cursor rules from
.cursor/rules/*.mdc:security.mdc- Security requirementstechnical-stack.mdc- React Native/SQLite patternsdocumentation.mdc- Documentation update requirementsversion-management.mdc- Git commit/push workflowgeneral-principles.mdc- Project philosophy
- Check current git status and branch
- Read
PROGRESS.mdto understand current project state
Step 2: Check Current State
-
Check current branch:
git branch --show-current -
Check for uncommitted changes:
git status -
If uncommitted changes exist:
- Stop and ask user to commit or stash first
- Never create branch with uncommitted changes
- Provide options: commit now, stash, or cancel
-
If on main/master:
- Proceed (this is expected for creating new branches)
- Will switch to main/master before creating branch
Step 3: Ask for Branch Name
-
Prompt user for branch name:
- Ask: "What would you like to name the new branch?"
- Provide examples of good branch names
- Explain naming conventions
-
Wait for user input:
- User will provide the branch name
- Validate the name before proceeding
Step 4: Validate and Normalize Branch Name
-
Validate branch name:
- Must not be empty
- Must not contain spaces (replace with hyphens)
- Must not start with special characters
- Must not be
main,master, or protected branch names - Should be lowercase (convert if needed)
-
Apply naming conventions:
- If name doesn't start with
feature/,fix/,refactor/, ordocs/:- Ask user which type: feature, fix, refactor, or docs
- Prepend appropriate prefix:
feature/,fix/,refactor/, ordocs/
- If name already has prefix, use it as-is
- Convert to lowercase
- Replace spaces and underscores with hyphens
- Remove special characters (keep only alphanumeric and hyphens)
- If name doesn't start 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.
- 7d ago First seen · 293 lines · 0 tokens per session scan A fc2cc3ee6966
create-branch is a command published in the GitHub repository KaelSensei/MagicAIBuilder (2 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,878 tokens. 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-08-31.
Other commands, from other repositories
implement-feature
Implement an approved feature plan with fresh-context slices, TDD, evidence, and PR-ready output.
review
Review code changes against project conventions.
speckit.git.commit
Proxy for speckit.git.commit.md.
speckit.git.remote
Proxy for speckit.git.remote.md.
prepare-release
Prepare a new release with AI-generated summary.
plan-worktree-cleanup
Remove stale and merged feature worktrees, and prune their leftover admin metadata.