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/duonginspace/claude-code-databricks-ml/commitgit clone --depth 1 https://github.com/duonginspace/claude-code-databricks-mlWhat 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.00014 | $0.00699 |
| Opus 5 | $0.00007 | $0.00349 |
| Sonnet 5 | $0.00003 | $0.00140 |
| Haiku 4.5 | $0.00001 | $0.00070 |
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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
- Current git status: !
git status - Current git diff (staged and unstaged changes): !
git diff HEAD - Current branch: !
git branch --show-current - Recent commits: !
git log --oneline -10
Your task
Based on the above changes, create a single git commit following the Conventional Commits 1.0.0 specification.
Commit message format
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
Rules
-
Choose the correct type based on the nature of the changes:
feat— a new feature (correlates with MINOR in SemVer)fix— a bug fix (correlates with PATCH in SemVer)build— changes to build system or external dependencieschore— maintenance tasks that don't modify src or test filesci— CI configuration changesdocs— documentation only changesstyle— formatting, whitespace, semicolons (no code logic change)refactor— code change that neither fixes a bug nor adds a featureperf— performance improvementtest— adding or correcting testsrevert— reverting a previous commit
-
Scope (optional): a noun in parentheses describing the section of the codebase, e.g.,
feat(parser):,fix(api):. -
Description: immediately after the colon and space. Short summary of the changes in imperative mood, lowercase, no period at end.
-
Body (optional): one blank line after the description. Free-form, may consist of multiple paragraphs. Explain the why, not the what.
-
Footer (optional): one blank line after the body. Use
BREAKING CHANGE: <description>for breaking API changes. Other footers follow git trailer format (Reviewed-by:,Refs: #123, etc.). -
Breaking changes: append
!after the type/scope AND/OR add aBREAKING CHANGE:footer. Example:feat!: drop support for Node 6orfeat(api)!: rename endpoint. -
Keep the first line under 72 characters.
-
Match the commit style of recent commits in the repository when choosing scope granularity.
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 · 73 lines · 14 tokens per session scan A 3b66efdfc3d9
commit is a command published in the GitHub repository duonginspace/claude-code-databricks-ml (5 stars, last pushed 5mo ago), licensed MIT. It adds 14 tokens to every session and 699 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-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.