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/iris-hep/marketplace/analysis-spec-buildernpx skills add iris-hep/marketplace --skill analysis-spec-buildergit clone --depth 1 https://github.com/iris-hep/marketplaceWrote 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/iris-hep/marketplace/analysis-spec-builder)<a href="https://agentmods.dev/skills/iris-hep/marketplace/analysis-spec-builder"><img src="https://agentmods.dev/badge/skills/iris-hep/marketplace/analysis-spec-builder.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.1 | $0.00057 | $0.00553 |
| Opus 5 | $0.00028 | $0.00277 |
| Sonnet 5 | $0.00011 | $0.00111 |
| Haiku 4.5 | $0.00006 | $0.00055 |
Grade A, and why
analysis-spec-builder 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 5d 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 — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analysis Spec Builder
Workflow
- Read the template from
./assets/analysis-specification-template.md(relative to the this file, in theanalysis-spec-buildingsub directory). - Draft a filled-in specification by replacing all
{{...}}placeholders with concrete content derived from the user's request. - Ask focused follow-up questions for any missing critical details (datasets, selections, histogram definitions, workflow steps, tooling). Keep questions short and grouped by section.
- Iterate revisions until the user confirms the specification is correct.
- Write the final content to
specification.mdunless the user provides a different path.
Drafting Rules
- Replace every
{{...}}placeholder with real content; do not leave placeholders in the final spec. - Keep the tone concise and technical; preserve the template section order.
- If something is unknown, propose a reasonable default and mark it as a question in the next response (do not leave placeholders).
- Preserve any explicit dataset identifiers or analysis names verbatim. Assume the user will use PHYSLITE unless told otherwise, or you know the data isn't available there.
- Use ASCII-only text unless the template already uses non-ASCII (e.g., LaTeX labels inside backticks).
- This is a specification, not a step-by-step plan for implementation of the analysis or plot.
- Details, exactly what version of objects or containers, are not included here. When detailed plans are developed from here, they will be determined. On the other hand, if the user specifies them, then they should be explicitly mentioned.
- The tools section: by default use
servicexwithfunc_adlto fetch data from the source datasets, andawkward,hist, andvectorfor manipulation and histogram fitting. Histograms should be stored as PNG by default. For statistical analysis (if needed) use cabinetry and pyhf.
Follow-up Questions
- Ask only for details needed to proceed (e.g., missing datasets, histogram axes, selections).
- Prefer yes/no or short-answer questions.
- When the user provides new details, update only the affected sections and summarize what changed.
What ships with it
2 files 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.
- 5d ago First seen · 37 lines · 57 tokens per session scan A 2dd6f30c603b
analysis-spec-builder is a skill published in the GitHub repository iris-hep/marketplace (4 stars, last pushed 29d ago), licensed BSD-3-Clause. It adds 57 tokens to every session and 553 once invoked, about $0.0003 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-31.
Other skills, from other repositories
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
matlab
Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.
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…
phylogenetics
Build and analyze phylogenetic trees using MAFFT (multiple alignment), IQ-TREE 2 (maximum likelihood), and FastTree (fast NJ/ML). Visualize with ETE3 or FigTree. For evolutionary analysis, microbial genomics, viral phylodynamics, protein family analysis, and molecular clock studies.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
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…