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 agents/ulises-jeremias/agentic-workstation/data-validategit clone --depth 1 https://github.com/ulises-jeremias/agentic-workstationWrote 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/agents/ulises-jeremias/agentic-workstation/data-validate)<a href="https://agentmods.dev/agents/ulises-jeremias/agentic-workstation/data-validate"><img src="https://agentmods.dev/badge/agents/ulises-jeremias/agentic-workstation/data-validate.svg" alt="Measured on agentmods" 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 | $0.00022 | $0.00105 |
| Opus 5 | $0.00011 | $0.00053 |
| Sonnet 5 | $0.00004 | $0.00021 |
| Haiku 4.5 | $0.00002 | $0.00011 |
Grade A, and why
data-validate 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 3d 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
You are the Data Validation specialist.
Responsibilities:
- Delegate dbt work to
dbt-validationand Snowflake checks tosnowflake-validation. - Follow repo
AGENTS.mdand documented commands (Makefile/CI). - Never claim validation passed without credentials and observed outputs.
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.
- 3d ago First seen · 13 lines · 22 tokens per session scan A 74270df359e9
data-validate is an agent published in the GitHub repository ulises-jeremias/agentic-workstation (2 stars, last pushed 7d ago), licensed MIT. It adds 22 tokens to every session and 105 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 agents, from other repositories
nw-data-engineer
Use for database technology selection, data architecture design, query optimization, schema design, security implementation, and governance guidance. Provides evidence-based recommendations across RDBMS and NoSQL systems.
debugger
Debugging specialist for errors and test failures. Use when encountering build errors, runtime exceptions, test failures, or unexpected behavior. Invoke with /debugger to investigate issues.
ccf-debugger
Investigates ONE assigned root-cause hypothesis/branch — follows the correlation ID across logs, queries the DB read-only to verify, returns evidence + judgment. Does NOT fix code. Used by /ccf:fix to isolate one investigation branch without flooding the main context.
namba-data-engineer
Use this role when schema, migration, pipeline, analytics, or transformation work is part of the change. State effect: workspace-write. Edit only files assigned by the main session.
database-reviewer
Reviews database schema design, migration safety, indexing strategy, query patterns, and data integrity. Spawn when user asks to "database review", "check schema design", "review migrations", or "audit database".
learnship-solution-writer
Analyzes a recently solved problem and produces a structured solution document for .planning/solutions/ with YAML frontmatter. Spawned by compound workflow on platforms with subagent support.