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 skills add vixues/LeAgent --skill data-analyzergit clone --depth 1 https://github.com/vixues/LeAgentWrote 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/vixues/leagent/data-analyzer)<a href="https://agentmods.dev/skills/vixues/leagent/data-analyzer"><img src="https://agentmods.dev/badge/skills/vixues/leagent/data-analyzer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/vixues/leagent/data-analyzer"><img src="https://agentmods.dev/badge/skills/vixues/leagent/data-analyzer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.1 | $0.00039 | $0.00390 |
| Opus 5.5 | $0.00016 | $0.00156 |
| Sonnet 5.5 | $0.00008 | $0.00078 |
| Haiku 4.5 | $0.00004 | $0.00039 |
Grade A, and why
data-analyzer 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 1mo 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
Data Analysis
You are assisting with data analysis tasks. Follow these guidelines.
Analysis Workflow
- Understand the data: identify columns, types, ranges, and any quality issues.
- Clean the data: handle missing values, outliers, and format inconsistencies.
- Analyze: compute relevant statistics (counts, sums, averages, distributions).
- Compare: when multiple datasets or time periods exist, provide comparative analysis.
- Summarize: present findings clearly with key metrics highlighted.
Statistical Methods
- Use descriptive statistics (mean, median, mode, std dev) as a baseline.
- Identify trends and patterns — year-over-year, month-over-month, category breakdowns.
- Flag outliers and anomalies with context about their potential significance.
- For comparisons, compute both absolute and percentage differences.
Output Formats
- Summary: Concise paragraph with key findings and numbers.
- Table: Structured tabular format for detailed breakdowns.
- Report: Sectioned report with executive summary, methodology, findings, and recommendations.
Best Practices
- Always state the sample size and time range of the data being analyzed.
- Round numbers appropriately for readability (2 decimal places for percentages).
- When making comparisons, ensure the baseline and comparison period are clear.
- Distinguish between correlation and causation in findings.
- Provide actionable recommendations when the analysis supports them.
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.
- 1mo ago First seen · 44 lines · 39 tokens per session scan A 9bdb480247eb
data-analyzer is a skill published in the GitHub repository vixues/LeAgent (236 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 39 tokens to every session and 390 once invoked, about $0.0002 per session on Opus 5.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
rn-device-control
This skill should be used when the user asks to "control the simulator", "take a screenshot", "boot the emulator", "install the app", "read UI hierarchy", "manage device state", "open a deep link", "grant permissions", "stream native logs", "disable animations", "change device locale", or needs guidance on xcrun…
rn-feature-development
This skill should be used when building any new feature in a React Native or Expo app, or when the $rn-dev-agent:rn-feature-dev command runs. Triggers on "build a feature", "add X to the app", "implement Y", "create a new screen", "rn-feature-dev", "feature development", "build me X", "add a screen", "wire up this…
using-rn-dev-agent
Entry point for the rn-dev-agent plugin. Maps user intent to the right command, agent, or skill. Use at the START of any React Native development conversation. Triggers on "I want to build", "build a feature", "add a feature to the app", "test this", "something is broken", "fix the crash", "help with my React Native…
rn-testing
This skill should be used when the user asks to "write a Maestro test", "create E2E flows", "add testIDs", "run UI tests", "run E2E tests", "verify a feature works", "test my screen", "set up maestro-runner", "mock network requests", "inspect store state", "write test assertions", or needs guidance on test timing…
rn-workflow
Validate and establish the proven rn-dev-agent operating sequence before a real React Native journey — read project instructions and the declared package manager, inventory sessions/Metro/devices read-only, establish one exclusive simulator/emulator via typed session actions, apply and verify package integration and…
capturing-proof
This skill should be used when the user asks to "capture proof", "record a demo of this feature", "make a video showing it works", "record the flow for the PR", "generate a PR body", "capture screenshots for the PR", "proof-capture", or when a verified feature needs PR-ready proof artifacts (video + numbered…