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/james-traina/compound-science/submission-guidenpx skills add James-Traina/compound-science --skill submission-guidegit clone --depth 1 https://github.com/James-Traina/compound-scienceWrote 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/james-traina/compound-science/submission-guide)<a href="https://agentmods.dev/skills/james-traina/compound-science/submission-guide"><img src="https://agentmods.dev/badge/skills/james-traina/compound-science/submission-guide.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.00094 | $0.03213 |
| Opus 5 | $0.00047 | $0.01606 |
| Sonnet 5 | $0.00019 | $0.00643 |
| Haiku 4.5 | $0.00009 | $0.00321 |
Grade A, and why
submission-guide 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 6d 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 — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Journal Submission
Reference for the full journal submission lifecycle: pre-submission preparation, journal-specific formatting, referee response strategy, and revision management. Covers conventions for top journals in economics, finance, political science, sociology, marketing, and statistics.
When to Use This Skill
Use when the user is:
- Preparing a manuscript for first submission to an academic journal
- Formatting a paper to meet a specific journal's requirements
- Writing a response letter to referee reports after receiving an R&R
- Managing tracked changes and revision logistics
- Anticipating common referee objections for a particular empirical method
- Writing a cover letter to the editor
Skip when:
- The task is choosing an empirical method (use
causal-inferenceorempirical-playbookskill) - The task is structural estimation implementation (use
structural-modelingskill) - The task is setting up a replication package (use
reproducible-pipelinesskill)
Pre-Submission Checklist
Complete every item before submitting. Missing any one of these is a common reason for desk rejection or delayed processing.
Manuscript
- Title: Concise, informative, no unnecessary jargon. Under 15 words is ideal.
- Abstract: States the question, method, data, and main finding. Respects journal word limit (typically 100-150 words for econ journals).
- JEL codes: 2-4 codes, primary code first. Check https://www.aeaweb.org/econlit/jelCodes.php for current classification.
- Keywords: 3-6 terms not already in the title.
- Introduction: Clearly states contribution in first two paragraphs. Includes a "roadmap" paragraph at the end.
- Literature review: Positions paper relative to 3-5 closest papers. Explains what this paper does that they do not.
- Identification section: Formal statement of assumptions, not just prose. Numbered assumptions preferred.
- Results: Main results first, robustness second. Do not bury the lead.
- Conclusion: No new results. Discuss limitations honestly. Suggest future work briefly.
- References: Every citation in text appears in references and vice versa. Use a bibliography manager (BibTeX/BibLaTeX).
- Anonymization: Remove all author-identifying information. Check PDF metadata, acknowledgments, file paths in code, dataset names that reveal institution.
- Page/word count: Within journal limits. Many journals have strict limits (e.g., AER Papers & Proceedings: 5 pages).
- Spell check and grammar: Run a final pass. Typos in the abstract signal carelessness.
- Agent review: Run the
journal-refereeagent for an adversarial review and theeconometric-revieweragent to audit tables against code output.
What ships with it
3 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.
- 6d ago First seen · 212 lines · 94 tokens per session scan A c44f1de84acd
submission-guide is a skill published in the GitHub repository James-Traina/compound-science (13 stars, last pushed 5mo ago), licensed MIT. It adds 94 tokens to every session and 3,213 once invoked, about $0.0005 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
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…