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/update-user-guide)<a href="https://agentmods.dev/commands/kaelsensei/magicaibuilder/update-user-guide"><img src="https://agentmods.dev/badge/commands/kaelsensei/magicaibuilder/update-user-guide.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.00727 |
| Opus 5 | $0.00000 | $0.00364 |
| Sonnet 5 | $0.00000 | $0.00145 |
| Haiku 4.5 | $0.00000 | $0.00073 |
Grade A, and why
update-user-guide 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 6d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update User Guide – Add or Refresh User Guide Sections
When /update-user-guide is invoked, add or update sections in USER_GUIDE.md so it stays in sync with the app. Use this after a new feature, or on demand to refresh the guide.
Step 1: Load Context
- Assume the project root as the working directory
- Read USER_GUIDE.md (if it exists) to see current structure and wording
- Read PROGRESS.md and CHANGELOG.md to see what’s new or changed (focus on user-visible features)
- If the user mentioned a specific feature or area, focus on that; otherwise, ensure all completed user-facing features are covered
Step 2: Decide What to Update
- New feature added: Add a new section (or subsection) that describes how to use it, in user-facing steps. Update the “Last updated” date at the top.
- Existing feature changed: Update the matching section so steps and options reflect current behavior. Update “Last updated.”
- Missing coverage: If PROGRESS.md or CHANGELOG shows a user-facing feature that isn’t in USER_GUIDE.md, add it.
- No USER_GUIDE.md: Create it (same content as
/create-user-guidewould produce) and then apply any requested or obvious updates.
Do not add or expand sections for:
- Bug fixes or internal refactors that don’t change how the user uses the app
- Developer-only or build-only changes
Step 3: Edit USER_GUIDE.md
- Add or update the relevant section(s) with:
- Clear heading (e.g. “Voice input”, “Export transactions”)
- Short step-by-step instructions (e.g. “Tap … → …”)
- Any options or tips (e.g. “If you see ‘Low confidence’, review the fields and edit as needed”)
- Update “Last updated” at the top to today’s date
- Keep tone and structure consistent with the rest of the guide (end-user, concise)
- If you add a new top-level flow (e.g. a new screen), add it in a logical order (e.g. after “Home”, before “Settings”)
Step 4: Align With Rules and Feature Workflow
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.
- 6d ago First seen · 65 lines · 0 tokens per session scan A bba1b5f507dd
update-user-guide is a command published in the GitHub repository KaelSensei/MagicAIBuilder (2 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 727 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.