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 agentmods add commands/kaelsensei/magicaibuilder/featuregit 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)<a href="https://agentmods.dev/commands/kaelsensei/magicaibuilder/feature"><img src="https://agentmods.dev/badge/commands/kaelsensei/magicaibuilder/feature.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 | $0.00000 | $0.01413 |
| Opus 5 | $0.00000 | $0.00707 |
| Sonnet 5 | $0.00000 | $0.00283 |
| Haiku 4.5 | $0.00000 | $0.00141 |
Grade A, and why
feature 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 today.
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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Command – New Functionality Workflow
When /feature <feature description> 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- Technical stack patternsdocumentation.mdc- Documentation update requirementsversion-management.mdc- Git commit/push workflow
- Read relevant documentation:
README.mdPROGRESS.md- Task or requirement documents
- Architecture and design documents
- Identify the current Git branch and assume it is a feature branch, not
main - Check for attachments (images, screenshots, mockups, diagrams):
- Analyze any visual references provided
- Extract design intentions, UI layouts, or flows from images
- Use attachments to clarify requirements and expected behavior
- If attachments conflict with description, ask for clarification
Step 2: Understand and Define the Feature
- Parse the feature description provided after
/feature - Incorporate context from any attached images or screenshots:
- UI mockups or design references
- Workflow diagrams
- Example screens or behavior demonstrations
- Error states or edge cases shown visually
- Clearly define:
- What new behavior is being added
- What is explicitly out of scope
- Identify impacted layers:
- UI components (if applicable)
- Database schema/queries (if applicable)
- External data sources (APIs, scraping, etc.)
- Caching mechanisms
- TypeScript / JavaScript utilities
- Other project-specific layers
- If requirements or scope are unclear (even with attachments), stop and ask before coding
Step 3: Architecture & Design Validation
Before writing code:
- Ensure the feature does not violate existing architecture
- Confirm:
- Separation of concerns is preserved (UI, data layer, external sources, etc.)
- Project-specific architectural constraints are maintained
- Data storage remains single source of truth (when applicable)
- No shortcuts or hacks are introduced
- For database changes:
- Consider migration strategy for existing data
- Ensure indexes are added for new queries
- Validate design consistency if UI mockups were provided:
- Check alignment with existing design system
- Ensure responsive design principles are followed
- Verify accessibility considerations
- If the feature conflicts with architecture, propose an alternative first
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.
- today First seen · 184 lines · 0 tokens per session scan A d22de02ded2c
feature is a command published in the GitHub repository KaelSensei/MagicAIBuilder (2 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,413 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-09-04.
Other commands, from other repositories
spec-plan
Step 4 of the Vibe-Spec workflow. Generate the high-level plan file for every phase in the V2 phase index, each with a scope + status header, so the user has a complete set of plan files to work from.
spec-phases
Step 3 of the Vibe-Spec workflow. Break the V1 spec into sequential, self-contained phases and append a phase index, producing the final V2 spec.
spec-secrets
Audit a Vibe-Spec app for secrets leaking to the browser. A locked-down, redacting command — a local script reads .env and the built bundle, and Claude only ever sees variable NAMES and pass/fail verdicts. Secret values never enter the model's context.
spec-setup
Guided environment setup for the Vibe-Spec stack. Figures out which tools your project needs (from your spec, or by project type), checks what's missing, and helps you install only the gaps — proposing exact per-OS commands and running each only after you confirm.
spec-doctor
Read-only environment health check for the Vibe-Spec stack. Detects your OS and reports which prerequisite tools (Git, Node, pnpm, Docker, uv) are installed, their versions, and what each is needed for. Installs nothing.
spec-implement
Step 5 of the Vibe-Spec workflow. Promote a phase plan to detailed, implement it following the vibe-spec references, then update the docs so the spec reflects reality.