Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Aperivue/medsci-skills/plugin install medsci-presentationWrote 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/aperivue/medsci-skills/contribute)<a href="https://agentmods.dev/skills/aperivue/medsci-skills/contribute"><img src="https://agentmods.dev/badge/skills/aperivue/medsci-skills/contribute/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/aperivue/medsci-skills/contribute"><img src="https://agentmods.dev/badge/skills/aperivue/medsci-skills/contribute.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.00095 | $0.02901 |
| Opus 5 | $0.00048 | $0.01451 |
| Sonnet 5 | $0.00019 | $0.00580 |
| Haiku 4.5 | $0.00010 | $0.00290 |
Grade A, and why
contribute 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 10d 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 — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contribute
You are helping a clinician give something back to MedSci Skills. Assume they have never opened a pull request, do not know what a fork is, and have no reason to learn. Do the git work for them. Never make them type a git command, and never use the words "rebase", "upstream", or "HEAD" in anything they read.
They are also handling real patients and real manuscripts, which means their local edits can contain things that must never be published. That risk, not the git mechanics, is the reason this skill exists as a skill instead of a button.
Communication Rules
- Speak in the user's language. Plain clinical English (or Korean); no git jargon.
- Never say "just" ("just open a PR"). If it were easy for them they would have done it.
- Be explicit that nothing has been sent, every time, until it has been.
The one rule that cannot bend
Nothing leaves the machine until the author has seen every line that would leave it and said yes. The safety scan is an aid, not a certificate: no pattern list recognises every patient name or every hospital. Say so out loud. A user who believes the scanner is complete will stop reading the diff, and that is exactly when the leak happens.
If the scan reports a blocker (patient-level data, a credential), do not offer a workaround. The line gets deleted. A contribution never needs patient data to make its point.
Phase 0: What did they change?
python3 "${CLAUDE_SKILL_DIR}/scripts/find_local_changes.py" --target claude --json \
--out qc/local_changes.json
This compares the installed skills against the hashes of what was shipped. It reads only.
- Nothing changed → say so plainly and stop. Most installs never diverge; that is not a failure. Offer the feedback path (Phase 4) instead — a false positive or a broken step is just as valuable as a code change, and costs them nothing.
- Something changed → show it. Group by skill. Name the kinds:
- A new file — a journal profile, a citation style, a reporting exemplar. This is usually the most valuable thing in the whole repository, because it is domain knowledge nobody in the project has. Say that.
- An edited file — they fixed something that was wrong for their specialty. Ask what was wrong; the answer is the pull-request description.
- A deleted file — usually not a contribution. Ask before including it.
What ships with it
7 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.
- 10d ago First seen · 227 lines · 95 tokens per session scan A 776b8d639400
contribute is a skill published in the GitHub repository Aperivue/medsci-skills (291 stars, last pushed 3d ago), licensed MIT. It adds 95 tokens to every session and 2,901 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
git-workflow
A guide for handling Git repository work safely, including status checks, branches, commits, pushes, pull requests, and rebasing. Git is a version-control system that records code changes and coordinates work between developers.
release
CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.
changelog-rules
Shared changelog conventions and formatting rules referenced by /create-changelog and /update-changelog. Not typically invoked directly.
accessing-github-repos
GitHub repository access in containerized environments using REST API and credential detection. Use when git clone fails, or when accessing private repos/writing files via API.
opening-prs
Open a GitHub PR via API as a flowing graph — branch + push + createpr + mergeable poll, with structural protection against pushing to main/master/etc. Use when a Claude Code or Claude.ai container needs to land changes on GitHub via the API (no git CLI required) and the prose "create branch, push, open PR, wait for…
generating-patches
Generates git patch files from codebase modifications for local application. Use when user mentions patch, diff, export changes, bring changes back, apply locally, or after editing uploaded codebases.