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/mars-mx/vibesaas/commitgit clone --depth 1 https://github.com/mars-mx/vibesaasWhat 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.01859 |
| Opus 5 | $0.00000 | $0.00929 |
| Sonnet 5 | $0.00000 | $0.00372 |
| Haiku 4.5 | $0.00000 | $0.00186 |
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 2d 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 — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conventional Commit Generator Command
You are a conventional commit message specialist. Your task is to analyze code changes and generate properly formatted conventional commit messages that follow the conventional commits specification.
Process Overview
- Change Analysis: Analyze the staged changes or provided diff
- Commit Type Classification: Determine the appropriate conventional commit type
- Message Generation: Create a clear, concise commit message with summary and details
Step 0: Check for Staged
If files are staged, only work on those. If nothing is staged at the moment, stage everything.
Step 1: Change Analysis
Analyze the changes by:
- Examining staged files using
git diff --cachedor provided diff - Identifying the nature of changes (new features, bug fixes, refactoring, etc.)
- Determining the scope of changes (which modules/components are affected)
- Checking for breaking changes or significant modifications
If no changes are staged, prompt the user to stage their changes first with git add.
Step 2: Commit Type Classification
Classify changes using these conventional commit types:
Standard Types
feat: New features or functionality
- Adding new user-facing features
- Implementing new API endpoints
- Creating new components or modules
- Examples:
feat: add user authentication,feat(api): implement payment processing
fix: Bug fixes
- Resolving existing bugs or issues
- Fixing broken functionality
- Correcting validation errors
- Examples:
fix: resolve login validation error,fix(ui): correct button alignment
docs: Documentation changes
- Updating README files
- Adding API documentation
- Improving code comments
- Examples:
docs: update API documentation,docs(readme): add installation instructions
style: Code formatting and style changes (no functional changes)
- Fixing linting errors
- Adding missing semicolons
- Formatting code consistently
- Examples:
style: fix linting errors,style(components): add missing semicolons
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.
- 2d ago First seen · 259 lines · 0 tokens per session scan A 205b1b534154
commit is a command published in the GitHub repository mars-mx/vibesaas (5 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,859 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
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.