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/cleanup-repo)<a href="https://agentmods.dev/commands/kaelsensei/magicaibuilder/cleanup-repo"><img src="https://agentmods.dev/badge/commands/kaelsensei/magicaibuilder/cleanup-repo/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/cleanup-repo"><img src="https://agentmods.dev/badge/commands/kaelsensei/magicaibuilder/cleanup-repo.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.03233 |
| Opus 5 | $0.00000 | $0.01617 |
| Sonnet 5 | $0.00000 | $0.00647 |
| Haiku 4.5 | $0.00000 | $0.00323 |
Grade A, and why
cleanup-repo 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 11d 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 — 430 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cleanup Repo Command – Repository Organization and Structure Cleanup
When /cleanup-repo is invoked, immediately execute the following steps to analyze, organize, and clean up the repository structure when files are scattered and disorganized.
Step 1: Load Project Context
- 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
- Read relevant documentation:
README.mdPROGRESS.md.cursor/docs/DOCUMENTATION_STRUCTURE.md(if exists)- Architecture documents
- Identify the current Git branch and assume it is a refactor branch, not
main
Step 2: Analyze Current Repository Structure
-
Scan the entire repository to understand current organization:
find . -type f -name "*.md" -o -name "*.json" -o -name "*.ps1" -o -name "*.js" | grep -v node_modules | grep -v .git -
Identify scattered files:
- Documentation files in root (should be in
docs/or.cursor/docs/) - Script files in root (should be in
scripts/ortools/) - Configuration files in wrong locations
- Test data files in root (should be in
test-data/ormisc/) - Image/assets in wrong locations
- Duplicate files
- Unused files
- Documentation files in root (should be in
-
Check for organizational issues:
- Multiple documentation files in root vs. organized folders
- Scripts scattered vs. in a
scripts/folder - Test data mixed with source code
- Configuration files not in standard locations
- Build artifacts in wrong places
- Temporary files that should be deleted
-
Review recommended structure (from
.cursor/docs/DOCUMENTATION_STRUCTURE.mdif available):- Documentation should be organized in folders
- Scripts should be in
scripts/ortools/ - Test data should be in
test-data/ormisc/ - Assets should be in
src/assets/or appropriate folders
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.
- 11d ago First seen · 430 lines · 0 tokens per session scan A 23c2bcc2f9e4
cleanup-repo 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 3,233 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
add-endpoint
Scaffold a new API endpoint with full layering.
review
Review code changes against project conventions.
fix-issue
Investigate and fix an issue.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.