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 cmertdalli/polisci-review --skill claude-skillgit clone --depth 1 https://github.com/cmertdalli/polisci-reviewWrote 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/cmertdalli/polisci-review/claude-skill)<a href="https://agentmods.dev/skills/cmertdalli/polisci-review/claude-skill"><img src="https://agentmods.dev/badge/skills/cmertdalli/polisci-review/claude-skill/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/cmertdalli/polisci-review/claude-skill"><img src="https://agentmods.dev/badge/skills/cmertdalli/polisci-review/claude-skill.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.00000 | $0.00507 |
| Opus 5 | $0.00000 | $0.00253 |
| Sonnet 5 | $0.00000 | $0.00101 |
| Haiku 4.5 | $0.00000 | $0.00051 |
Grade A, and why
claude-skill 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 12d 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
100% identical to polisci-review — 0 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.
What it actually says
description: Run a public-facing political science pre-submission audit with journal personas, stage gating, and evidence-grounded issue reporting argument-hint: [journal] [track] [stage] [path]
You are coordinating a rigorous political science pre-submission audit.
This installed skill is self-contained. Read the canonical review files in this directory before reviewing:
./core/invocation-spec.md./core/journal-manifest.json./core/paper-discovery.md./core/track-stage-rules.md./core/issue-taxonomy.md./core/references/guardrails.md./core/references/journal-signals.md./core/references/journal-personas.md- the relevant module specs in
./core/modules/ ./core/report-template.md
Then:
- Parse
$ARGUMENTSusing the canonical invocation contract. - Discover the manuscript and any linked
.tex, appendix, figure, table, and bibliography files. Prefer.texwhenever available; support.docx,.md,.txt, and text-readable.pdfon a best-effort basis. - Detect the stage and track if they were omitted.
- Run the 9-module review structure defined in
./core/modules/. - Write two output files in the main manuscript directory when a manuscript path is available; otherwise write them in the current working directory:
review-report.mdusing the canonical report templatereview-report.jsonconforming to./core/issue-schema.json
- Before finishing, make sure
review-report.jsonis valid JSON and briefly confirm the paths you wrote.
Mandatory guardrails:
- Do not merely describe the outputs. Write the files unless the environment prevents file output.
- If the environment cannot write files, say so explicitly and return the Markdown report plus the JSON artifact directly in the response.
- Every issue must include a
module, location anchor, evidence status, andjournal_policy_ref. - Do not claim missing references, broken cross-references, or absent robustness checks without checking the files.
- If
.docxor.pdftext cannot be read reliably, say so and ask for exported text instead of guessing. - Proposals and dissertations must be reviewed with stage-aware expectations.
- Use
PAforPolitical Analysis.
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.
- 12d ago First seen · 41 lines · 0 tokens per session scan A 347ebb8849db
claude-skill is a skill published in the GitHub repository cmertdalli/polisci-review (18 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 507 tokens. A static security scan graded it A with 0 findings. It is 100% identical to polisci-review, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
ieee-letter
Write or compress an IEEE communications LETTER for WCL (IEEE Wireless Communications Letters) or CL (IEEE Communications Letters): a single-contribution paper with a compressed introduction, no standalone related-work section, one system model, one core result (an algorithm OR a closed-form expression), and a tight…
ieee-experiments
Design and audit IEEE communications simulation and numerical-results sections for JSAC, TWC, TCOM, WCL, and CL. Covers benchmark schemes, Monte-Carlo protocol, BER/SER/outage/rate/EE metrics, SNR/antenna/user sweeps, analysis-vs-simulation validation, convergence and complexity, learning-based evaluation, ISAC…
ieee-polishing
Polish academic prose to IEEE-journal style at the sentence level — clarity, sentence length, section-appropriate tense, calibrated hedging, US English, acronym discipline, numbered-citation phrasing, and unit/number formatting. Also translate Chinese drafts into IEEE-style English. Use this whenever the user wants to…
ieee-response
Draft the two letters an IEEE submission needs — the point-by-point response to reviewers and the cover letter to the editor — so every comment is answered, every change is traceable to the revised manuscript, and the tone stays cooperative without conceding more than the evidence requires. Use this whenever the user…
ieee-writing
Draft, restructure, or plan IEEE communications-journal manuscript sections (JSAC, TWC, TC/TCOM, WCL, CL): abstract + Index Terms, introduction with a contributions list, related work, system model, problem formulation, proposed solution/algorithm, performance analysis (theorems/proofs), numerical results, discussion…
ieee-figure
Produce publication-grade result figures for IEEE communications papers (JSAC, TWC, TC/TCOM, WCL, CL) — correct column widths, embedded fonts, vector output (PDF/EPS), grayscale- and colorblind-safe palettes, readable fonts, and the comms-standard plot types: BER/outage vs SNR on a log y-axis, achievable/sum rate vs…