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/aws-neuron/neuron-agentic-development/neuron-explorer-profile-schemanpx skills add aws-neuron/neuron-agentic-development --skill neuron-explorer-profile-schemagit clone --depth 1 https://github.com/aws-neuron/neuron-agentic-developmentWrote 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/aws-neuron/neuron-agentic-development/neuron-explorer-profile-schema)<a href="https://agentmods.dev/skills/aws-neuron/neuron-agentic-development/neuron-explorer-profile-schema"><img src="https://agentmods.dev/badge/skills/aws-neuron/neuron-agentic-development/neuron-explorer-profile-schema.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.00133 | $0.03807 |
| Opus 5 | $0.00067 | $0.01903 |
| Sonnet 5 | $0.00027 | $0.00761 |
| Haiku 4.5 | $0.00013 | $0.00381 |
Grade A, and why
neuron-explorer-profile-schema scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -X POST http://localhost:3002/api/v1/db/${PROFILE_NAME}/_search \ How it starts
The opening of the file, as written. The whole thing — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Neuron Explorer Profile Schema
The neuron-explorer profile schema is the OpenAPI-typed contract for the
parquet tables produced when a profile is ingested. This skill is a starting
point — the schema evolves with each neuron-explorer release, so always
fetch the version that matches your installed CLI before relying on field
names or types.
When to use this skill
- You need to know what tables exist and what each one represents.
- You need to look up fields, units, types, or enum values for a specific table.
- You need to find which fields relate to a topic (matmuls, source lines, HBM, semaphores, etc.).
- You want to understand where the values in a table come from (which input artifact, which producer in the Neuron stack).
For running queries against an ingested profile, use
/neuron-nki-profile-querying. For capturing a profile, use
/neuron-nki-profiling.
Profile output format guidance: prefer Parquet over JSON
When using neuron-explorer view avoid using the legacy --output-format json
because it is disorganized, incomplete, poorly documented, and not scalable.
The default output format is Parquet. Parquet is a columnar and efficiently encoded
format, so producing/manipulating/analyzing Parquet is fast even for large profiles.
The neuron-explorer UI reads from the same Parquet, so what you query
matches what the UI shows.
Also, note that --output-format summary-json maps to the data in the
Summary.parquet table — same fields, same values. Prefer the default, full Parquet
output over summary-json because it takes about the same time to produce
and contains more information.
Get the schema for your installed neuron-explorer
The schema is embedded in the neuron-explorer binary. To dump it:
neuron-explorer --show-profile-schema | \
scripts/write_profile_schema_to_separate_yaml_files.py --out ./schema
--show-profile-schema prints all per-table YAML files concatenated with
--- separators. The bundled helper script splits the stream into one file
per table, naming each by the top-level YAML key (Instruction.yaml,
Summary.yaml, etc.). The OpenAPI root document is written to
schema.yaml.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 270 lines · 133 tokens per session scan A c5c6df8aa237
neuron-explorer-profile-schema is a skill published in the GitHub repository aws-neuron/neuron-agentic-development (56 stars, last pushed 15d ago), licensed Apache-2.0. It adds 133 tokens to every session and 3,807 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
exploratory-data-analysis
Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…
nature-statistics
Audit, revise, or draft manuscript statistical reporting for Nature / high-impact journal submissions. Use when the user asks to check statistical analysis sections, p values, confidence intervals, sample size, biological versus technical replicates, randomization, blinding, multiple-comparison correction, model…
evaluating-with-leakage-gates
Evaluate an OpenMed de-identification or clinical NER model against the leakage-first release gates G1a through G8, which gate releases on residual PHI leakage rather than on F1. Use when the user wants to run the OpenMed eval harness on a synthetic golden set, decide whether a de-id model is RELEASABLE or…
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…
mixed-precision
Use FP16/BF16 mixed precision to accelerate training and reduce memory. Use when optimizing GPU performance.
indication-dossier
Build a source-backed biomedical indication dossier. Use when a research task asks for disease biology, target rationale, patient segmentation, biomarkers, trials, drugs, competitive landscape, or translational evidence.