research-publishing

research-publishing is a skill for Claude Code from fcakyon/phd-skills. It costs 64 tokens per session (987 once invoked), scanned A, original, MIT.

A preparation aid for releasing research code and data publicly alongside an academic paper.

In plain words
What is it for?
It is for auditing credentials and private information, pinning dependencies, finding dead or duplicated code, adding a license and usage documentation, and structuring a reproducible research repository.
Why use it?
It helps remove secrets and machine-specific details, check dependencies and licenses, and organize the repository so others can install and repeat the work.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the phd-skills plugin — 12 skills, 6 commands, 2 agents, 4 hooks shipped together

Good fit It is for auditing credentials and private information, pinning dependencies, finding dead or duplicated code, adding a license and usage documentation, and structuring a reproducible research repository.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/fcakyon/phd-skills/research-publishing
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 fcakyon/phd-skills --skill research-publishing
Clone the repo
git clone --depth 1 https://github.com/fcakyon/phd-skills

Made for: Claude Code.

Or install phd-skills, the plugin that ships this one along with the rest of its 12 skills, 6 commands, 2 agents, 4 hooks.

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 research-publishing

README.md
[![agentmods](https://agentmods.dev/badge/skills/fcakyon/phd-skills/research-publishing/github.svg)](https://agentmods.dev/skills/fcakyon/phd-skills/research-publishing)
Your own site
<a href="https://agentmods.dev/skills/fcakyon/phd-skills/research-publishing"><img src="https://agentmods.dev/badge/skills/fcakyon/phd-skills/research-publishing/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 research-publishing

Your own site · 80×15
<a href="https://agentmods.dev/skills/fcakyon/phd-skills/research-publishing"><img src="https://agentmods.dev/badge/skills/fcakyon/phd-skills/research-publishing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 64 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 987 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00064 $0.00987
Opus 5.5 $0.00026 $0.00395
Sonnet 5.5 $0.00013 $0.00197
Haiku 4.5 $0.00006 $0.00099

Measured 2mo ago against content hash ac298a042983, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

research-publishing 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 2mo 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.

plugin/skills/research-publishing/SKILL.md · 122 lines

How it starts

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

Research Publishing Methodology

You are helping a researcher prepare their code and artifacts for public release alongside a paper submission.

Step 1: Repository Assessment

Before any changes, audit the current state:

  1. Sensitive content scan:

    • API keys, tokens, credentials (grep for common patterns)
    • Hardcoded paths specific to the researcher's machine
    • Internal URLs or private infrastructure references
    • Personal identifiable information in comments or data
  2. Dependency audit:

    • List all dependencies with pinned versions
    • Identify any proprietary or restricted-license dependencies
    • Check for abandoned/unmaintained dependencies
    • Verify all dependencies are pip/conda installable
  3. Code organization:

    • Identify dead code, debugging artifacts, scratch files
    • Find duplicated code that should be unified
    • Check for overly complex code that can be simplified

Step 2: Repository Structure

A publishable research repository should have:

project/
  README.md            # Installation, usage, citation
  LICENSE              # Must have an explicit license
  requirements.txt     # or pyproject.toml with pinned deps
  setup.py / setup.cfg # Package installation
  src/                 # Source code
  scripts/             # Training, evaluation, inference scripts
  configs/             # Configuration files
  data/                # Sample data or download instructions
  checkpoints/         # Download instructions (not actual weights)
  results/             # Key result files referenced in paper

Step 3: Reproducibility Checklist

For each experiment in the paper:

  • Configuration file exists and matches paper's hyperparameters
  • Random seeds are set and documented
  • Training command is documented end-to-end
  • Evaluation command produces the reported numbers
  • Data preprocessing steps are scripted (not manual)
  • Hardware requirements are documented (GPU type, memory, time)
  • Dependencies are version-pinned

Read the full file on GitHub · 122 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. 2mo ago First seen · 122 lines · 64 tokens per session scan A ac298a042983

Subscribe to this mod's changes

research-publishing is a skill published in the GitHub repository fcakyon/phd-skills (437 stars, last pushed 18d ago), licensed MIT. It adds 64 tokens to every session and 987 once invoked, about $0.0003 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-08-30.