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/kelvinkosbab/AppBootstrapAIWrote 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/kelvinkosbab/appbootstrapai/claude)<a href="https://agentmods.dev/commands/kelvinkosbab/appbootstrapai/claude"><img src="https://agentmods.dev/badge/commands/kelvinkosbab/appbootstrapai/claude/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/kelvinkosbab/appbootstrapai/claude"><img src="https://agentmods.dev/badge/commands/kelvinkosbab/appbootstrapai/claude.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.00019 | $0.00272 |
| Opus 5.5 | $0.00008 | $0.00109 |
| Sonnet 5.5 | $0.00004 | $0.00054 |
| Haiku 4.5 | $0.00002 | $0.00027 |
Grade A, and why
claude 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.
What it actually says
Sync this project with the AppBootstrapAI bundle and audit it.
- Find the bundle (the directory that holds
install.sh), in this order:$APPBOOTSTRAP_BUNDLE, if set.bundle.pathin.claude/.appbootstrap-manifest.json, if that directory still hasinstall.sh. Rungit -C <path> pull --ff-onlyso it's current.- Otherwise clone
bundle.repofrom the manifest (defaulthttps://github.com/kelvinkosbab/AppBootstrapAI) withgit clone --depth 1into a temp directory outside this repo.
- Follow
playbooks/sync-and-audit.mdin that bundle step by step, with BUNDLE set to the bundle path and TARGET set to this repo's root. Skip its "Find the bundle" step; you just did it. - Don't commit, push, or pass
--force,--force-conflicts, or--pruneunless I ask.
Extra instructions: $ARGUMENTS
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 · 16 lines · 19 tokens per session scan A 7e6fe1790c25
claude is a command published in the GitHub repository kelvinkosbab/AppBootstrapAI (7 stars, last pushed today), licensed MIT. It adds 19 tokens to every session and 272 once invoked, about $0.0001 per session on Opus 5.5. 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-10-16.
Other commands, from other repositories
figma-start
A command that prepares a designer's review branch from a developer's GitHub pull request. A pull request is a proposed set of code changes, and a branch is a separate line of project history.
handoff
A handoff command that creates a pull request from a designer's working branch to the developer's branch after design changes are ready for review. A pull request is a request to inspect and merge code changes.
figma-apply
A command that applies changes from a Figma design file to the current design branch, then commits, pushes, and checks the project build. Figma is a tool for creating and sharing interface designs.
feat
Kick off tasks creation for a new feature (4-item interview before invoking pm-agent; an epic-sized requirement routes to phased decomposition, a feature already built on one platform routes to cross-platform parity, a change that touches no endpoint routes to client-only).
feature-build
Build a complete mobile feature from description to running code with E2E tests. Orchestrates 6 phases - planning, implementation, testing, build-fix, quality gate, and verification. Auto-detects platform.
checklist
Generate a custom checklist for the current feature based on user requirements.