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/viksant/vibe-coding-tools-content/data-scientistgit clone --depth 1 https://github.com/viksant/vibe-coding-tools-contentWrote 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/viksant/vibe-coding-tools-content/data-scientist)<a href="https://agentmods.dev/agents/viksant/vibe-coding-tools-content/data-scientist"><img src="https://agentmods.dev/badge/agents/viksant/vibe-coding-tools-content/data-scientist.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.00047 | $0.02293 |
| Opus 5 | $0.00023 | $0.01146 |
| Sonnet 5 | $0.00009 | $0.00459 |
| Haiku 4.5 | $0.00005 | $0.00229 |
Grade A, and why
data-scientist 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 256 lines · 47 tokens per session scan A 98f96d289a6e
data-scientist is an agent published in the GitHub repository viksant/vibe-coding-tools-content (44 stars, last pushed 2mo ago), with no licence file. It adds 47 tokens to every session and 2,293 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
testing-strategy
Agent "testing-strategy" from Solvro/ml-mcp, covering testing strategy — solvro mcp, framework & tools, test location, what to test and mcp server / rag pipeline.
architecture-decisions
Agent "architecture-decisions" from Solvro/ml-mcp, covering architecture decisions — solvro mcp, core architecture: four-component system, key patterns to preserve, singleton config and langgraph state machine (rag).
coding-standards
Agent "coding-standards" from Solvro/ml-mcp, covering coding standards — solvro mcp, file structure conventions, import order (enforced by ruff isort), 1. standard library and 2. third-party.
debugging-guide
The project uses Python's standard logging module with structured extras.
git-workflow
Follow Conventional Commits (explicit in .github/agents.md).
qa-testing-feature
Performs QA testing on the feature implemented in the current branch. Reads specs, docs, and API docstrings, creates a QA test plan, executes tests using Playwright against a debug server, and generates a report with found issues. Use after implementing a feature to validate it meets requirements before finalizing a…