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 skills/frumu-ai/tandem/data-explore-datanpx skills add frumu-ai/tandem --skill data-explore-datagit clone --depth 1 https://github.com/frumu-ai/tandemWrote 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/skills/frumu-ai/tandem/data-explore-data)<a href="https://agentmods.dev/skills/frumu-ai/tandem/data-explore-data"><img src="https://agentmods.dev/badge/skills/frumu-ai/tandem/data-explore-data.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.00019 | $0.01028 |
| Opus 5 | $0.00010 | $0.00514 |
| Sonnet 5 | $0.00004 | $0.00206 |
| Haiku 4.5 | $0.00002 | $0.00103 |
Grade A, and why
data-explore-data 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 4d 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.
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.
- 4d ago First seen · 120 lines · 19 tokens per session scan A 98be17aa7d75
data-explore-data is a skill published in the GitHub repository frumu-ai/tandem (118 stars, last pushed 29d ago), with no licence file. It adds 19 tokens to every session and 1,028 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 skills, from other repositories
dpf-architecture-review
Use when reviewing or updating a DPF spec, design doc, or implementation plan for architectural alignment.
dpf-decision-via-kernel
Use when an open DPF question has two or more architecturally-distinct options that need kernel scoring.
dpf-verify-substrate-first
Use when tempted to propose a new DPF substrate concept — a table, type, enum value, capability, epic, MCP tool, or agent role.
dpf-elicit-tacit-knowledge
Use when durable DPF knowledge lives only in a human's head — a decision rationale, the why behind a choice, a profession technique, domain context a build depends on.
dpf-evidence-before-diagnosis
Use when about to claim a cause for a DPF symptom without having checked the live DB, status fields, logs, or runtime state.
dpf-ux-fit-review
Use before code or PR handoff for UI-impacting DPF work — any route, viewport, dashboard, metric, card, button, empty state, navigation, or admin/settings/config screen, form, or field. Config forms are UI surfaces.