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 skills/bubblelabai/bubblelab/commitnpx skills add bubblelabai/BubbleLab --skill commitgit clone --depth 1 https://github.com/bubblelabai/BubbleLabWhat 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.00018 | $0.00620 |
| Opus 5 | $0.00009 | $0.00310 |
| Sonnet 5 | $0.00004 | $0.00124 |
| Haiku 4.5 | $0.00002 | $0.00062 |
Grade A, and why
commit 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 yesterday.
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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Skill (OSS Repo)
Create a well-formed conventional commit with automatic version bumping.
Step 1: Analyze Changes
Run these commands in parallel:
git status
git diff --staged
git diff
git log --oneline -5
Step 2: Bump Package Versions
Always run the version bump before committing:
pnpm run bump-versions
This increments the patch version of all publishable packages (bubble-core, bubble-runtime, shared-schemas, etc.).
Stage the bumped package.json files along with your other changes.
Step 3: Stage Files
Stage relevant files. Be selective:
- DO NOT stage
.env, credentials, or secret files - DO NOT stage unrelated changes
- Prefer
git add <specific-files>overgit add -A - DO include the bumped
packages/*/package.jsonfiles
Step 4: Typecheck
Run typecheck to ensure no type errors before committing:
pnpm run typecheck
If typecheck fails, fix the errors before proceeding. Do NOT commit with type errors.
Step 5: Write Commit Message
Follow conventional commits format:
type(scope): concise description
[optional body]
Co-Authored-By: Claude Opus 4.6 <[email protected]>
Types: feat, fix, chore, refactor, docs, test, perf, enhance
Scope: Optional, use for specific modules (e.g., feat(confluence): ..., fix(google-drive): ...)
Rules:
- Description is lowercase, no period at end
- Focus on the "why" not the "what"
- Keep first line under 72 characters
- If the user provided a message via
$ARGUMENTS, use it (adjusting format if needed)
Step 6: Commit
Use a HEREDOC for proper formatting:
git commit -m "$(cat <<'EOF'
type(scope): description
EOF
)"
IMPORTANT:
- NEVER amend existing commits unless explicitly asked
- NEVER use
--no-verifyunless explicitly asked - NEVER push unless explicitly asked
- If a pre-commit hook fails, fix the issue and create a NEW commit
Step 7: Verify & Remind
Run git status after committing to confirm success.
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.
- yesterday First seen · 104 lines · 18 tokens per session scan A d707a0237f9e
commit is a skill published in the GitHub repository bubblelabai/BubbleLab (1,094 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 18 tokens to every session and 620 once invoked, about $0.0001 per session on Opus 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-08-30.
Other skills, from other repositories
golang-testing
Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI…
golang-dependency-injection
Comprehensive guide for dependency injection (DI) in Golang. Covers why DI matters (testability, loose coupling, separation of concerns, lifecycle management), manual constructor injection, and DI library comparison (google/wire, uber-go/dig, uber-go/fx, samber/do). Use this skill when designing service architecture…
golang-graphql
Implements GraphQL APIs in Golang using gqlgen or graphql-go. Apply when building GraphQL servers, designing schemas, writing resolvers, handling subscriptions, or integrating GraphQL with existing Go HTTP services. Also apply when the codebase imports github.com/99designs/gqlgen or github.com/graph-gophers/graphql-go.
golang-pkg-go-dev
Golang package and module documentation and exploration via godig, a pkg.go.dev API client (CLI + MCP server) — package docs, API references, symbols, code examples, available versions, importers (who imports a package), licenses, and known vulnerabilities. Read-only, no auth. Use for looking up any Go/Golang…
golang-security
Security best practices and vulnerability prevention for Golang. Covers injection (SQL, command, XSS), cryptography, filesystem safety, network security, cookies, secrets management, memory safety, and logging. Apply when writing, reviewing, or auditing Go code for security, or when working on any risky code involving…
golang-structs-interfaces
Golang struct and interface design patterns — composition, embedding, type assertions, type switches, interface segregation, dependency injection via interfaces, struct field tags, and pointer vs value receivers. Use this skill when designing Go types, defining or implementing interfaces, embedding structs or…