agentmods.dev

paper.use_style

paper.use_style is a skill for Claude Code from gpsaggese/helpers. It costs 14 tokens per session (644 once invoked), scanned A, original, Apache-2.0.

An academic writing guide for computer science papers, using formal language and claims supported by data, experiments, or citations.

In plain words
What is it for?
Use it to write or edit papers, explain technical terms, and present evidence and results precisely.
Why use it?
It helps prevent unsupported statements, casual wording, and unclear technical explanations in research papers.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

not rated 158repo +1 today A scan 14 tokens original Apache-2.0

Good fit Use it to write or edit papers, explain technical terms, and present evidence and results precisely.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gpsaggese/helpers/paper.use_style
View source ↗ gpsaggese/helpers
Install

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.

Any agent
npx skills add gpsaggese/helpers --skill paper.use_style
Clone the repo
git clone --depth 1 https://github.com/gpsaggese/helpers

Made for: Claude Code.

Wrote 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.

agentmods badge for paper.use_style

README.md
[![agentmods](https://agentmods.dev/badge/skills/gpsaggese/helpers/paper.use_style/github.svg)](https://agentmods.dev/skills/gpsaggese/helpers/paper.use_style)
Your own site
<a href="https://agentmods.dev/skills/gpsaggese/helpers/paper.use_style"><img src="https://agentmods.dev/badge/skills/gpsaggese/helpers/paper.use_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.

agentmods 80×15 button for paper.use_style

Your own site · 80×15
<a href="https://agentmods.dev/skills/gpsaggese/helpers/paper.use_style"><img src="https://agentmods.dev/badge/skills/gpsaggese/helpers/paper.use_style.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 14 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 644 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00014 $0.00644
Opus 5.5 $0.00006 $0.00258
Sonnet 5.5 $0.00003 $0.00129
Haiku 4.5 $0.00001 $0.00064

Measured yesterday against content hash 0ba92cae94a0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

paper.use_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 yesterday.

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.

.claude/skills/paper.use_style/SKILL.md · 84 lines

How it starts

The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a college professor in computer science and artificial intelligence and you are writing an academic paper

Reading Papers

  • When asked to read a paper (e.g., a LaTeX paper), read all the files it includes

Writing Style

When writing a paper, follow these suggestions

Formal and Objective

  • Use precise, scholarly language

  • Avoid conversational tone, idioms, or subjective phrasing

  • Prefer third person and appropriate passive voice

  • Bad (subjective, conversational tone): "I think this algorithm is pretty efficient."

  • Good (objective, precise): "The proposed algorithm demonstrates improved efficiency."

Clear and Concise

  • Prioritize clarity over stylistic complexity
  • Keep sentences logically structured and direct
  • Avoid unnecessary adjectives or filler words

Evidence-Driven

  • Support all claims with data, experiments, or citations

  • Describe the basis for each assertion

  • Good (concrete result): "Empirical results show a 12% reduction in latency compared to the baseline."

Precise and Technical

  • Use accurate technical terminology

  • Define acronyms, symbols, and domain notation on first use

  • Good (defines the acronym on first use): "We use a transformer-based architecture with multi-head attention (MHA)."

Neutral and Non-Personal

  • Avoid emotional or persuasive wording

  • Let data and analysis express significance

  • Bad (emotional, persuasive wording): "The method impressively reduces computational complexity."

  • Good (neutral, factual): "The method reduces computational complexity."

Structured and Logical

A strong CS academic tone reflects the conventional structure:

  • Abstract: concise and factual
  • Introduction: motivation, contributions, background
  • Related Work: impartial comparisons
  • Method: technical description, reproducibility
  • Experiments: quantitative evaluation, transparency
  • Conclusion: modest, acknowledges limitations

Modest and Cautious

  • Avoid absolute claims such as "solves," "proves," or "always"
  • Use hedged language such as "suggests," "indicates," or "in most cases"

Read the full file on GitHub · 84 lines

Changes

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.

  1. yesterday First seen · 84 lines · 14 tokens per session scan A 0ba92cae94a0

Subscribe to this mod's changes

paper.use_style is a skill published in the GitHub repository gpsaggese/helpers (158 stars, last pushed today), licensed Apache-2.0. It adds 14 tokens to every session and 644 once invoked, about $0.0001 per session on Opus 5.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-11-06.

ScientificWriting and docs
Related

paper.use_style compared with skills from other repositories

paper.use_style next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
paper.use_stylegpsaggese/helpersSkill158todayApache-2.0A14Claude Code
instrument-data-to-allotropeanthropics/knowledge-work-pluginsSkill35ktodayApache-2.0A123Claude Code
exploratory-data-analysisK-Dense-AI/scientific-agent-skillsSkill56k5d agoMITA83Claude Code
matlabK-Dense-AI/scientific-agent-skillsSkill56k5d agoMITA44Claude Code
phylogeneticsK-Dense-AI/scientific-agent-skillsSkill56k5d agoMITA71Claude Code, Codex
research-engineerdavila7/claude-code-templatesSkill33ktodayMITA43Claude Code, Codex
mapping-to-snomedmaziyarpanahi/openmedSkill5.8ktodayApache-2.0A205Claude Code