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/armanzeroeight/fastagent-plugins/validate-dbtgit clone --depth 1 https://github.com/armanzeroeight/fastagent-pluginsWhat 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.00010 | $0.00408 |
| Opus 5 | $0.00005 | $0.00204 |
| Sonnet 5 | $0.00002 | $0.00082 |
| Haiku 4.5 | $0.00001 | $0.00041 |
Grade A, and why
validate-dbt 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.
What it actually says
Validate dbt Project
Context
- dbt version: !
dbt --version 2>&1 || echo "dbt not installed" - Current directory: !
pwd - dbt project: !
ls dbt_project.yml 2>&1 && echo "Found" || echo "Not in dbt project" - Models: !
find models -name "*.sql" 2>&1 | head -10 || echo "No models found"
Your Task
Validate dbt project configuration, compile models, and run tests.
Arguments
$1: Model name to validate (optional, validates all if not provided)
Steps
-
Validate project configuration
dbt debug -
Compile models
dbt compile --select $1 -
Run tests
dbt test --select $1 -
Check documentation
- Verify all models have descriptions
- Check column documentation
- Ensure tests are defined
-
Provide recommendations
- Missing tests
- Undocumented models
- Performance improvements
- Best practice violations
Output Format
## dbt Validation Results
**Project:** [project-name]
**Models Checked:** [count]
### Configuration
✓ Passed / ✗ Failed
### Compilation
✓ Passed / ✗ Failed
[Compilation errors if any]
### Tests
✓ Passed / ✗ Failed
- Total: [count]
- Passed: [count]
- Failed: [count]
### Documentation Coverage
- Models documented: [count]/[total]
- Columns documented: [count]/[total]
### Recommendations
1. [Recommendation]
2. [Recommendation]
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 · 81 lines · 10 tokens per session scan A d61708683534
validate-dbt is a command published in the GitHub repository armanzeroeight/fastagent-plugins (29 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 408 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 commands, from other repositories
MIGRATE_DESIGN
Design doc for the migration tool PR. Author: Sol ([email protected]). Co-authored-by: wakesync.
tech-debt
Run bun run check:fix and then bunx knip and identify unused files and functions to refactor the project and simplify. Look at the deprecated features and confirm with the user to delete them. Look at the dependencies and remove the ones that are not needed based on knip results.
commit
Act as a senior software engineer to commit changes to the repository in non-interactive modes ONLY, using the following template.
aidd-churn
Rank files by hotspot score to identify prime candidates for refactoring before PR review.
workflow-router
Route to the appropriate spec-driven workflow command based on the user's intent.
git
Git operations with intelligent commit messages and workflow optimization.