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 hamzabellouch/agent-skills --skill academic-nature-nature-citationgit clone --depth 1 https://github.com/hamzabellouch/agent-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/hamzabellouch/agent-skills/academic-nature-nature-citation)<a href="https://agentmods.dev/skills/hamzabellouch/agent-skills/academic-nature-nature-citation"><img src="https://agentmods.dev/badge/skills/hamzabellouch/agent-skills/academic-nature-nature-citation/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/hamzabellouch/agent-skills/academic-nature-nature-citation"><img src="https://agentmods.dev/badge/skills/hamzabellouch/agent-skills/academic-nature-nature-citation.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.00236 | $0.01041 |
| Opus 5 | $0.00118 | $0.00521 |
| Sonnet 5 | $0.00047 | $0.00208 |
| Haiku 4.5 | $0.00024 | $0.00104 |
Grade A, and why
nature-citation 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 8d 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.
This is a copy
94% identical to nature-citation — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nature Citation — Router
This skill is split into two layers:
- A static layer under
static/that holds versioned, reusable content fragments (core principles and scope, the Chinese-user operating mode, and the citation workflow). - A dynamic layer (this file plus
manifest.yaml) that loads the core every time and reaches for heavier material only when a step needs it.
Do not try to apply the citation logic from memory or from this router. Always load fragments from disk as described below.
Routing protocol
Follow these four steps every time the skill is invoked.
1. Load the manifest and the core layer
Read manifest.yaml. Then read every file listed under always_load:
static/core/principles.md— what the skill produces, the strict journal scope, the source hierarchy, and the search-quality rules.static/core/chinese-mode.md— how to operate when the user writes in Chinese or asks forNature系列/CNS及子刊style support.static/core/workflow.md— the seven-step workflow and the final report format.
2. No content axis — confirm scope and language inline
Unlike the other nature-* skills, nature-citation has no fragment axis. Its variation is runtime parameters, not different content bodies:
- journal scope —
Nature系列/CNS/CNS及子刊/ flagship-only. Read it from the user's wording (seecore/principles.md) and pass it to the script as--scope. - user language — if the user writes Chinese, follow
core/chinese-mode.md(Chinese notes, English search queries). - input length — if there are more than ~10 segments, switch to the batched long-article strategy in
references/script-usage.md.
State the detected scope and date limits in one short line before searching.
3. Run the workflow
Follow the seven steps in core/workflow.md: segment, parse, search, evaluate support conservatively, export one reference-manager file, generate review artifacts when useful, and report with the HTML browser path first. Prefer scripts/nature_citation.py for the search/export when internet access is available; open references/script-usage.md for its full flag list and the long-article batch strategy.
What ships with it
12 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.
- evals/evals.json 1.8 KB
- manifest.yaml 1.6 KB
- README_EN.md 1.9 KB
- README.md 1.8 KB
- references/journal-scope.md 2.1 KB
- references/ris-endnote.md 2.0 KB
- references/script-usage.md 3.2 KB
- references/search-strategy.md 2.9 KB
- scripts/nature_citation.py 69 KB runs code
- static/core/chinese-mode.md 767 B
- static/core/principles.md 3.0 KB
- static/core/workflow.md 5.3 KB
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.
- 8d ago First seen · 71 lines · 236 tokens per session scan A 58928bef2e20
nature-citation is a skill published in the GitHub repository hamzabellouch/agent-skills (4 stars, last pushed 1mo ago), licensed MIT. It adds 236 tokens to every session and 1,041 once invoked, about $0.0012 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to nature-citation, differing in 4 lines, and is treated as a copy.
Other skills, from other repositories
spec-implement
Orchestrate parallel implementation of a feature specification by dispatching coder agents batch-by-batch with code review gates between batches. Use this skill when the user says "implement this feature", "start implementing", "run the spec", "execute the plan", "continue implementing", or wants to begin coding a…
spec-create
Create a structured feature specification with self-contained task files organized into parallel execution batches. Use this skill when the user says "create a spec", "plan this feature", "write up an implementation plan", "break this into tasks", or after any planning conversation where the user wants to capture…
spec-ship
Push the current branch to GitHub and create a pull request. Use this skill when the user says "ship it", "ship this", "push to github", "create a pr", "open a pull request", "send for review", "get this reviewed", or wants to push their work and open a PR. Also use when the user says "/spec-ship" (or their host's…
spec-checkpoint
Create a comprehensive checkpoint commit with detailed analysis of all changes. Use this skill when the user says "checkpoint", "commit everything", "save my progress", "create a commit", or wants to stage and commit all current changes with a well-crafted message. Also use when the user says "/spec-checkpoint" (or…
generative-seo
Run an evidence-based SEO + GEO (Generative Engine Optimization) program for ANY website or product codebase — auditing technical SEO, writing or retrofitting content so it gets cited by ChatGPT/Perplexity/AI Overviews, tracking AI-citation visibility, refreshing competitor research, and drafting distribution posts.…
spec-verify
Verify a completed feature spec by driving the real running app — not just lint/typecheck/build — and checking off every acceptance criterion from its specs/{feature}/ folder one by one. Use this after /spec-implement finishes a spec, when the user says "test this end to end", "verify this feature actually works"…