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/appleweiping/weiping_wiki/paper-writenpx skills add appleweiping/WEIPING_WIKI --skill paper-writegit clone --depth 1 https://github.com/appleweiping/WEIPING_WIKIWrote 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/appleweiping/weiping_wiki/paper-write)<a href="https://agentmods.dev/skills/appleweiping/weiping_wiki/paper-write"><img src="https://agentmods.dev/badge/skills/appleweiping/weiping_wiki/paper-write.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.00061 | $0.00963 |
| Opus 5 | $0.00030 | $0.00481 |
| Sonnet 5 | $0.00012 | $0.00193 |
| Haiku 4.5 | $0.00006 | $0.00096 |
Grade A, and why
paper-write 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Paper Write
Write a top-venue paper. Every sentence must be backed by evidence or clearly marked as motivation/intuition.
Decision Gate
Before running:
-
refine-logs/AUDIT_REPORT.mdexists with verdict PASS or CONDITIONAL PASS -
refine-logs/RESEARCH_QUESTION.mdexists -
refine-logs/EXPERIMENT_PLAN.mdexists - Results with
paper_resultevidence label are available - Target venue is identified (page limit, format, deadline)
Phase 1 — Paper Skeleton
Create the LaTeX structure:
paper/
main.tex # Master file
sections/
abstract.tex
introduction.tex
related-work.tex
method.tex
experiments.tex
results.tex
analysis.tex
conclusion.tex
figures/
tables/
references.bib
Define the narrative arc:
- Hook: What's the problem? Why should anyone care?
- Gap: What's missing in current approaches?
- Contribution: What do we do differently? (1-3 bullet points)
- Evidence: How do we prove it works?
- Impact: What does this enable?
Phase 2 — Section Drafting (in order)
Method (write first — it's the core)
- Algorithm description with mathematical notation
- Architecture diagram (describe for figure generation)
- Complexity analysis
- Connection to theory (if applicable)
Experiments
- Experimental setup (datasets, metrics, baselines, implementation details)
- Main results table (from audit-approved
paper_resultdata) - Ablation studies
- Analysis (why does it work / when does it fail)
Introduction
- Motivating example or statistic
- Problem statement
- Brief description of approach
- Summary of results
- Contribution list (3 bullets max)
Related Work
- Organize by theme, not chronologically
- Position our work clearly relative to each group
- Be fair to prior work — acknowledge strengths before noting gaps
Abstract (write last)
- 150-250 words
- Problem → Approach → Results → Impact
- Include one concrete number (best improvement)
Phase 3 — Evidence-Claim Alignment
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 · 123 lines · 61 tokens per session scan A 9165ce676436
paper-write is a skill published in the GitHub repository appleweiping/WEIPING_WIKI (122 stars, last pushed 9d ago), licensed MIT. It adds 61 tokens to every session and 963 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-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…
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…
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.
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…