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/feature-branch)<a href="https://agentmods.dev/commands/kaelsensei/magicaibuilder/feature-branch"><img src="https://agentmods.dev/badge/commands/kaelsensei/magicaibuilder/feature-branch/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/commands/kaelsensei/magicaibuilder/feature-branch"><img src="https://agentmods.dev/badge/commands/kaelsensei/magicaibuilder/feature-branch.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.00000 | $0.01115 |
| Opus 5 | $0.00000 | $0.00558 |
| Sonnet 5 | $0.00000 | $0.00223 |
| Haiku 4.5 | $0.00000 | $0.00112 |
Grade A, and why
feature-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 9d 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Branch Command – Branch Creation & Management Workflow
When /feature-branch <branch-name> or /feature-branch is invoked, immediately execute the following steps.
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 workflow
- Check current git status and branch
- Read
PROGRESS.mdto understand current project state
Step 2: Determine Branch Name
- If branch name provided: Use
<branch-name>from command - If no branch name provided:
- Infer from current work context
- Use format:
feature/<description>orfix/<description> - Ask user for branch name if unclear
- Validate branch name:
- Use lowercase with hyphens (e.g.,
feature/search-reset-button) - Avoid special characters or spaces
- Keep it descriptive but concise
- Use lowercase with hyphens (e.g.,
Step 3: Check Current State
-
Check current branch:
git branch --show-current -
Check for uncommitted changes:
git status -
If uncommitted changes exist:
- Commit them first (following version-management.mdc rules)
- Or stash them if user prefers
- Never create branch with uncommitted changes unless explicitly requested
-
If on main/master:
- Warn user (but proceed if confirmed)
- Always create feature branch from main/master
Step 4: Create Feature Branch
-
Ensure you're on the base branch (usually
mainormaster):git checkout main # or master git pull origin main # or master -
Create and switch to new branch:
git checkout -b <branch-name> -
Push branch to remote (set upstream):
git push -u origin <branch-name>
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.
- 9d ago First seen · 176 lines · 0 tokens per session scan A 50d0add50e64
feature-branch is a command published in the GitHub repository KaelSensei/MagicAIBuilder (2 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,115 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.
scm
SCM workflow for Git operations (branching/merge/conflict/worktree) plus Conventional Commit execution.
prepare-release
Prepare a new release with AI-generated summary.