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 mronkko/claude-academic-research/plugin install academic-researchWrote 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/mronkko/claude-academic-research/cluster-screening)<a href="https://agentmods.dev/skills/mronkko/claude-academic-research/cluster-screening"><img src="https://agentmods.dev/badge/skills/mronkko/claude-academic-research/cluster-screening/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/mronkko/claude-academic-research/cluster-screening"><img src="https://agentmods.dev/badge/skills/mronkko/claude-academic-research/cluster-screening.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.00098 | $0.02993 |
| Opus 5 | $0.00049 | $0.01496 |
| Sonnet 5 | $0.00020 | $0.00599 |
| Haiku 4.5 | $0.00010 | $0.00299 |
Grade B, and why
cluster-screening scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
allow_rules: Bash(ssh:*) (~/.claude/settings.local.json) How it starts
The opening of the file, as written. The whole thing — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cluster-screening
Glossary: unfamiliar with PRISMA, MCP, BBT, stage tag, or DOI? See skills/_glossary.md.
This skill covers one thing: running the screening or coding LLM pass
somewhere the plugin cannot reach, and bringing the answers back.
Everything before it (search, import, enrichment, the screening
protocol) and everything after it (audit, export, the manuscript) is
systematic-review's. Load that skill for those; load this one for the
round trip.
Pre-flight (ALWAYS run first, both of them, in this order)
python3 "${CLAUDE_PLUGIN_ROOT:-.}/scripts/setup/check_configured.py"
python3 "${CLAUDE_PLUGIN_ROOT:-.}/scripts/setup/check_cluster_config.py"
If the first says NOT CONFIGURED, stop and hand off to /setup.
The second prints the automation level. Read the effective: line and
obey it. The level is not yours to choose, raise, or work around. It
is a statement about how much of a shared facility account — somebody
else's allocation, on hardware the user is accountable for — the user
has agreed to hand over. If the level blocks what you were asked to do,
say so and print the commands; do not set a level to get past a
permission prompt, and do not suggest --automation auto as a fix for
one.
The block looks like this:
automation: confirm
source: config.toml [cluster] automation
effective: auto
allow_rules: Bash(ssh:*) (~/.claude/settings.local.json)
query_rules: none
settings_files: 2 read
automation: is what was asked for; effective: is what will actually
happen; any NOTE: line explains a difference between them. Relay a
NOTE: to the user in full. Both directions matter: confirm with an
allow rule confirms nothing (usually one "don't ask again" click, long
forgotten), and auto without one prompts on every call, which in a
headless session reads as a hang.
To change it, the user decides and this writes it:
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/setup/set_cluster_automation.py <level>
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 · 277 lines · 98 tokens per session scan B 12dc4b1663fc
cluster-screening is a skill published in the GitHub repository mronkko/claude-academic-research (23 stars, last pushed 6d ago), licensed MIT. It adds 98 tokens to every session and 2,993 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…