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 skills add ShaishavMaisuria/research-paper-lifecycle-skills --skill match-stylegit clone --depth 1 https://github.com/ShaishavMaisuria/research-paper-lifecycle-skillsWrote 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/shaishavmaisuria/research-paper-lifecycle-skills/match-style)<a href="https://agentmods.dev/skills/shaishavmaisuria/research-paper-lifecycle-skills/match-style"><img src="https://agentmods.dev/badge/skills/shaishavmaisuria/research-paper-lifecycle-skills/match-style/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/shaishavmaisuria/research-paper-lifecycle-skills/match-style"><img src="https://agentmods.dev/badge/skills/shaishavmaisuria/research-paper-lifecycle-skills/match-style.svg" alt="Reviewed on agentmods" width="80" 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.00204 | $0.01413 |
| Opus 5 | $0.00102 | $0.00707 |
| Sonnet 5 | $0.00041 | $0.00283 |
| Haiku 4.5 | $0.00020 | $0.00141 |
Grade A, and why
match-style 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 12d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Match Style
Aligns a draft to a target voice without touching its substance. Three modes, combinable:
- author voice — match the researcher's own prior papers (terminology, rhythm, hedging, structure) so a new draft reads as theirs.
- venue register — match the published style of the target venue (via
study-exemplars). - co-author merge — make a multi-author draft read in one consistent voice instead of a patchwork.
This is part of the acceptance-maximizing toolkit, alongside polish-prose (de-AI-ify + tighten), benchmark-paper (venue-fit score), simulate-reviewers (content critique), and preflight-check (desk-reject defects). Be honest with the user: no rewrite guarantees acceptance. What style alignment buys is consistency, venue fit, and readability — real but bounded contributors to how a paper is received.
When to use vs. polish-prose
polish-prosefixes objective problems (AI tells, wordiness, inconsistent terms) against general/venue norms.match-stylealigns to a specific target voice you provide (your corpus and/or venue exemplars). Runpolish-prosefirst to clean, thenmatch-styleto align.
Inputs
- The draft:
.tex/.md/ text. - For author voice: paths to the author's own prior papers (
.tex/.pdf/.txt). These must be the author's own work — see Guardrails. - For venue register: the target venue id →
venues/profile →study-exemplarscorpus. - Optional: a glossary of preferred terms/acronyms.
Process
- Build the style signature of the target.
- Author voice: run
python3 scripts/style_signature.py --corpus <files...> --out author.json. It measures terminology frequency, mean/var sentence length, hedging density, connective usage (however/moreover/thus…), passive-voice rate, citation density, section-heading vocabulary. - Venue register: run the same over the
study-exemplarscorpus (open-access only) →venue.json.
- Author voice: run
- Profile the draft the same way:
python3 scripts/style_signature.py --corpus <draft> --out draft.json. - Diff draft vs target(s):
python3 scripts/style_signature.py --compare draft.json --against author.json [venue.json] --out style-gap.md. This reports where the draft deviates (e.g. "you use 'we propose' 0×; your prior papers average 3×", "hedging 2× higher than venue exemplars"). - Surface conflicts. When author voice and venue register disagree (e.g. your habitual first-person vs a venue that prefers passive), present the trade-off — do not silently pick one.
- Align the draft section by section, guided by
style-gap.mdand the rewrite norms in references/style-dimensions.md. Preserve every number, result, claim, and citation verbatim. Keep a change log. - Verify nothing substantive moved: re-run
verify-citationsif references were near edits; diff claims/numbers before/after.
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.
- 12d ago First seen · 60 lines · 204 tokens per session scan A e49d18af91d8
match-style is a skill published in the GitHub repository ShaishavMaisuria/research-paper-lifecycle-skills (42 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 204 tokens to every session and 1,413 once invoked, about $0.0010 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
aaai-reproducibility
Use when strengthening an AAAI paper's reproducibility checklist (placed after references), experimental traceability, seed and hyperparameter reporting, compute and cost disclosure, dataset access and licensing, code/data ZIP readiness, and the claim-to-evidence map that Phase-1 reviewers use to judge rigor across…
aaai-submission
Use when auditing an AAAI main technical track submission for OpenReview readiness, double-blind anonymity, page limits, reproducibility checklist, supplementary material, author limits, multiple-submission policy, and AAAI AI-use policy compliance.
aaai-topic-selection
Use when deciding whether a project is a strong AAAI submission across its broad AI scope, should be reframed or routed to a dedicated track such as AI for Social Impact or AI Alignment, or should instead go to IJCAI, NeurIPS, ICML, ICLR, AISTATS, UAI, ACL, CVPR, KDD, CHI, ICRA, or another specialist venue.
acl-author-response
Use when drafting an ACL author response inside an ACL Rolling Review cycle on OpenReview, covering the response window before meta-review, reviewer discussion dynamics, score-change strategy, flagging review issues to the area chair, anonymity rules, and deciding between responding now versus revising for a later ARR…
acl-camera-ready
Use when preparing an accepted ACL main-conference or Findings paper for camera-ready, covering the extra content page, de-anonymization and acknowledgements, AI-assistance disclosure, keeping the Limitations section, ACL Anthology metadata and CC BY 4.0 publication, meta-review-driven edits, and presentation-mode…
acl-experiments
Use when designing or auditing experiments for an ACL paper, covering tuned LLM baselines, multi-dataset and multilingual evaluation, statistical significance and variance, human evaluation with agreement reporting, contamination and prompt-sensitivity controls, ablations, and error-analysis expectations in NLP…