Borrowing it
Nothing to install: this file belongs to AndreaBozzo/dataprof. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/AndreaBozzo/dataprof/master/.github/skills/code-review/SKILL.mdgit clone --depth 1 https://github.com/AndreaBozzo/dataprofWrote 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/andreabozzo/dataprof/code-review)<a href="https://agentmods.dev/skills/andreabozzo/dataprof/code-review"><img src="https://agentmods.dev/badge/skills/andreabozzo/dataprof/code-review/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/andreabozzo/dataprof/code-review"><img src="https://agentmods.dev/badge/skills/andreabozzo/dataprof/code-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 98 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00084 | $0.01912 |
| Opus 5.5 | $0.00034 | $0.00765 |
| Sonnet 5.5 | $0.00017 | $0.00382 |
| Haiku 4.5 | $0.00008 | $0.00191 |
Grade A, and why
code-review 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reviewing dataprof
dataprof is a local, deterministic data profiler: a Rust workspace with PyO3
Python bindings. It reports on data and never transforms, cleans, or moves it.
The release surface is Rust library crates plus Python wheels; there is no CLI
binary. Standing repository conventions live in
AGENTS.md — this file is only about what to look for when
reviewing a change.
The bug class that costs most here is rarely a local mistake inside the diff. It is a change that is correct where it was made and inconsistent with something that was not touched: a sibling input path, a second predicate for the same concept, or a number quoted in documentation. Read the diff, then go look at the places it should have changed too.
1. The same input must produce the same numbers everywhere
Profile numbers must be identical regardless of which engine or input path produced them. A diff that changes one path and leaves its siblings alone is the most common real defect, and it passes every test that only exercises the path it touched.
When a diff touches any of these, check the others for the same behaviour:
| path | file |
|---|---|
| CSV parser (shared by file and reader entry points) | crates/dataprof-csv/src/lib.rs |
| JSON / JSONL parser | crates/dataprof-json/src/lib.rs |
| Parquet | crates/dataprof-parquet/src/arrow_profiler.rs, record_batch_analyzer.rs |
| incremental streaming engine | crates/dataprof-engines/src/streaming/incremental.rs |
| async streaming reader | crates/dataprof-engines/src/streaming/async_reader.rs |
| memory-mapped reader | crates/dataprof-engines/src/streaming/memmap.rs |
| columnar (Arrow) engine | crates/dataprof-engines/src/columnar/mod.rs |
partial analysis (infer_schema, analyze_structure, quick_row_count) |
crates/dataprof-partial/src/lib.rs |
| database connectors | crates/dataprof-db/ |
| shared profile construction | crates/dataprof-runtime/src/profile_builder.rs |
Flag it when a fix lands in one of these and the same input would still be answered differently by another. Check both raw attributes and the serialized report, since a diff can bring one into line and leave the other out.
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.
- 2mo ago First seen · 153 lines · 84 tokens per session scan A 746ee6d599a1
code-review is a skill published in the GitHub repository AndreaBozzo/dataprof (31 stars, last pushed today), licensed MIT. It adds 84 tokens to every session and 1,912 once invoked, about $0.0003 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
review-respond
Respond to all pending review comments on the current PR — fetch comments, apply fixes, verify accuracy, test, commit, and reply. Use when addressing Copilot reviews, GitHub PR reviews, or any batch of review feedback.
fast-rust
Practical guidance for writing, refactoring, and reviewing fast, reliable, and maintainable Rust code.
feature-flag-conventions
Cargo features: shared otel/mcp/allocator contract, then Xberg's ORT-free targets, aggregates, PDF backend, parity guard. Use when editing [features].
tuicr
Use tuicr's review CLI to read and add comments in active TUI review sessions, and launch tuicr in cmux, tmux, Zellij, or Herdr when a user needs an interactive review pane.
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.
high-stakes-analytics-decision-lab
Build or review source-backed descriptive, diagnostic, predictive, and prescriptive analysis for consequential decisions. Use when an agent must profile and safely prepare uploaded data, turn a real dataset or research question into a reproducible study, investigate drivers without overstating causality, validate a…